Planning and Design
The act of building an Intranet is simple compared to the amount of time needed to get the design, requirements and planning figured out.
Identify the project Sponsor and Stakeholders – Before you can start off on your Intranet project, you need to make sure you’ve got proper management support. Who will back you up when you propose to introduce an Intranet to your organization? Who is ultimately responsible for setting the vision and direction? Every project needs a sponsor and stakeholders. Setting up an Intranet is no different.
Design Requirements – Be sure to write down any specific requirements.
- Does the stakeholder expect to be able to find a procedure using a simple search interface?
- How many documents will you be hosting?
- What design will you use (centralized, hub and spoke, etc.)
- Who will be involved in evaluating projects?
- What is the time frame for testing and implementing?
- What is your budget?
- Who will be responsible for maintaining the site after it goes “live"?
Be sure you’ve got these questions answered in order to start your project out on the right foot.
Research Solutions – using your requirements as a guide, research solutions. If you don’t have any budget, you’ll be forced to look at free solutions. If you have very few resources to help maintain the site after it is implemented, you may consider a hosted solution as opposed to on-site. Be sure to read reviews from industry trade magazines such as eWeek or sites that deal specifically with Intranet software (sometimes referred to as Portals or Content Management systems). CMSWire has a good list of software packages.
Demos – once you find a few solutions that should meet your needs, start by getting your hands on demos. This may be a lot of work, but it’s better to find out a product won’t work for your organization before you purchase it rather than after.
Prepare a Summary – once you’ve found the right package, write up a summary of your findings and present it to the sponsor and stakeholder(s).