Intranets can be invaluable communication tools for computer-based workgroups, but if they are not planned properly, the final product may not serve any useful purpose. Follow these simple steps to build a functional Intranet.

Difficulty Level: average      Time Required: n/a

1. Define key features the Intranet needs to support. Consider features such as email, conferencing, bulletin boards, electronic documents, news feeds, and knowledge bases.
2. Decide whether the Intranet will be hosted internally or externally. If hosting externally, choose an outsourcing vendor.
3. Prepare a system design. The system design will specify needed hardware and software components (even outsourced solutions require methods of access). Hire a consultant for this if necessary.
4. Evaluate vendor products and make the necessary build-or-buy decisions.
5. Acquire computers for the workgroup. These can be desktop, server, notebook, and handheld computers as appropriate to meet the needs of the community.
6. Network computers to fit the system design. For example, client desktops may require access to Web and email servers.
7. Develop, integrate, and test Intranet software. Besides developer testing, Intranets can benefit from usability testing and small, controlled "pilot" deployments.
8. Create an acceptable use policy. Clearly define the appropriate use models of the Intranet and the consequences of inappropriate use.
9. Install and configure software as needed across the Intranet. Users may need logon identifiers and passwords. Security policies and publishing models may also be configured in software.
10. Train the workgroup in using the Intranet effectively. Describe the available features and how they work; explain the acceptable use policy.
11. Roll out the Intranet to the workgroup. Promote use initially through advertising and, possibly, a reward system.
12. Immediately begin to monitor Intranet use and evaluate potential enhancements. A healthy Intranet will evolve continuously.
    

1. Consider starting small to reduce risk: build a "version one" Intranet with relatively few features, then grow it later.
2. Watch your budget! Many Intranet projects have strict financial constraints.
3. Be sure to listen to feedback from the community.
   

Related Features:

• "The Acceptable Use Policy"
• "Organizational Leadership and Intranets"