Intranet Rollout Work Breakdown Structure
This is a practical guide to building a work breakdown structure for an intranet rollout project — a deliverable-oriented decomposition of the whole scope into manageable work packages, adapted to the realities of launching a company intranet or digital workplace.
What a Work Breakdown Structure is
A work breakdown structure is a deliverable-oriented decomposition of the whole scope into manageable work packages. For the full concept and how it works in general, see Work Breakdown Structure. 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 work breakdown structure 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
- Top-level deliverables
- Sub-deliverables
- Work packages (8–80 hours)
- WBS numbering
- WBS dictionary entries
Intranet Rollout-specific considerations
Tailor the work breakdown structure 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 work breakdown structure 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.