FreeNo sign-upYour plan stays on your computer
Work Breakdown Structure Tool
Break what your project must produce into work packages, each small enough to estimate and with one owner, and test every branch against the 100% rule, so no work turns up halfway through.
This tool also runs as a stage in a playbook, which takes you through several tools in order:
- Plan a project that finishes on time Stage 1 of 6: what, exactly, is all the work? Start at stage 1
Not following the playbook?
What the project must deliver
- Start with what the project has to produce, not with a task list.
- One line is enough: every branch below is tested against it.
Branches and work packages
- A branch is one main part of what the project produces, such as a fitted store or a trained team.
- Under each, the work packages: pieces small enough to estimate, give to one owner and track.
- Name each by what it produces (Approved drawings), not by an action (Draw the plans).
- Build it with the people who will do the work.
Or paste a list you already have
One item per line. A line with no indent is a branch; an indented line, or one starting with a dash or a number like 1.2, is a work package under it. An owner can follow a tab or " | ".
Your plan never leaves your browser
The branch and package names, the owners and the scope stay on your computer and in your progress file. To write the diagnosis, only the counts are sent to our server, by place in your list. How it works
Test it against the 100% rule
The pieces under any branch should add up to all of it, no more and no less. Missing work never shows up as an error: it shows up as a project that finishes late. One branch at a time: write what "done" means, check its packages, and ask whether they cover all of it. If not, add what is missing there. A covered branch folds away and the next one opens.
- Ask the people who will do the work: what has to happen before this branch can be called done?
- Often missed: approvals from someone outside the team (a landlord, a client, a regulator), permits and licenses, inspections and sign-offs.
- Also: contracts that take weeks to sign, shipping and customs, and suppliers' lead times.
- And: testing before it goes live, training the people who will use it, moving data or stock, telling customers and staff, handing over afterwards.
- Missing work that touches two branches? Put it under the branch it holds up, or split it into one package for each.
The work breakdown structure
What the first list missed
Who owns what
The three rules, checked
Save your progress
Download your progress file to continue from this point any time, on any computer: choose it under "Coming back?" at the start of the tool. Each new file includes everything so far, including the earlier stages when they are connected, so keep the latest one. Your work stays in this browser only until you close it.
Not saved yet.
Take your results with you
A PDF of your work breakdown structure, what the first list missed, who owns what, the three rules checked, and the diagnosis.
About the tool
Why it exists
All the work, before any of it is scheduled
Projects rarely finish late because a known task took too long. They finish late because of work nobody listed: an approval, an inspection, a contract that takes three weeks to sign. A work breakdown structure lists everything the project must produce, level by level, and tests that nothing is missing. This tool builds one with you, checks it against the three rules, and keeps it as a file you can come back to.
It works on its own, and as stage 1 of our playbook for planning a project that finishes on time, where the work packages and their owners go on to the critical path.
The method
How the tool works
Two levels. Branches are the main parts of what the project produces; work packages are the pieces under each, small enough to estimate, give to one owner and track as a unit. Most projects of a few months need 15 to 40 packages.
The 100% rule. The pieces under any item add up to all of its scope, no more and no less. Only the people doing the work can judge that, so the tool asks it of each branch, with what "done" means for the branch written beside it, and lets you add what is missing right there. The step's tips list the kinds of work first lists often miss: outside approvals, permits, inspections, contracts with long lead times, customs, testing, training, handover.
Nouns, not verbs. A package names something the project produces ("Sofas ordered"), so everyone can tell when it is finished. A name that starts with an action ("Order the sofas") gets a suggested noun form, which you can use or ignore.
One owner each. Every package needs one named person. A package with no owner, or with two, is flagged, and the owners' package counts are shown, because the busiest owners are where clashes start.
What the first list missed. Packages added after you first continue to the check, in step 2 or back in step 1, are counted as work the first list missed, branch by branch.
What leaves your computer. The names of branches, packages and owners stay in your browser and your progress file. To write the diagnosis, the page sends our server only the counts and your answers, by place in your list, and the server keeps nothing.