What is a work breakdown structure (WBS)?
A work breakdown structure is the project drawn as a tree. At the top is the thing being delivered: a campaign, a rebrand, a documentary, a website. Below it are the major components, and below each of those the pieces that make them up, down to units of work small enough that one person can own one, estimate it and say when it is done. For a brand film the branches might be development, pre-production, production, post-production and delivery; under post-production sit the edit, the grade, the sound mix, the motion graphics and the versioning; under versioning sit the individual cuts and formats.
The WBS is about scope, not sequence. It answers what has to exist, not when or in what order, which is what the schedule does later. The convention is that the tree is complete: everything in the project appears somewhere, and nothing appears that is not in the project. That rule is what makes it useful, because a WBS that leaves out the music license or the captioning will produce an estimate that leaves them out too.
Why it matters
Why a WBS matters
Most estimating mistakes are omissions. A producer who prices a shoot from memory forgets the thing that was not on the last job, and the forgotten item turns into an overrun or an argument. A WBS forces the whole scope into view before a number is put on it, and it gives the client and the agency a shared picture of what the money buys. When the client later asks for one more version, both sides can see that it is a new branch rather than part of an existing one.
It also makes delegation honest. A tree whose leaves are each owned by a named person is a plan that can be checked. Progress is measured by leaves finished rather than by a feeling, and risk shows up where branches are still unassigned or unestimated a week before the shoot. For creative projects, which have a way of growing in the dark, that visibility is the difference between managing the work and discovering it.
In practice
How a WBS works in practice
- 01
Building one starts with the deliverables list from the scope of work. The project manager or producer, often with the creative director and heads of department, breaks each deliverable into phases and each phase into tasks, stopping when a task is small enough to estimate in hours or days and to assign to one owner. Each element gets a code, so that the edit of the thirty-second cut is traceable from the top of the tree to a line on the timesheet. The structure is usually drawn as an outline or a diagram and then loaded into whatever project tool the agency uses.
- 02
From there it drives everything else. Estimates are built by pricing the leaves and adding up. The schedule is built by sequencing them. Resourcing is built by seeing which people own too many. During the project, time and cost are tracked against the same codes, so that the report shows which branch is over and why. Change is handled by adding or altering branches explicitly, which makes scope creep visible as a tree that is growing. At wrap, the completed WBS is a record of what the project actually took, and it becomes the template for the next one like it.
Watch out
What people get wrong about a WBS
Confusing it with a schedule or a to-do list. A WBS describes the deliverables and their components; the timeline and the daily tasks come from it but are not it. The second mistake is breaking the work down too far, so that the tree has hundreds of leaves and nobody maintains it, or not far enough, so that "post-production" is a single line with a single guessed number. The third is building it once and ignoring it. A WBS that is not the basis for the estimate, the timesheets and the change orders is a diagram, and the project runs on hope instead.
