A successful Intranet project needs to clearly define all dependencies. Key dependency considerations include:
Content & Data
- Where is content (both static, dynamic and document based) being sourced from?
- Are there external platforms that need to be dynamically linked to or integrated with?
- If an existing Intranet exists, is any current information housed within this to be used?
- What is the required information architecture for the Intranet?
- What new content is required?
- What is required to generate and organize this new content?
- What resources are required to undertake the content preparation phase?
Authoring & Migration
- Who (from a resource and responsibility perspective) is responsible for the authoring of new Intranet content?
- Who (from a resource and responsibility perspective) is responsible for the entering of content (both new and existing content migration)?
- What workflow/approval processes are required to sign-off on content?
Access by stakeholders
- What stakeholder groups will require access to the Intranet?
- What security roles need to be defined and setup for the different stakeholder groups?
- What are the content and functionality rules that need to be applied to the different security roles?
- Is external system authentication integration required?
- What are the reporting requirements for the Intranet?
- What roles are to have access to view the reporting features?
- Is the Intranet to be hosted on-premise or in the cloud?
- If cloud based, are there any hosting preferences or existing providers that should be used?
In Part 5 we’ll cover defining your Intranet project deliverables.