You're staring at something on your list that won't move — "launch the site," "do taxes," "write the report" — and you keep sliding past it. The fix has a name, and naming it helps: the thing you're missing is a smaller first step.
Breaking a big task into smaller jobs is called task decomposition. You'll hear the same idea under several names depending on who's talking:
- Chunking — the casual term, borrowed from memory research: the mind handles small grouped units far better than one long string.
- Breaking it down — the plain-English version most people actually say.
- A work breakdown structure (WBS) — the formal project-management version, where a project is split into progressively smaller deliverables, drawn as a tree.
Different words, one move: turn a single large job into a sequence of smaller, doable ones.
The reason isn't tidiness. It's that a big task and a small task ask different things of your brain.
A task like "write the report" is really a cloud of unanswered questions — what goes in it, where to start, how long it'll take. That uncertainty is uncomfortable, so the task gets postponed in favor of anything more concrete. "Draft the three section headings" has none of that fog. You know exactly what to do, so you start — and starting is nearly the whole battle.
Decomposition buys you three things at once:
- A start. The first small step is a door you'll actually walk through.
- Visible progress. Ten checked-off steps feel like movement; one unfinished monolith feels like failure, even after hours of work.
- Honest estimates. You can guess how long "book the venue" takes. You cannot guess "plan the event" — so you never do, and the calendar lies to you.
You don't need a diagram. You need to keep asking one question: what's the very next physical action?
- Write the outcome, not the task. "A filed tax return," not "taxes." Knowing what done looks like tells you what steps lead there.
- List the steps between here and done. Don't polish — just empty your head onto the page.
- Find the true first action. The one you could do in the next ten minutes with nothing else in the way. If it still feels heavy, it's hiding another task inside it — break it again.
- Give each step a home. A step that fits inside one focused hour is a step you can schedule and actually finish.
- Do only the next one. The list exists so you don't have to hold the whole project in your head. Trust it and work the top item.
For the small, repetitive steps that pile up — emails, admin, quick calls — you can group them instead of scattering them; that's task batching, decomposition's natural companion. And when a step deserves your full attention, single-tasking keeps you on it.
The test is simple: a step is small enough when you no longer have to ask how do I start this? If you do, it's not a step yet — it's another task waiting to be decomposed. In practice, aim for pieces that fit inside a single hour. That size is small enough to begin without dread and large enough to be worth marking done.
There's a reason the one-hour step keeps coming up. Decomposition ends where your actual life happens: in single hours. A project is an abstraction; an hour is real. When each step fits an hour, you can do more than plan — you can account. At the end of the block, one honest sentence about what you did and a color — green if it was lived, amber if neutral, red if it slipped away — turns the plan into a record you can't argue with.
Over a month of graded hours that record shows you which steps were real progress and which were busywork dressed as progress. Big tasks hide that truth; decomposed ones expose it. Because the hours are numbered, the point of breaking work down was never just to get more done — it's to make each finite hour into something you can point at afterward and say what it was for. You can start with the next one in the app.