Quarter planning without the theatre
· 5 min read · by Tan Gravam
The short answer
A quarter plan is a set of commitments the delivering teams agreed to, not a ranked wishlist — so the planning meeting has exactly two inputs and one rule. The inputs: demands that are already decision-ready (understood, owned, sized, unknowns written down), and each team's honest capacity for the quarter. The rule: commit down the list until the capacity line, then stop. Everything below the line gets a recorded not-now instead of a place on a wishlist, and anything pushed past the line by a real deadline gets committed early with a recorded exception — why now, what is missing, who accepts it. The theatre version differs in each particular: it ranks unshaped ideas, treats capacity as negotiable in the room, and ends with a list nobody agreed to deliver.
Most quarter planning meetings produce a ranked list. Ranking feels like deciding — there are numbers, there is a spreadsheet, someone fights for third place versus fifth — but nothing in a ranking commits anyone to anything. The test of a planning meeting is not whether the list is ordered. It is whether, on the way out, a named team has agreed to deliver each item at the top of it.
Two inputs, prepared before the room
Input one: demands that are decision-ready, and only those. A demand earns a place on the planning agenda by being decidable: the problem stated apart from anyone's favourite solution, an outcome, a named owner, a first capacity figure, and the unknowns written down as unknowns. Everything else stays out — not as punishment, but because scoring a vague demand just ranks the vagueness, and the room will spend its scarce minutes debating what the item even is.
Input two: each team's honest capacity for the quarter. In FTE-months, coarse on purpose, with the standing costs already subtracted — support rotation, the platform upgrade nobody gets to skip, the realistic level of interruption. A capacity number that assumes a quarter with no surprises is not an input; it is the first lie of the meeting, and every commitment stacked on it inherits the lie.
The meeting is a walk down to a line
With both inputs real, the meeting itself is almost boring. Walk the list from the top. For each demand: does the delivering team agree with the capacity figure, and can they hold it alongside what is already committed? If yes, commit it — which means the team said yes, not that the room voted. Keep walking until a team's capacity runs out. That is the line.
Everything below the line gets the honest treatment instead of the kind one: a recorded not-now with a reason and, where one exists, the condition that would change it. Not a wishlist position. A wishlist is the slow no at organisational scale — forty requesters who were never told, checking back all quarter.
When something must cross the line anyway
It happens every quarter, and pretending otherwise is its own theatre. A regulatory date, a contract renewal, a commitment your CEO already made on a stage. The mechanism is not to argue — it is to make the crossing explicit: an exception naming why it is early, what is still missing, who accepts the risk, and what would change the decision. Then something below it moves down, visibly, because capacity did not grow when the deadline appeared.
Counted at quarter end, these exceptions are the most useful number planning produces: if most of your misses were early commitments, the problem is not estimation — it is the door.
What to stop doing
Stop estimating the whole backlog — items below the line do not need estimates, they need honest states. Stop treating capacity as negotiable inside the room; the room can change what gets the capacity, not how much of it exists. Stop ending on a list without agreements: if no team said yes to an item, the meeting decided nothing about it, however high it ranks.
And stop measuring the meeting by how it felt. The measure arrives at the end of the quarter, in the closed outcomes of the things above the line: what was promised, what shipped, and what the difference was. A quarter plan is only as honest as its close.
I'm Tan Gravam. I build DeliverySheet — it takes a vague work request to a clear delivery decision, so the shape, owner, capacity, dependencies and open questions are on the table before anyone commits people or a date.
$10/month per workspace during the launch period (normally $189), unlimited members, 7-day free trial. I answer the support email myself.
More on deciding what to commit to
Read the overview: How to decide what to commit to →
- What a decision-ready demand actually contains
Not a template to fill in — the six things that have to be established before a request can honestly become a commitment, and how to tell when one is missing.
- What goes in the quarter, and who decides
Quarterly planning fails as arithmetic before politics: capacity treated as a total, and no record of what you are not doing.
- An owner is a person, not a team
A team name in the owner field means the decision has no address — and the failure shows up at exactly the moment a judgement call is needed.