New to this topic?
We recommend reading these guides first to get the most out of this one:
Production Scheduling
100%
Rule: Capture All Work
3-5
Decomposition Levels
8/80
Hour Rule for Packages
Scope
Baseline Foundation

What Is a Work Breakdown Structure?

A Work Breakdown Structure (WBS) is a hierarchical decomposition of a project into smaller, manageable pieces. It starts with the final deliverable at the top and breaks it down level by level until you reach work packages — discrete chunks of work that can be estimated, assigned, and tracked.

The WBS is not a schedule, not a task list, and not an org chart. It is a scope definition tool. It answers: "What work must be done?" before you ask "In what order?" (CPM) or "How long?" (PERT). Every scheduling method assumes you already know what the tasks are — the WBS is how you figure that out.

No WBS = No Scope Control

Projects without a WBS have no baseline for what is "in scope" and what is not. Every new request seems reasonable because there is no reference document to check against. The result is scope creep, blown budgets, and missed deadlines. The WBS is the foundation of scope management — if it is not in the WBS, it is not in the project.

The 100% Rule

The most important principle in WBS construction: the WBS must capture 100% of the project scope. Every level must represent 100% of the work in its parent. If you decompose "Installation" into "Electrical," "Mechanical," and "Plumbing," those three must account for all installation work. If commissioning is part of installation, it must be listed too.

100% Rule in Both Directions

The 100% rule works both ways: no work should be missing (under-decomposition), and no work should appear that is not part of the project scope (over-decomposition / gold plating). If it is in the WBS, it gets resourced and tracked. If it is not, it does not get done. This is the power of the WBS as a scope control tool.

WBS Structure

LevelNameDescriptionExample
0ProjectThe entire projectNew Packaging Line
1Major DeliverablesPrimary outcomes or phasesDesign, Procurement, Installation, Commissioning
2Sub-DeliverablesComponents of each major deliverableElectrical, Mechanical, Controls
3Work PackagesLowest-level schedulable/assignable workRun conduit, Pull wire, Terminate panels
New Packaging Line (Level 0)
├─ Design (1.0) ├─ Procurement (2.0) ├─ Installation (3.0) ├─ Commissioning (4.0)
    ├─ 3.1 Electrical   ├─ 3.2 Mechanical   ├─ 3.3 Controls
        ├─ 3.1.1 Run conduit   ├─ 3.1.2 Pull wire   ├─ 3.1.3 Terminate panels
Work packages (level 3) are the lowest level — these become tasks in your CPM network or rows in your Gantt chart

How to Build a WBS

Start with the final deliverableWhat is the project producing? A new line, a validated process, a facility expansion. This is Level 0.
Identify major deliverables or phasesBreak the project into 3-7 major components. Choose either a deliverable-oriented decomposition (what is produced) or a phase-oriented decomposition (when it happens). Deliverable-oriented is generally preferred.
Decompose until work packages are clearKeep breaking down until each element is small enough to estimate and assign. Apply the 8/80 rule: work packages should take between 8 and 80 hours (1-10 days). Smaller than 8 hours is micromanagement; larger than 80 hours is too vague.
Apply the 100% rule at every levelVerify that each parent is fully represented by its children — no gaps, no extras. This is the quality check for your WBS.
Number with a WBS codeAssign a hierarchical code (1.0, 1.1, 1.1.1) to every element. This becomes the universal reference for scope, cost, schedule, and change management.

The WBS Dictionary

For each work package, create a WBS dictionary entry that defines:

FieldPurposeExample
WBS CodeUnique identifier3.1.2
Work Package NameClear, descriptive titlePull wire
DescriptionWhat work is included (and excluded)Pull 480V and control wiring from MCC to new line. Excludes termination (3.1.3).
Responsible PartyWho owns deliveryElectrical contractor (ABC Electric)
Acceptance CriteriaHow you know it is doneAll wire pulled per drawing E-101, megger tested, labeled
Estimated EffortHours or cost40 person-hours, $4,800

Deliverable-Oriented vs. Phase-Oriented

ApproachLevel 1 Looks LikeBest For
Deliverable-OrientedConveyor System, Wrapper, Palletizer, ControlsProduct/equipment-focused projects. Aligns with procurement and engineering.
Phase-OrientedDesign, Procure, Install, Commission, ValidateProcess-focused projects. Aligns with timeline and milestones.
HybridMix of both based on what makes senseLarge, complex projects where neither pure approach works

WBS in Manufacturing Operations

Project TypeTypical Level 1 Elements
New line installationEngineering, Equipment Procurement, Site Prep, Installation, Commissioning, Validation, Training
Plant shutdown / turnaroundMechanical, Electrical, Instrumentation, Insulation, Painting, Safety, Logistics
New product introductionProduct Design, Process Design, Tooling, Validation (IQ/OQ/PQ), Documentation, Training, Launch
Facility expansionPermits, Construction, Utilities, Equipment, IT Infrastructure, Staffing
Lean transformationAssessment, VSM, Pilot Cell, Standard Work, Training, Rollout, Sustainment
✅ Good WBS Practices
  • Apply the 100% rule rigorously at every level
  • Use the 8/80 hour rule for work package sizing
  • Build the WBS with the team, not in isolation
  • Create a WBS dictionary for every work package
  • Use the WBS as the scope baseline for change control
