Timebox
Concept
A rule that fixes a length of time in advance and, when the time runs out, cuts the scope rather than the clock.
Why it exists
Extending the time until something finishes has no end. A meeting scheduled to run until a conclusion arrives usually takes two hours, and the conclusion at the two-hour mark isn't much different from the one available at thirty minutes. A feature that ships when it's done goes three months with nobody knowing when that is.
The larger problem is that ordering disappears. With no fixed remaining time, there's no reason to decide what comes first. The clock is what forces a priority order to exist at all.
So the rule that fixes the time and treats scope as the variable took hold. It's a device that makes deciding what to drop happen continuously during the work rather than only before it.
How it works
Fix the time first and fit the rest inside it. Four rules.
- Set the length before starting. A concrete value: 15 minutes for the daily scrum, two hours for planning, two weeks for a cycle.
- Stop when the time is up. Allow the extension once and everything afterward extends. The moment "just five more minutes" is said, it stops being a rule.
- Finish by cutting scope. Remaining agenda items get booked into another slot or dropped, and unfinished work rolls to the next cycle. Finished means the time is up, not that everything is done. Rolling work is normal; extending the cycle is not.
- Choose what to do based on the time left. Picking what to cover with twenty minutes remaining is the real yield of the rule.
Applied to a cycle, a second rule attaches: keep the length identical every time. The number of days chosen for one cycle is its sprint cadence, and changing that number repeatedly makes the previous cycle's results useless for the next plan.
It doesn't apply to everything. Incident response, which has to run until it's resolved, doesn't get this rule. It gets a checkpoint instead: if the cause isn't found within 30 minutes, the judgment shifts toward rolling back. A checkpoint is a decision time rather than a deadline.
How it sounds at work
"That's fifteen minutes. You two take the rest separately."
Applying the stop-when-time-is-up rule as written.
"If it doesn't finish this cycle, it rolls. We're not extending the cycle."
Confirming that scope is the variable.
"If we haven't found the cause in 30 minutes, I'm rolling it back."
Setting a decision point on work that has to run to completion.
Pagedeck's planning meeting once stretched to four hours. Discussing each item thoroughly made it longer every time, and the later items got settled carelessly by people who were tired. Theo pinned it at two hours and moved leftover items to the next meeting.
The first two ran out after covering half the list. From the third onward, Mia arrived having ordered the items beforehand, and everything necessary fit inside the two hours. Shortening the time is what produced the ordering.
Where to go next
- Sprint
see the largest place this rule applies
- Sprint cadence
see how that length gets chosen
Last updated 2026-09-16