The day · Page 40
You own the clock
For you only
There is an old line about time, from a 1955 essay in The Economist by C. Northcote Parkinson: "work expands so as to fill the time available for its completion." He wrote it as a joke about bureaucracy. Every workshop facilitator since has watched it operate as physics. Give a team six loose hours and they will spend six hours "almost done". Give them six hours cut into named pieces, with a person who calls the pieces out loud, and the same team ships.
So the clock is yours, and you call it like a race announcer, warmly and without apology:
12:30, halfway. "Three hours down, three to go. If your user cannot click through the main path yet, that is your afternoon." Lunch lands in the room around now. The clock does not stop.
14:30, the last hour call. "Ninety minutes of building left. Stop adding. Start sharpening the one click path you will demo." This is the call teams resent in the moment and thank you for at 16:00.
15:15, the last fifteen. Save links. Test the prototype link on a phone, because that is what the user will probably hold. Breathe.
15:30, hands off. The build is over. Nobody polishes during testing. This rule will be tested, once, by one team. Hold it once and it holds all day.
Two notes on calling time kindly. First, count down in work remaining, not time elapsed: "enough time to fix one flow" lands better than "45 minutes left". Second, never grant extensions, even when the whole room asks. The deadline is what made the day work; a slipped clock teaches every future timebox to be negotiable. The kind version of firm is cheerful: "I know. And the users are already in the building."
The timeboxes are not the discipline. They are the kindness. Nobody has to decide when to stop, because you already did.