How to create a work breakdown structure

A work breakdown structure splits a project into phases, deliverables and work packages. Learn the 100% rule, how to size work and how to draw one.

Written by
FlowDraw Team
Published
Reading time
6 min read
A FlowDraw board with a work breakdown structure for Customer conference 2027: five phases, each split into deliverables and numbered work packages.

Six weeks before a conference, someone asks who booked the AV. Nobody did, because it was on nobody’s list. A work breakdown structure is that list, drawn so gaps show up while there is still time.

Quick Answer

A work breakdown structure splits a project into smaller and smaller pieces of work. Name the project, split it into phases, list the deliverables in each, then break those into work packages that one owner can estimate. Each level must hold all the work of its parent.

What is a work breakdown structure?

It is a tree of everything a project must produce, often shortened to WBS. It says what the work is, not when it happens. The example is Customer conference 2027, with 600 guests on Oct 14 and 15.

Part of a work breakdown structure for a customer conference, with numbered pins on the project box, a phase, a deliverable and a work package.
Four levels, shown on three of the five phases
  1. Project: the whole job, in one box.
  2. Phase: a major stage, such as “2 Prepare”.
  3. Deliverable: something that will exist at the end, such as “2.1 Program”.
  4. Work package: the smallest piece, with an owner and a size, such as “2.1.1 Call for speakers”.

Make one when a project is too big to hold in your head, or when several people must agree on its scope. A small job with one owner can use a checklist.

How to create a work breakdown structure

Name the project

Put the outcome in the top box, with what limits it. “Customer conference 2027, 600 guests, Oct 14 and 15” tells everyone what is in scope. “Events” would not.

Split into phases

The example uses five: Plan, Prepare, Promote, Deliver and Close. Phases suit one-off work like events.

The project box joined by a rail to three phases: 2 Prepare with 25 days, 3 Promote with 20 days and 4 Deliver with 12 days.
Three of the five phases, under the project

You can also split by product part, such as hardware and software, when the work is building something. Pick one way per level, or pieces start to overlap.

List the deliverables

Under each phase, ask what must exist when it ends. Use nouns: “Venue”, “Program”, “Logistics”. Nouns keep you describing results, and steps can come later.

Under 1 Plan the deliverables 1.1 Event brief and 1.2 Venue, and under 2 Prepare the deliverables 2.1 Program and 2.2 Logistics.
Each phase becomes things you can point at

Size the work

Keep splitting until each piece passes the test on the board: one owner, 1 to 10 days, done when its output exists. Number as you go, so people can say “2.1.2” in a meeting.

Each deliverable split into two work packages with a number, a name, an owner and days, such as 1.1.1 Goals and audience, Ana, 3 days.
Work packages carry an owner and a size

Ask the owner for the estimate. Their number is more likely to hold than yours.

Splitting is also how you find vague work. “Catering and AV” hides two jobs, and “Everything else” hides a gap:

Two panels for 2.2 Logistics. The left has shared owners and a package called Everything else. The right has one owner for each of two packages.
The same deliverable, vague and specific

Check it with the 100% rule

Each level holds all the work of its parent, and nothing more. The numbers on the board let you test it:

PhaseIts work packages add up toShown on the phase
1 Plan3 + 4 + 6 + 316 days
2 Prepare10 + 5 + 4 + 625 days
3 Promote5 + 4 + 6 + 520 days
4 Deliver3 + 4 + 2 + 312 days
5 Close2 + 35 days
Project16 + 25 + 20 + 12 + 578 days of work

Two things to keep straight:

  • 78 days is effort, not calendar time. Several people work at once. To get dates, put the work packages on a Gantt chart.
  • Phase 5 has room to grow. “5.2 Wrap-up” still shows “Add a work package”, so its 5 days will change.

Then walk the tree with the team and ask what is missing. Finally, use a RACI matrix to show who else is involved in each piece.

Drawing a work breakdown structure in FlowDraw

The template is free, in the Project management category.

The FlowDraw Templates page with Work breakdown structure as the search result.
Find it under Templates in the sidebar
  1. Open the template

    Search for “Work breakdown structure” under “Templates”, open the card, then choose “Use template”.

  2. Retype what is there

    Double-click any text and type. A work package is a box with three text boxes on it: number, name, and owner with days. The two placeholders under 5.2 are boxes you can type in directly.

  3. Add a work package

    Drag from an empty part of the board around one package and its short line, which selects all five elements. Press ⌘D (Ctrl+D on Windows), drag the copy into place and retype it.

  4. Extend the line

    If the new package sits below the last one, click the vertical line and drag its lower end down to reach it.

  5. Update the sums

    Totals are plain text, so nothing adds up on its own. Retype the days on the phase and in the top box when packages change.

  6. Agree it together

    Choose “Share” and add people. They can comment with C, and on Free everyone you invite can also edit. On Pro only one person can edit.

The work breakdown structure template open in the FlowDraw editor, with the toolbar at the bottom and Share at the top right.
The template open in the editor

On Free, this board is over the limit, with 197 elements where Free holds 150. It opens whole and you can change every word, but adding anything is refused until you are under 150.

Deleting the title block, the key with its two notes and phase 5 leaves 146. Pro has no limit.

Work breakdown structure mistakes to avoid

  • Writing a schedule. The tree has no order. “First” and “then” belong on a Gantt chart.
  • Verbs at every level. “Do the venue” invites more doing. “Venue” can be finished.
  • Shared work packages. With two owners, each assumes the other has it.
  • A catch-all box. “Other” or “Miscellaneous” fails the 100% rule, because nobody can say what it holds.
  • Going too deep. A package of an hour or two is a to-do list. Stop when you can estimate and assign.
  • Leaving out management. Planning and follow-up are work too. Here, they have phases of their own.

FAQ

It defines all the work in a project, so nothing is forgotten and everything has an owner. Estimates, budgets and schedules are then built from its smallest pieces.

Continue Reading

A FlowDraw board with an engineering org chart: Alex Morgan at the top, then Lisa Carter, Mark Evans and Chris Walker with their reports.

Guides·

How to make an org chart

Make an org chart people can trust: what to collect, how to show reporting and dotted lines, and how to draw and share one for free in FlowDraw.

A FlowDraw board with a RACI matrix for a Team plan launch: ten tasks across eight people, with coloured R, A, C and I letters and a key beside it.

Guides·

How to make a RACI matrix

A RACI matrix shows who does, owns, advises on and hears about each task. Learn what the letters mean, how to fill one in and the checks to run before sharing.

A FlowDraw board with a PERT chart for a trade show booth: nine linked task boxes from Start to Finish, with the critical path drawn in red.

Guides·

How to make a PERT chart

A PERT chart maps tasks, estimates and the critical path. Learn the three-point formula, the forward and backward pass, and how to read a finish date.

Ready to create your first diagram?

Turn your ideas, notes, or documents into a clear,
editable flowchart in seconds.

Get Started Free