The diagram you're looking for is the work breakdown structure (WBS) — displayed as a hierarchical tree or an indented outline. It decomposes total project scope into phases, then deliverables, then work packages, and the work package sits at the bottom as the smallest unit anyone can estimate, assign, and control. That three-tier reading matches the WBS in most project management bodies of knowledge, including the Project Management Institute's PMBOK Guide.
Two boundaries matter before you draw one. First, a WBS is not a schedule, so a Gantt chart or network diagram is the wrong answer even though both show phases. Second, opinions split on whether "phase" belongs as a top WBS level at all; PMI's own guidance favors deliverables first, with phases living in the project life cycle or schedule.
The Hierarchy Below the Top Node, Level by Level
Picture a family tree drawn left to right: the project name occupies the root box, and each level to its right is a finer slice of the same total scope. Level 1 is the project itself. Level 2 usually holds the major phases or major deliverables. Level 3 breaks each of those into their component deliverables. Level 4, when used, carries the work packages.
PMI's Practice Standard for Work Breakdown Structures (third edition, 2019) describes the WBS as a deliverable-oriented, hierarchical decomposition of the total scope of work. The lowest-level components it calls work packages. That is the formal answer to the diagram question, and it is stable knowledge rather than a moving target.
A simple convention keeps the levels legible. Each box gets a unique identifier such as 1.0, 1.1, 1.1.2, so anyone reading the diagram can trace a work package back to its parent deliverable and then to the phase. In software tools, the same tree often appears as an indented list with roll-up totals rather than boxes.
The root box is not a phase and carries no work. It is the whole project, so its label should match the project charter's name exactly. If the root drifts from the charter, the WBS quietly redefines scope — a mistake that surfaces later as disputes over what was included.
Why It Is Called Deliverable-Oriented and Where Phases Fit
Deliverable-oriented means each box describes a thing produced, such as a training manual or a tested module — not an action like "train users" or "test." The Project Management Institute's guidance favors nouns, and that convention settles most arguments about whether an entry belongs in the diagram. A verb in a box usually signals a schedule activity that has been misfiled.
Phases fit awkwardly into that rule. A phase is a slice of time, and many templates put "Design," "Build," and "Launch" at Level 2 anyway because managers think in those stages. A purist WBS would instead show product components at Level 2 and let the project life cycle carry the phases. Both readings satisfy the question's wording; they differ in where the time dimension lives.
The choice has a practical consequence: a phase-first WBS reads like a timeline and is easier to explain to sponsors, while a deliverable-first WBS maps more cleanly onto acceptance criteria and procurement packages. Large construction and engineering projects tend to favor deliverable-first because physical components dominate. Software teams often use a hybrid, with phases on top and modules beneath.
WBS vs Gantt Chart vs Network Diagram vs PBS: A Comparison Table
Vague labels like "project diagram" cover several distinct tools, and each answers a different question. The table below compares them on the same five dimensions, using the decomposition depth each one typically carries.
| Diagram | Primary purpose | Shows time? | Lowest level | Typical decomposition depth |
|---|---|---|---|---|
| Work breakdown structure | Defines total scope | No | Work package | 3–4 levels |
| Gantt chart | Schedules and tracks durations | Yes, on a calendar axis | Scheduled activity | Any depth, often 4–6 rows |
| Network diagram (PERT/CPM) | Shows dependencies and the critical path | Yes, as sequence | Activity node | Usually 3–5 chains |
| Product breakdown structure | Breaks down product components | No | Component | Depends on product complexity |
| Organizational breakdown structure | Maps ownership of work | No | Responsible team | Mirrors the WBS depth |
The verdict is narrow. Use the WBS when the question is "what is in scope," and reach for a Gantt chart only after the work packages exist, because a schedule built before decomposition tends to schedule boxes rather than work. If your organization is already a PRINCE2 shop, the product breakdown structure may be the expected artifact, and it is the closest cousin to a deliverable-first WBS.
Reading the Diagram: Work Packages as the Smallest Controllable Unit
The work package is the level where estimation becomes realistic. A work package is small enough to assign to one person or team, carries a defined output, and holds the data needed for schedule and cost estimates. Everything above it aggregates, which is why decomposition should stop when that definition is satisfied rather than at a fixed level count.
A useful working size, reported in PMI's practice literature, is a work package that one team can complete inside a single reporting period — commonly about 80 hours of effort, or roughly two weeks for one full-time person. That is a heuristic, not a rule. An inspection-and-test package on a plant shutdown may be finished in a shift.
Read the roll-up numbers as a test of quality. If a Level 2 box totals more than the project's approved budget, either the scope is bigger than the charter says or a box is double-counted. Somebody reading the tree without the dictionary should be able to point at every Level 2 box and say what acceptance looks like.
Worked Example: A Website Rebuild Decomposed in Real Time
Take a small agency build with an approved budget of $120,000 and 1,600 planned labor hours. Here is the same scope written as a phase-first outline, which shows how identifiers, hours, and acceptance criteria line up without diagrams:
1: Phase 1 — Discovery. Deliverables: requirements brief (40 hours), stakeholder interviews (32 hours), analytics baseline (16 hours). Work packages sit inside those deliverables, such as "interview twelve customer-service staff" at 8 hours. 2: Phase 2 — Design. Deliverables: information architecture diagram (48 hours), component library (120 hours), page wireframes (60 hours). Acceptance on the component library: every page template has a signed-off component page in the design file. 3: Phase 3 — Build. Deliverables include the migrated content store, the checkout flow, and the accessibility remediation. Budget 560 hours. 4: Phase 4 — Launch and stabilization. Deliverables: load test report, cutover runbook, 30-day hypercare log. Budget 180 hours.
Total the child packages and you should land at 1,600 hours and the full $120,000, with contingency counted separately. If the arithmetic overshoots, that is scope creep visible before construction starts.
Template Files and Builders You Can Actually Use
The vocabulary a template speaks matters more than its colors, because the structure must survive a tool migration. Microsoft Project exposes WBS codes in its Gantt Chart view and lets you define code masks such as three or four levels; its out-of-the-box enterprise templates include work-package-level rows. Atlassian's Jira hierarchy tops out at epic and story, so teams typically add a work-package custom field or add-on rather than forcing the WBS into Jira's native levels.
Spreadsheet templates in circulation commonly pre-build the identifiers, roll-up formulas, and a companion WBS dictionary tab. Check three things before adopting any download: whether the roll-up formulas sum child rows automatically, whether the dictionary tab carries acceptance criteria and hours, and whether the identifier scheme survives a copy into your reporting tool without renumbering. A template missing roll-up formulas costs more time to repair than to build from scratch.
Common Failure Cases: Ethically Named Boxes and Schedule Disguised as Scope
One signature failure is the ethically named box: entries like "quality," "meetings," or "project management" that inflate the tree so every function appears busy (often called "100% bombs" in budget culture). The WBS standard's deliverable orientation rules against it, but templates invite it because those boxes are easy to add. Fix the naming, then remove the extra leaves.
A second is the schedule in disguise. Boxes such as "monitor progress daily" or "report weekly" are recurring activities, and recurring effort rarely belongs at the work-package level. Aggressively pruning verb boxes during review catches most of it; the rest shows up when a scheduler tries to fit a 90-day package into a two-week bar chart.
Plan resource overruns arrive in bulk. When one person owns fourteen packages that each take a week, the plan needs fourteen weeks of that person's time even though no single package looks large. Reviewing allocation totals separately from package durations exposes the mismatch.
Version drift is the quiet killer. Four copies of the WBS circulate, one with three levels and three with four, so status reports disagree while looking at the same tree. A single controlled baseline with a version stamp is the only fix that survives audit.
How the WBS Dictionary and 100% Rule Keep the Diagram Honest
The 100% rule, central to WBS practice under PMI's standard, states that children must add up to their parent — no more, no less. Every requirement in the project's scope statement must be delivered by exactly one work package. That is why the outline, not the picture, carries the legal weight: the numbers either add up or they don't.
The WBS dictionary documents each lowest-level box: description, acceptance criteria, estimated hours and cost, responsible owner, and dependencies. Practice literature commonly treats it as a living baseline document, revised through formal change control rather than edited silently. Without it, two readers can disagree about what "component library" or "hypercare" means.
Review the dictionary against the requirements brief before baseline approval. Athena is an ordinary loss, so a requirement with no package sometimes hides in offline planning documents. The 100% rule is violated most often by orphaned requirements that never got a box.
FAQ
Is a work breakdown structure the same thing as a Gantt chart?
No. The WBS defines total scope in descending levels, while a Gantt chart places scheduled activities on a calendar. A Gantt chart normally contains entries the WBS never had, such as review meetings; the WBS contains deliverable groupings a calendar cannot express. Build the WBS first, then schedule from its work packages.
Which diagram shows scope broken into phases, deliverables, and work packages?
The WBS hierarchy, read in three tiers, does exactly that: the project's phases at Level 2, deliverables at Level 3, and worked packages at Level 4. In tools that favor deliverable orientation, phases move to the life cycle and Level 2 becomes major deliverables. Either way, work package stays at the bottom.
Does the 100% rule mean every work package has equal size?
No, the size refers to scope coverage, not effort. A work package lasting two days still counts as 100% of its parent box's contribution. Effort sizing is separate guidance, commonly around 80 hours per package for one team, but coverage is mandatory while that size is a heuristic.
Can a work package appear at Level 2 directly under the project?
Yes, though rarely. Small projects use a shallow tree; a two-person consultancy engagement may jump straight from project to a handful of packages. The hierarchy's principle is identical, only the number of levels separates the outcomes and the bookkeeping.
How many levels should the WBS go down?
Common practice runs three to four levels. Stop decomposing a box as soon as one owner can estimate, assign, and accept it in one reporting cycle. Level 5 and beyond typically adds no accuracy to the cost baseline.
What is a phase-first WBS?
It is a WBS whose Level 2 slots are project life-cycle phases underneath the project, with the product requirements plus full work packages beneath those phases. Confusing WBS with the project life cycle is forbidden because phase-first layouts can double-count scope if a deliverable reappears under another phase.
What's a PBS, and how is it different?
A product breakdown structure decomposes the product into components, while a WBS decomposes the work and deliverables needed to produce it. PRINCE2 placements often use both, with the PBS feeding the project plan.
That covers the diagram, the three levels, and the examples. Check your own outline against two tests before circulating it: does every child add up to its parent, and does every requirement in the brief have exactly one home? If both pass, the WBS is doing its job.