What is a timebox on a team ceremony for, and what should you do when it runs out?

## What a timebox actually is A timebox is a **fixed end time, agreed before the meeting starts, that does not move because the discussion is unfinished**. The second half of that sentence carries the whole idea. A meeting with a scheduled end that everybody expects to overrun is not timeboxed; it is optimistically booked. It is also a **ceiling, not a target**. A planning session with ninety minutes on the calendar that finishes in thirty-five has succeeded. Teams that treat the booked length as an amount to be consumed have quietly converted a constraint into an obligation. ## What the constraint buys - **Prioritisation inside the room.** When the end is real, a group spends its attention on what matters most rather than on whatever came up first. Scarcity does the ordering that an agenda rarely manages on its own. - **A cost you can predict.** Four recurring ceremonies across a seven-person team is a measurable slice of everybody's week. Fixed ends make that number knowable in advance, and a knowable number is the only thing anyone can sensibly argue about. - **Protection for whatever comes next.** An open-ended meeting takes its overrun out of someone else's focused work, or out of another meeting, and nobody ever records that transfer. - **Permission to stop.** Ending a live discussion is socially awkward. A clock everyone agreed to in advance does it impersonally, which is why it works. - **A diagnostic signal.** A timebox that keeps being hit tells you something true about the inputs. An open-ended meeting hides the same information, because overrun there simply looks like thoroughness. ## What it costs The honest answer is that a timebox can truncate the one conversation that mattered. It advantages people who speak quickly and confidently. It can push a group into a decision that twenty more minutes would have improved. And it can let a team defer the same hard subject week after week, because that subject never fits in whatever time remains. Those costs are real, and pretending otherwise is what makes timeboxing sound like bureaucracy to anyone who has been on the losing end of one. | | Fixed end time | Open-ended meeting | |---|---|---| | What decides the order | The group, because time is scarce | Whoever raises something first | | Cost to the week | Known before it happens | Discovered afterwards, if at all | | Main risk | An important point gets truncated | Everything scheduled after it is displaced | | Overrun | Visible, and diagnostic | Invisible, and reads as diligence | | Who is advantaged | Concise speakers | Persistent speakers | ## When the timebox runs out Three honest moves, and one dishonest one. 1. **Close on time with a decision about the remainder.** Name what is unresolved, who owns resolving it, and by when. The meeting ends as agreed and nothing disappears silently. 2. **Give the remainder its own session.** Book a short, smaller conversation with only the people the unresolved item concerns. Most overruns are one topic that needed three people, held hostage to a room of nine. 3. **Accept the consequence.** Sometimes the right answer is to begin the iteration with less agreed than you wanted, and let that show. A visible gap gets fixed; a hidden one repeats. The dishonest move is the silent extension — "let us just take another ten minutes". Somebody else pays for those minutes, the group learns that the end time is negotiable, and the diagnostic signal is destroyed. ## Chronic overrun accuses the inputs, not the team If a ceremony runs over most weeks, discipline is not the problem. Look instead at: - items arriving with no acceptance criteria, so the meeting does the thinking that should have happened before it; - too many people in the room, most of whom cannot act on the decision; - the wrong meeting for the decision — a design argument that has wandered into a planning session; - an unresolved conflict that will surface wherever the team gathers; - a length copied from another team's calendar rather than derived from this team's purpose. A concrete case: a seven-person team building an allotment-management service overran a ninety-minute planning session by forty-one minutes, twice running, as a release timed to an annual conference approached. The cause was not stamina. Fourteen items had been pulled in with no acceptance criteria, so planning had become refinement with a deadline attached. Fixing the inputs returned the meeting to about an hour without anyone being asked to talk faster. ## Setting and revisiting one Derive the length from the decision the meeting must produce and the smallest set of people who must be present. Make the end time visible in the room. Review it after three or four runs rather than defending the first guess. And when meeting load is genuinely too high, shorten the sessions and shrink attendance before cancelling anything — but a ceremony that has changed no decision in a month is not paying for itself, and the right move is to stop holding it while keeping whatever job it was doing somewhere cheaper.