Intranet Rollout Issue Log
This is a practical guide to building a issue log for an intranet rollout project — a register of problems that have occurred and need resolving, adapted to the realities of launching a company intranet or digital workplace.
What a Issue Log is
A issue log is a register of problems that have occurred and need resolving. For the full concept and how it works in general, see Issue Log. On an intranet rollout project it plays the same role, tuned to this kind of work.
Why it matters for an Intranet Rollout project
Intranet Rollout projects live or die on launching a company intranet or digital workplace. A well-built issue log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how intranet rollout projects drift into avoidable delay and cost.
What to include
- Issue description
- Priority and severity
- Owner
- Resolution and status
Intranet Rollout-specific considerations
Tailor the issue log to the risks that most often derail intranet rollout projects:
- Content ownership
- Adoption
- Search and information architecture
Example
On a real intranet rollout project, the issue log would be shaped by launching a company intranet or digital workplace. In particular, it should explicitly account for the project’s biggest risks — content ownership, adoption, search and information architecture — rather than treating them as afterthoughts.