// description
A hierarchical decomposition of a project into progressively smaller components — from the overall deliverable down to individual work packages that can be estimated, assigned, and tracked. The WBS defines the full scope of the project: if it's not in the WBS, it's out of scope.
// history
The Work Breakdown Structure was formalised by the U.S. Department of Defense in 1962 as part of the Polaris missile programme — one of the most complex engineering projects in history at that point. The WBS became a standard tool in project management methodology and is required by most government contracts. It forms the backbone of the Project Management Body of Knowledge (PMBOK) and is used in aerospace, construction, software, and event management.
// example
A new online course WBS: Level 1 — Course Complete. Level 2 — Content, Platform, Marketing, Admin. Level 3 under Content — Module scripts, Video recordings, Slide decks, Workbooks. Level 3 under Marketing — Sales page, Email sequence, Launch event, Social posts. Each leaf-level item is a discrete piece of work that can be assigned a time estimate and an owner (even if that's just you).
// katharyne's take
WBS is what separates "I'm going to build a course" from an actual plan. Breaking it down hierarchically forces you to think through everything — not just the obvious big chunks but the forgotten pieces (like "set up payment processing" and "create affiliate tracking links"). When a project feels overwhelming, it's usually because it's still a blob in your head. WBS turns the blob into a list of manageable tasks. Anxiety drops significantly.
// creative uses
- Build a reusable WBS template in Notion for your KDP publishing process: Level 2 branches for Content (illustrations, interior layout, front matter), Production (Affinity Publisher file, PDF export, cover file, KDP upload), and Marketing (listing copy, keywords, A+ content, Etsy cross-post). Run every new title through the same template and your average time-to-publish compresses dramatically.
- Use a WBS to scope a new digital product line before you commit to it. If you're considering a Midjourney prompt subscription, decompose it into all its parts: product creation, platform setup (Gumroad/Stan), delivery automation, monthly content cadence, customer support workflow. The true scope often changes whether you pursue it at all, or how.
- Apply WBS to a content batch day: Level 2 — Video, Written, Visual. Level 3 under Video — Script, Record, Edit, Thumbnail, Upload, Schedule. When every micro-task is listed, batching becomes a checklist race rather than a vague goal. It's also much easier to delegate or automate individual tasks when they're itemised.
// quick actions
- Pick one project you currently think of as a single item ("build the course," "launch the shop"). Open a blank Notion page or text file and spend 10 minutes decomposing it into at least 3 levels. Stop only when every leaf item is something you could complete in under 2 hours. That's your WBS.
- After completing your WBS for any project, count the total leaf-level tasks and estimate hours per task. Multiply by 1.5 (everything takes longer than you think). Compare that to your actual available hours before the deadline. Adjust scope or deadline before you start, not when you're already behind.
- Save every WBS you build. After the project is done, add a "missed tasks" column — things that came up that weren't in the original breakdown. Over 3-4 projects, patterns emerge and your templates get more accurate. This compounds into genuinely reliable project planning.
// prompt ideas
Build me a complete Work Breakdown Structure for [describe your project — e.g. launching a new online course, publishing a KDP book, setting up a new Etsy shop]. Go to at least 3 levels: the overall deliverable, the main branches, and the individual tasks within each branch. Every leaf-level task should be completable in under 2 hours. Flag any tasks I might typically forget that people commonly miss in this type of project.
I'm planning to [describe a project] with a deadline of [date]. Here is my rough WBS so far: [paste your breakdown]. Review it for completeness: what am I missing, what branches are too vague to be actionable, and which tasks are likely bigger than I've assumed? Give me a revised version with your additions and a rough time estimate for each leaf-level task.
Turn this project I've been procrastinating on — [describe it] — into a WBS I can paste into Notion today. I have [X hours per week] available. Decompose the project fully, give each task a time estimate, then build me a 4-week schedule that fits within my available hours and identifies which week I need to make a go/no-go decision on scope.