How to Create a Work Breakdown Structure (WBS)
Short answer: a work breakdown structure (WBS) breaks a project into smaller, manageable pieces — phases, then deliverables, then tasks. To build one, start with the final deliverable, break it into major phases, then decompose each phase into tasks small enough to estimate and assign. Stop when each item is a chunk of work one person can own.
What is a work breakdown structure?
A WBS is a hierarchical decomposition of everything a project needs to deliver. The top is the project itself; below it are phases or major deliverables; below those are the individual tasks. It is a map of scope — not a schedule. It answers “what has to be done,” while a Gantt chart answers “when.”
A good WBS makes a project feel finite. Instead of one intimidating goal, you have a tree of concrete pieces you can estimate, assign, and track.
How to create a WBS step by step
1. Start with the end deliverable
Put the final outcome at the top — “Launch mobile app,” “Build the house,” “Run the conference.” Everything below exists to produce this.
2. Break it into major phases
Identify the four to eight big chunks of work. For software that might be Discovery, Design, Development, Testing, and Launch. These become your second level.
3. Decompose each phase into tasks
Under each phase, list the concrete work needed to complete it. “Design” might break into wireframes, visual design, design review, and handoff.
4. Stop at the right level of detail
Keep decomposing until each task is small enough to estimate confidently and assign to one owner — usually a few hours to a few days of work. Going finer creates noise; staying coarser hides risk.
The 100% rule and other guidelines
The most important WBS principle is the 100% rule: the children of any item must add up to 100% of that item’s scope — no more, no less. If a phase’s tasks do not fully cover it, something is missing; if they exceed it, you have scope creep.
A few more guidelines: describe WBS items as deliverables or outcomes (nouns) rather than vague activities; make each item mutually exclusive so work is not double-counted; and avoid going more than three or four levels deep for most projects.
WBS vs Gantt chart
A WBS and a Gantt chart are two views of the same work. The WBS organizes scope into a hierarchy; the Gantt chart lays those tasks on a timeline with dependencies and dates. You build the WBS first to capture what, then schedule it on a Gantt chart to plan when.
In LoopGantt, the two are the same data: nest tasks under phases in the WBS tree and they appear on the Gantt chart automatically, with the hierarchy preserved.
Frequently asked questions
What is the 100% rule in a WBS?
It states that the sub-items of any element must represent exactly 100% of that element’s scope — together they fully define it, with no gaps and no overlap.
How many levels should a WBS have?
Most projects need three to four levels: project, phase, and task (sometimes sub-task). Going deeper usually adds management overhead without improving clarity.
Is a WBS the same as a task list?
No. A task list is flat; a WBS is hierarchical and organizes tasks under deliverables and phases, which makes scope, ownership, and progress far easier to see.
Turn your WBS into a schedule
Build a free WBS in LoopGantt — nest tasks under phases, then watch them populate a Gantt chart with dependencies and a critical path, all from one project.