Change Management Programme Work Breakdown Structure
This is a practical guide to building a work breakdown structure for a change management programme project — a deliverable-oriented decomposition of the whole scope into manageable work packages, adapted to the realities of delivering large-scale organisational change.
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 a change management programme project it plays the same role, tuned to this kind of work.
Why it matters for a Change Management Programme project
Change Management Programme projects live or die on delivering large-scale organisational change. 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 change management programme 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
Change Management Programme-specific considerations
Tailor the work breakdown structure to the risks that most often derail change management programme projects:
- Resistance to change
- Sustaining adoption
- Leadership alignment
Example
On a real change management programme project, the work breakdown structure would be shaped by delivering large-scale organisational change. In particular, it should explicitly account for the project’s biggest risks — resistance to change, sustaining adoption, leadership alignment — rather than treating them as afterthoughts.