When I first started teaching project management many years ago, I used to ask every new class exactly the same question.
“How many of you have created a Work Breakdown Structure?”
Usually, around half the hands would go up.
Then I’d ask the second question.
“How many of you are completely confident you’ve done it correctly?”
At that point the hands would slowly begin disappearing.
I’ve always found that rather revealing because the Work Breakdown Structure, or WBS, is one of those project management tools that everyone recognises but relatively few people truly understand.
Most project managers know they should produce one because every methodology talks about it, every textbook includes it and every certification exam expects you to understand it. Yet when people actually sit down to create one, uncertainty quickly appears.
Some begin listing hundreds of individual tasks. Others produce complicated diagrams that nobody can follow.
I’ve even seen project schedules copied straight out of Microsoft Project and proudly presented as a Work Breakdown Structure.
None of those approaches solves the real problem.
The purpose of a WBS isn’t to create another document for the project folder. Its real purpose is to help you think clearly before you start planning.
In fact, I’d go even further than that. I believe many project failures can be traced back to poor thinking at the beginning rather than poor execution later on.
If you don’t fully understand what has to be delivered, how can you possibly estimate it accurately, allocate the right resources or build a realistic schedule?
That’s why I always tell my students that the WBS isn’t really about breaking work down at all.
It’s about building understanding.
Once people grasp that idea, everything else suddenly starts to make sense.
Why Most Work Breakdown Structures Fail Before the Project Begins
Take something completely outside project management. Imagine you’ve just bought a thousand-piece jigsaw puzzle.
You wouldn’t begin by picking up the first random piece and wondering where it fits. The first thing you’d do is study the picture on the front of the box.
That picture tells you what success looks like. Only then would you begin grouping the edge pieces, finding common colours and gradually assembling the finished image.
Projects work in exactly the same way.
Before you start worrying about individual tasks, meetings and deadlines, you need a clear picture of what the finished project actually looks like.
I think this is where so many Work Breakdown Structures go wrong. People become obsessed with activity.
They start writing things like “Hold meeting”, “Write report”, “Review document” and “Order equipment”. Before long they have pages of tasks, yet they still haven’t properly described what they’re trying to deliver.
How to Create a Work Breakdown Structure Using Deliverables
If I were helping you build a new house, I certainly wouldn’t begin by asking where the electrical sockets should go. We’d first agree that the house needed foundations, walls, a roof, plumbing, electrical services and internal finishes.
Those become the major building blocks. Only once everyone agrees on those would we begin looking at the smaller pieces that sit underneath each one.
Can you see what’s happening?
Instead of building a list of jobs, we’re gradually creating a picture of the finished project.
And that’s the secret.
A good Work Breakdown Structure grows from the top down. You begin with the finished outcome and then progressively break it into manageable deliverables until each piece is small enough for someone to estimate confidently, assign to an owner and monitor during delivery.
Notice that I didn’t say “break it down until every tiny task has been identified.”
That’s another trap.
The WBS isn’t trying to replace your schedule. It’s trying to provide the structure from which your schedule can be built.
Why a Good Work Breakdown Structure Improves Project Planning
Once you’ve built a sensible Work Breakdown Structure, something rather interesting begins to happen.
- Estimating suddenly becomes easier.
- Risks become easier to identify.
- Resource planning becomes more realistic.
Even your project schedule almost starts writing itself because you’ve already done the difficult thinking.
I sometimes compare it to building a house. If the architect produces accurate drawings, the electrician, plumber, carpenter and roofer all know where they fit into the bigger picture.
If those drawings are vague or incomplete, everybody spends their time making assumptions, and assumptions usually cost money.
Projects behave in exactly the same way.
A well-designed WBS provides the blueprint that allows every other planning document to fit together naturally.
Creating a Work Breakdown Structure Should Never Be a Solo Exercise
One mistake I’ve watched countless Project Managers make over the years is disappearing into their office, shutting the door and returning two days later proudly announcing that the Work Breakdown Structure is finished.
Unfortunately, it rarely is.
- The software engineers spot missing components.
- The procurement team identify forgotten suppliers.
- The finance department ask awkward questions about costs.
- The customer points out an entire deliverable that nobody had considered.
That’s why the best Work Breakdown Structures are rarely created by one person. They’re created through discussion, challenge and collective experience.
The Project Manager facilitates the conversation, but the team provides the knowledge.
Ironically, the longer those conversations last, the smoother the project usually becomes.
Final Thoughts on Creating a Work Breakdown Structure That Works
After more than four decades in project management, I’ve become convinced that successful projects rarely begin with better software.
They begin with better thinking.
The Work Breakdown Structure is simply one of the best thinking tools we’ve ever developed.
It forces us (in a good way), to step back, understand what success really looks like and organise our ideas before anyone starts building schedules or assigning resources.
That may not sound particularly exciting, it won’t produce colourful dashboards, it won’t impress your stakeholders with flashy graphics.
But it will quietly influence almost every planning decision that follows.
And that’s why, despite all the new technology available to Project Managers today, I still believe the humble Work Breakdown Structure remains one of the most valuable planning tools you’ll ever learn to use.
