A work breakdown structure (WBS) is a hierarchical decomposition of the total scope of a project into smaller, manageable pieces. It answers "what will we deliver?" before you ask "when?" or "how much?". Every schedule activity, cost estimate and risk should trace back to an item in the WBS.
Key rules
- The 100% rule: the WBS includes 100% of the work defined by the project scope — and nothing more. The children of each element add up to exactly 100% of the parent.
- Deliverable-oriented: describe outcomes (nouns) rather than activities (verbs) at the upper levels: "Website content", not "Write content".
- Mutually exclusive: no overlap between elements, or work gets counted twice.
- Right-sized work packages: the lowest level should be small enough to estimate and assign — a common guideline is 8 to 80 hours of effort.
How to create a WBS in six steps
- Start from the charter and scope statement.
- Put the project name at level 1.
- Choose level-2 structure: by phase, by deliverable or by component.
- Decompose each element until you reach work packages that one person or team can own.
- Number each element (1, 1.1, 1.1.1) for traceability.
- Write a WBS dictionary: for each work package, a description, owner, acceptance criteria, estimate and dependencies.
Example: company website relaunch
| Code | Element |
|---|---|
| 1 | Website relaunch |
| 1.1 | Project management (plan, status reporting, closure) |
| 1.2 | Discovery (stakeholder interviews, analytics review, requirements) |
| 1.3 | Design (sitemap, wireframes, visual design, design system) |
| 1.4 | Content (content audit, copywriting, imagery, SEO metadata) |
| 1.5 | Build (CMS setup, templates, integrations, migration) |
| 1.6 | Testing (functional, accessibility, performance, UAT) |
| 1.7 | Launch (DNS cutover, redirects, training, hypercare) |
Note that project management itself is a WBS element — it consumes effort and budget.
From WBS to schedule
Each work package is broken into activities, which are estimated (try the PERT estimator), sequenced with dependencies and loaded into a Gantt chart. Running the critical path then shows which work packages drive the end date.
Common mistakes
- Using the WBS as a to-do list of activities rather than deliverables.
- Decomposing too deeply — hundreds of tiny items nobody maintains.
- Forgetting "invisible" work: project management, training, documentation, data migration.
- Building it alone — the team that will do the work should help decompose it.
Put this into practice
Use our free tools to apply what you just read — or get a free consultation if you want an expert to look at your project.