The AI Learning Hub Journal

A Plan Made of Stages

Five stages, four gates — and an honest line in the ledger for eacha task list says what you will do; a stage plan says what must be true before you move onTHE PROTOTYPEthe weekend: screensand the happy path2 days — spentEXPLORE AND PLANthe job, the not-list,this stage plan3 daysBUILD AND CHECKSthe rest of the screens,checks that run alone4 daysBELOW THE SCREENdata done properly, accounts,the services you depend on9 days — the biggestSHIP AND WATCHshipping, watching, fixingwhat week one reveals5 daysGATE — IS THIS TRUE YET?you have decided to make it real,not only to demonstrate itGATE — IS THIS TRUE YET?the job is understood and therefusals are down in writingGATE — IS THIS TRUE YET?the screens exist and the checkspass without you watchingGATE — IS THIS TRUE YET?data safe and restorable · accounts hold —only now does the link go anywhere publicTHE LEDGER, DRAWN TO SCALE — 23 DAYS TO A REAL FIRST VERSION23495the demo — under a tenththe biggest line is work you cannot see from the screen at allillustrative estimates for the groomer’s page, never promises about your project — the numbers drift, the shape transfersWHY A PLAN MADE OF STAGES SURVIVES CONTACT WITH REALITYreality argues with tasks, not with truths — a servicebehaves oddly, the groomer remembers something vital,a week disappears into family life · a task list meets thisbadly: half-done items pile up until it describes nothinghowever the details move, the gates still hold: datasafe before accounts, accounts before the public linkyou always know where you stand, by asking one plainquestion — what is true so far?done with a stage is quiet — nothing shiny, just a yes with evidence behind it · the demo earned applause; the rest mostly earns a nodYOU CAN TICK OFF TASKS ALL WEEK WHILE NOTHING IMPORTANT BECOMES TRUE a gate tells you exactly where you stand — and real products are built out of nods, 23 honest days at a time
A stage is a gate with a plain question attached — is this true yet? — and the ledger is drawn to scale beneath it.

What Has to Be True First

With the job understood and the refusals written down, you need a plan — and the useful kind is made of stages, not tasks. A task list says what you will do: build this screen, connect that email. A stage plan says what must be true before you move on, which is a different and sturdier thing. The data must be safe — recorded properly, backed up, restorable — before accounts are worth building on top of it. Accounts must work, and keep each customer to their own bookings, before the link goes anywhere public. Each stage is a gate with a plain question attached: is this true yet? If yes, move on. If not, the plan has just told you exactly where you stand — which is the thing a task list cannot do, because you can tick off tasks all week while nothing important becomes true.

  • A task list says what you will do; a stage plan says what must be true
  • Data safe before accounts; accounts before the link is public
  • Each stage is a gate with a plain question: is this true yet?
  • You can tick off tasks all week while nothing important becomes true

The Stages, with Honest Numbers

Here is the road this course will walk, with the ledger's honest line for each stage. Exploration, scope and this plan — the work of this module — is 3 days. Building the rest of the screens, plus checks that run without you: 4 days. The parts that aren't the screen — data done properly, accounts, and the services you secretly depend on: 9 days, the biggest line on the whole ledger. Shipping it, watching it, and fixing what the first week reveals: 5 days. Add the 2-day weekend already spent and the total reaches 23 days to a real first version. These are illustrative estimates for the groomer's page, not promises about your project. But the shape transfers even where the numbers drift: the demo is the smallest line, and the largest line is work you cannot see from the screen at all.

  • This module's work — exploration, scope, plan — is 3 days
  • Building and checks: 4 days; the parts that aren't the screen: 9
  • Shipping, watching and launch fixes: 5 — the total reaches 23
  • The largest line is work you cannot see from the screen

Plans That Survive Reality

Plans made of stages survive contact with reality because reality argues with tasks, not with truths. The moment you start building, surprises arrive: a service behaves oddly, the groomer remembers something vital, a week disappears into family life. A task list meets surprises badly — half-done items pile up until the list stops describing anything real. A stage plan bends without breaking, because however the details move, the gates still hold: data safe before accounts, accounts before the public link. You always know where you are by asking what is true so far. Along the way you learn what done actually feels like. Done with a stage is quiet: nothing shiny to show, just a question you can answer with a yes and some evidence. The demo taught you to expect applause. The rest of the work mostly earns a nod — and real products are built out of nods.

  • Reality argues with tasks; it cannot argue with what must be true
  • Surprises bend a stage plan without breaking it
  • Done with a stage is quiet: a yes, with evidence behind it
  • The demo earned applause; the rest earns nods, and products are built of nods
◆ Try it yourself

Give your own project its Module 1. Write the one-sentence job description of your product — one sentence, one verb, the job version one must do. Then write your not-list: at least three things version one refuses to do, each with a by-hand workaround that costs minutes a week and a date when you will look at it again.

The job description:
[my product, in one sentence with one verb]

The not-list:
1. [feature version one refuses] — by hand: [the workaround] — review: [date]
2. [feature version one refuses] — by hand: [the workaround] — review: [date]
3. [feature version one refuses] — by hand: [the workaround] — review: [date]

The first gate:
[what must be true before anyone relies on this]
How you'll know it worked
  • Your job description has one verb, and everything else either serves it or waits
  • Every not-list item has a by-hand workaround measured in minutes a week
  • You can say which stage you are in now, and what must be true to leave it

Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.