Home › The Garage › Decomposition
Transformation

Work decomposition

A goal too big to start is just a goal too big to see. Decomposition breaks it into pieces small enough to estimate, assign and finish — so progress becomes visible instead of a single distant deadline.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. Why decompose
  2. The work breakdown structure
  3. Epics, stories, tasks
  4. How small is small enough
  5. Common questions
Goal Workstream A Workstream B Workstream C tasks tasks tasks
Break the goal into workstreams, then into tasks small enough to estimate and finish.

Why decompose

Large goals stall because they can’t be started — there is no obvious first move, no way to estimate, no way to tell if you’re on track. Decomposition breaks the goal into progressively smaller pieces until each is something a person can pick up, size and complete. It turns one intimidating deadline into a visible flow of finishable work.

The work breakdown structure

A work breakdown structure (WBS) is the classic tool: a tree that splits the goal into deliverables, deliverables into work packages, and packages into tasks. The rule is that children fully add up to their parent — nothing missing, nothing double-counted. A good WBS is organised around outputs (the things produced), not activities, so it stays stable even as the plan to build them changes.

Epics, stories, tasks

Agile teams decompose the same way with different words: an epic is a large body of work, split into user stories (a small slice of value from the user’s point of view), split into tasks. The discipline that keeps stories honest is that each should deliver something demonstrable on its own — a vertical slice — rather than a horizontal layer no one can see yet.

How small is small enough

Small enough to estimate and finish in one go
A piece is decomposed far enough when the team can estimate it with reasonable confidence and complete it without a hidden sub-project inside. If estimates come back as “somewhere between a day and a month,” it isn’t small enough yet. Right-sized pieces are what make a priority order and a Now / Next / Later roadmap actually workable.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What is a work breakdown structure?

A tree that decomposes a goal into deliverables, then work packages, then tasks, where the children fully add up to the parent. Organised around outputs rather than activities, it makes a large piece of work estimable and trackable.

What is the difference between an epic, a story and a task?

An epic is a large body of work, a user story is a small slice of value from the user’s perspective, and a task is a unit of work inside a story. Each story should deliver something demonstrable on its own.

How small should decomposed work be?

Small enough that the team can estimate it confidently and finish it in one go, with no hidden sub-project inside. If an estimate ranges from a day to a month, the piece needs breaking down further.

Should a WBS be organised by activity or by deliverable?

By deliverable — the outputs to be produced. Organising around outputs keeps the structure stable even when the plan for how to produce them changes, and makes it easier to check nothing is missing.

Related guides: Prioritisation techniques · Agile vs waterfall · Transformation roadmap