FIVE THINGS TO CONSIDER WHILE DEVELOPING AN INTRANET

Key concept 1.

Web sites now vary widely from the straight HTML of the 90s. Many are graphic-intensive to
encourage visits, repeat visits and commerce (either online or by using the information on the site
to facilitate a purchase). Library web sites tend to be less graphic intensive, highlighting their
focus on information provision. Intranets need to be even less graphic, concentrating on access to
information and time-saving process.

 Key Concept 2

 Decentralised production is very important because you want staff to interact with the Intranet, not
just think of it as another communication method. “I have to email this info as a memo, print it out and post it for the staff without a PC, and send it to the Webmistress to post it on the Intranet
- Why do I have to duplicate my efforts?” Having a system where an individual posts to the
Intranet, staff members have set their profiles to retrieve certain posts via email, or see it
immediately on their intranet/desktop etc can streamline the communication channel.

Key concept 3.

 Content – what should be on the Intranet?
Once the goals of the Intranet are developed, content needs to be identified for the Intranet.
Conducting an information audit of staff manuals, procedures and other sources of organisational
information is essential.
Assessing their suitability for the Intranet means seeing if they align with the goals/outcomes of
the Intranet  it’s a great opportunity to junk outdated information. More importantly in most
cases, is “chucking” the information into usable pieces that can be put together to form
procedures.

Key concept 4.

 Ongoing development – how will the Intranet evolve?
Following on from these planning and evaluation stages, you need to consider the evolution of the
Intranet.

Key concept 5.

 Informal information audits