❌ Common Mistakes
  • Confusing a WBS with a task list or Gantt chart — no sequences or dates
  • Decomposing by organizational unit instead of deliverable
  • Going too deep (every nut and bolt) or too shallow (vague mega-packages)
  • Missing management and support work (project management, documentation, training)
  • Building the schedule before defining the WBS

🎯 Key Takeaway

The Work Breakdown Structure is the single most important planning artifact in project management. It defines what the project includes before you figure out when or how long. Every CPM network, Gantt chart, and EVM baseline starts with a WBS. Build it with the team, enforce the 100% rule, size work packages at 8-80 hours, and use it as the foundation for scope control. If someone asks "Is this in scope?" the answer should be: "Is it in the WBS?"

Interactive Demo

Explore a work breakdown structure. Expand and collapse levels to see cost and hour rollups.

⚡
Try It Yourself
Work Breakdown Structure Explorer
▼
Click on any category to expand or collapse it. The WBS shows a 3-level decomposition of a manufacturing project with hours and cost rolling up from work packages.
▶1.0New Production Line616h$307K
▶1.1Equipment260h$195K
●1.1.1Install CNC Machine120h$85K
●1.1.2Conveyor System80h$42K
●1.1.3Robotic Arm Setup60h$68K
▶1.2Facility Prep128h$55K
●1.2.1Floor Reinforcement40h$15K
●1.2.2Electrical Upgrade56h$22K
●1.2.3HVAC Modifications32h$18K
▶1.3Commissioning108h$27K
▶1.4Project Management120h$30K
Cost by Category
Equipment$195K (64%)
Facility Prep$55K (18%)
Commissioning$27K (9%)
Project Management$30K (10%)
616h
Total Hours
$307K
Total Cost
12
Work Packages
4
Categories
Ready for the full knowledge check? Test your understanding with guided scenarios and data export.
PROTake the Pro Knowledge Check →
Keep Learning
📖
Guide
Critical Path Method
📖
Guide
Gantt Charts
📖
Guide
Scope Management
🎓 Part of the Project Management track — view all 13 guides →
Free forever · Every feature included

Stop reading, start modeling

Model your process flow, run simulations, optimize staffing with TOC math, and test your knowledge with 107 interactive checks — all in one platform.

Open Workbench →

Take this to a room

The running order

For project teams at kickoff. They should leave with a WBS test they can apply and the 8/80 rule for sizing packages.

7 beats · 10 min
  1. 1

    No WBS, no scope control

    Without one there is no reference document, so every new request looks reasonable.

    • If it is in the WBS it gets resourced and tracked. If it is not, it does not get done.
    • Projects without one have no basis for saying no.
    • That is where scope creep starts, every time.

    Ask the room When someone asks for something extra, what do we check it against?

  2. 2

    The 100 per cent rule

    Each level captures all of the work at that level. Children add up to their parent exactly.

    • No gaps and no extras.
    • It works in both directions: missing work is under-decomposition, invented work is gold plating.
    • This is the quality check you apply at every level, not once at the end.
  3. 3

    Deliverables, not phases

    Both structures are legal. One of them measures better.

    • Deliverable-oriented: what is produced. Generally preferred.
    • Phase-oriented: when it happens. Useful for some contracts.
    • Activities belong in the schedule. The WBS holds outcomes.
  4. 4

    The 8/80 rule

    Work packages between 8 and 80 hours - one to ten days.

    • Smaller than 8 hours is micromanagement and administrative overhead.
    • Larger than 80 hours cannot be meaningfully estimated or tracked.
    • Three to five levels is typical for most projects.

    Ask the room How big are our current work packages?

  5. 5

    Number everything

    A hierarchical code becomes the universal reference for scope, cost, schedule and change.

    • 1.0, 1.1, 1.1.1 - assigned to every element.
    • Every cost, every task and every change request cites it.
    • Without codes, three systems describe the same work in three different vocabularies.
  6. 6

    The dictionary carries the meaning

    The WBS gives names. The dictionary says what each name includes and excludes.

    • Scope description, deliverables, acceptance criteria, explicit exclusions.
    • Most scope arguments are disagreements about a definition nobody wrote down.
    • It takes an afternoon and prevents months of argument.
  7. 7

    What we do next

    Start from the deliverable and decompose until you can estimate.

    • Level 0 is what the project produces. Then three to seven major components.
    • Decompose to the 8/80 range, applying the 100 per cent rule at each level.
    • Number every element and write the dictionary entries.
    • Then, and only then, build a schedule.

    Ask the room Which project needs its WBS rebuilt before we schedule it?

Related Guides

📅 Critical Path Method
Schedule the work packages
🎯 Scope Management
Control what is in and out
📊 Gantt Charts
Visualize the schedule