Chapter IV
Cool-down
Two weeks with nothing scheduled — where the betting table meets and the whole loop starts again.
The cycle ends on time — that was the whole point — and what follows is not another cycle. For two weeks, nothing is scheduled. No bets are running, no pitches are assigned, and nobody owes anybody a deadline. Cool-down is the deliberate slack that makes six weeks of hard deadlines sustainable, and it's on the calendar by design.
What cool-down is not
Cool-down only works if it stays unscheduled. Three common mistakes undo it.
Not an overflow buffer.
By default, an unfinished bet gets no extension — it goes back through shaping and has to win a new bet. The rare exception: true must-haves that are all downhill, with nothing left to figure out, only execution.
Not extra project time.
Nothing is bet, assigned, or promised during cool-down. Scheduling work into it just turns the six-week cycle into an eight-week one — with no slack left anywhere.
Not idle.
The time is unscheduled, not empty. People are free to work on whatever they want — fixing bugs, exploring ideas, trying out new technical possibilities.
The two tracks, at rest and at work
What the two weeks hold
For the builders, cool-down is self-directed. The just-shipped day view is live and real users are meeting it — so there are bugs worth fixing while the code is still warm, rough edges worth sanding, and the itches every builder collects during six weeks of holding the line: the refactor there was never room for, the idea that wants a prototype, the tool that would make next cycle faster.
For the shapers, cool-down is the deadline quietly working the other track. The pitches they've been shaping all cycle — Chapter I, from the other side — have to be finished now, because the one meeting where the two tracks touch sits in these two weeks: the betting table, deciding what the builders pick up when the clock restarts.
Fig. 1 · The seam between cycles
Builders
Unscheduled, self-directed
Fix — the bugs the shipped bet surfaced, while the code is warm
Polish — the rough edges there was no time for before the deadline
Wander — prototypes, tools, itches — whatever they judge worth it
Shapers
The betting table convenes
Finish — the pitches shaped in parallel all cycle long
Bet — one meeting chooses the next cycle's work
Staff — every bet gets a team before the meeting ends
Two weeks, two tracks. The builders' side has no schedule at all; the shapers' side has the one meeting the whole system turns on. When W8 ends, the bets placed here become the next builder track.
Why it works
More than a break
Cool-down reads like a perk, but the rest of the system depends on it. Teams can ship imperfect work at week six because bugs and follow-up have somewhere to go afterward. And the betting table can run without a backlog because small fixes get done here instead of piling up in a queue.
Then week eight ends and the loop starts over. The builders pick up the new bets; the shapers start shaping for the next betting table. Six weeks of building, two weeks between. That's the whole method.
Terms from this chapter
Cool-down
The two weeks between cycles with no scheduled work. Time to breathe, fix bugs, explore ideas, and decide what to do next.
Self-directed work
What fills the builders' cool-down: fixes, polish, and explorations chosen by the people doing them.
The seam
The betting table meets during cool-down, where shaped pitches become the next cycle's bets.
Six and two
The cadence the method runs on: a six-week cycle, then two weeks of cool-down, then the next cycle.