Intranet Rollout Stakeholder Register
This is a practical guide to building a stakeholder register for an intranet rollout project — a record of stakeholders, their influence and how to engage them, adapted to the realities of launching a company intranet or digital workplace.
What a Stakeholder Register is
A stakeholder register is a record of stakeholders, their influence and how to engage them. For the full concept and how it works in general, see Stakeholder Register. 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 stakeholder register 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
- Stakeholder name and role
- Power and interest
- Attitude
- Engagement approach
Intranet Rollout-specific considerations
Tailor the stakeholder register 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 stakeholder register 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.