What a Failing Renovation Taught One Team About the Work Breakdown Structure
A regional organization set out to upgrade a community centre — new HVAC, accessible washrooms, a refreshed kitchen, and rewiring to support hybrid events that had become essential during the pandemic. The schedule looked tidy. Three months in, it was anything but. Trades showed up to work that wasn't ready, two scopes overlapped and nobody owned the seam between them, and the budget was bleeding through change orders no one had anticipated. The plan was not wrong. It was vague. What follows is an anonymized account of how the project manager pulled it back, and the tool that did the heavy lifting: a usable work breakdown structure.
The symptom was a schedule that lied
The original plan had tasks like "renovate kitchen" and "electrical work" — verbs and rooms, not deliverables. Because nobody had decomposed those into concrete pieces of work, no one could say whether "electrical work" was 20 percent or 80 percent done. The schedule reported progress that did not exist. A work breakdown structure (WBS) is the antidote: it breaks the total scope into a hierarchy of deliverables, each small enough to estimate, assign, and verify as truly finished.
How they rebuilt it
Start from deliverables, not activities. They restated each branch as a thing that gets delivered — "accessible washroom, inspection-ready" — instead of an action like "do plumbing."
Decompose to a work package you can manage. Each branch was broken down until the lowest item could be estimated in a known range and owned by one person — the classic 8-to-80-hour rule of thumb.
Apply the 100% rule. The children of any box must add up to all of the parent and nothing extra. If rewiring the events space wasn't under any branch, it didn't exist in the plan — and that gap was exactly the missed scope causing change orders.
Give every work package one owner. The overlapping kitchen and electrical scopes got a clear boundary and a single name against each piece, which ended the "I thought you had it" stalemate.
What the WBS is — and what it isn't
A WBS is deliverable-oriented, not a schedule and not a to-do list. It answers "what are we producing?" before anyone argues about sequence or dates. The schedule, the budget, and the responsibility assignments all hang off it. Build the schedule first and you will plan around scope you never fully defined; build the WBS first and the schedule almost assembles itself.
If a task can't be marked truly done, it's too vague — decompose it further.
Nouns and deliverables, not verbs and activities, at every level.
Capture the unglamorous work too: permits, inspections, cleanup, sign-off.
Stop decomposing when an item is estimable and assignable, not before, not long after.
Within two weeks of rebuilding the WBS, the team could finally say with confidence what was finished and what wasn't. The change orders didn't vanish, but they became predictable rather than ambushes. The lesson the team took away was simple: a schedule is only as honest as the work breakdown beneath it.
If you are scoping a complex build or upgrade and want the breakdown right before the first shovel hits the ground, XNM's program & project delivery advisory can help you structure the work so the plan tells the truth.