Process 3 of 15 in this collection

Breaking Work Down: From Goal to Next Physical Step

Process · 2 min read

Big work only moves when it is broken into steps someone can physically do this week. This article covers task breakdown, sub-tasks, and the Step Order sequence - the plain-language version of what professionals call a work breakdown structure.

A goal is a destination. Nobody drives to a destination - they drive to the next turn. Breaking work down is the skill of finding the next turn, and it is the difference between a plan that moves and a plan that gets admired.

The stranger test

A well-written task passes one test: could a capable stranger read it and know what doing it looks like? "Handle the water situation" fails. "Get two quotes for the northern lot pump install" passes. When a task fails the test, it is usually a project in disguise - split it.

Three to seven steps, not fifty

Break a project into the three to seven steps you can actually see from here. Planning fifty steps ahead feels thorough but is fiction after step seven - reality will rewrite the rest anyway. When the visible steps complete, the next ones will have become visible. This is how professionals plan; they simply call it rolling-wave planning.

Sub-tasks and sequence

Big step? Nest it. A task like "Kitchen remodel" holds its own sub-tasks (demolition, electrical, finish work) under a parent task - the expandable arrows in the task views.
Order matters? Number it. The Step Order field turns consciously sequenced work into the "do this next" list (the Start Cadence view). It is deliberately sparse: only work that truly has an order carries a number, so the sequence stays meaningful.
One owner each. Every step has a name on it. Support people are named too, but one person answers "how is it going?"

Captured beats perfect

Sera pulls tasks out of your meetings and emails automatically - sometimes vaguely worded, sometimes without a project. That is fine. A captured-but-scruffy task can be tidied, re-laned, or merged later; a task that lived only in someone's head cannot. Tidying the pool occasionally (a ten-minute "what is this?" pass) is normal hygiene, and Sera will find duplicates for you if you ask.

Key points

A good task passes the stranger test: could a capable stranger read it and know what doing it looks like? Break projects into 3-7 next steps, not fifty - detail beyond the visible horizon is fiction. Anything big nests sub-tasks under a parent task (the expandable arrows). Step Order numbers the consciously sequenced work into a "do this next" list - it is deliberately sparse, only sequenced work carries one. Every task gets one owner; a task with no project or vague wording is still better captured than lost - Sera extracts them from meetings automatically and they can be tidied later.