In short
- A flat list makes every task look equally urgent, which hides the one task that blocks the other twenty.
- A phase is a group of steps that must all be true before the next group begins.
- The gate between two phases is where the value is: it turns a vague sense of progress into a yes-or-no question.
A to-do list treats every task as equal. Buy tiles and get the building permit sit side by side, and nothing tells you that one of them will stop the whole job if it is late. That is fine for a weekend of errands. It fails on anything that runs for months.
Long work has a shape. Some things must be finished before others can start, and the cost of doing them out of order is high: you tile a bathroom and then discover the plumbing was never pressure-tested. A phase is simply a way of writing that shape down.
What a phase actually is
A phase is a group of steps that belong together and that must all be done before the next group begins. The line between two phases is a gate: a moment where you stop and confirm the work behind you is really finished.
Phase 2
Foundation
8 of 8 steps done
Phase 3
Structure
locked until the gate clears
The gate asks one question
Is everything behind this line actually true?
- Foundation inspected
- Inspection report filed
- Payment released
Gates are where most of the value sits. They turn a vague feeling of progress into a yes-or-no question, and they give you a natural point to pay a contractor, brief a client, or report to a manager. Nobody has to interpret “about 60% done”. Either the phase closed or it did not.
A phase you can leave without checking anything is not a phase. It is a heading.
Three signs you need phases
If any of these sound familiar, a flat list is costing you time:
- You regularly redo work because something earlier was skipped.
- Nobody can say in one sentence where the project stands.
- Each new project starts from a blank page, even though you have done the same kind of work before.
The third one is the expensive one. A list is thrown away when the job ends, so the next job begins from memory. A flow is the thing you keep, and it gets better every time you run it.
Start small
You do not need a methodology. Take the last project you finished and do this:
- 1Write down the four to six stages it went through, in order.
- 2Under each stage, list only the things that had to be true before you could move on.
- 3For each stage, write one sentence: what do I have at the end of this?
- 4Delete anything nobody would ever forget. Those steps are noise.
That is a flow. It will be wrong in small ways, which is fine — the next project starts from it instead of from a blank page, and you fix it as you go.
Put it into practice
Build your first flow, or start from a ready-made one, in a couple of minutes.