Intranet Rollout Lessons Learned
This is a practical guide to building a lessons learned for an intranet rollout project — what went well and badly, captured to improve future projects, adapted to the realities of launching a company intranet or digital workplace.
What a Lessons Learned is
A lessons learned is what went well and badly, captured to improve future projects. For the full concept and how it works in general, see Lessons Learned. 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 lessons learned 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
- What happened
- Impact
- Root cause
- Recommendation
Intranet Rollout-specific considerations
Tailor the lessons learned 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 lessons learned 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.