The mid-quarter ask is an edit, not an addition

It is week seven of a twelve-week quarter and something urgent has arrived — a regulator letter, a churning enterprise customer, a promise the CEO made on a stage. The question the room asks is "can we fit it in?" That is the wrong question, and every honest answer to the right one starts from the same fact: capacity did not grow when the request arrived.

There is no empty seat

The quarter's capacity was committed at planning, when the team walked the list down to the line and stopped. If the plan was honest, every FTE-month is already spoken for. So the urgent ask cannot be added; it can only replace. Treating it as an addition does not avoid the subtraction — it performs the subtraction silently, taking the time from whichever commitment is least defended: usually the platform work, the refactor, the thing whose stakeholder is not in the room.

An edit has a name in it

Treated as what it is — an edit to the existing plan — the mid-quarter ask forces one specific piece of honesty: naming the commitment it displaces. Not "the team will absorb it", which is a displacement with the victim chosen later, but a sentence with an object in it: the audit-log project moves three weeks. And the person who was promised the displaced work hears it that day, from you, with the reason — not at quarter end, by inference, when the slip surfaces on its own. The displaced commitment does not vanish; its date moves or its scope shrinks, visibly, on the record.

Urgent pays the exception

An urgent commitment, by definition, usually skips the shaping a promise normally clears — there was no time to size it properly, confirm its dependencies, or write down its unknowns. That is exactly why an urgent commitment made before the work is ready always carries a recorded exception, with four fields: why it is being committed early, what evidence is still missing, who accepts the risk, and what condition would change the decision. It is a minute of writing, and it is not friction for its own sake. The exception is what makes the mid-quarter yes countable later: a quarter with five urgent asks on the record is diagnosable — you can see who asked, what each one displaced, and how many landed. A quarter with five silent squeezes is just a quarter that "went badly".

A worked example

Sofia runs the platform group at a fintech. In week seven, legal arrives with a data-retention change and a regulator date eleven weeks out. The old version of this conversation is capitulation with resentment: yes, of course, somehow — followed by a quarter-end surprise about the audit-log project nobody explicitly decided to delay.

Sofia's version has three moves. First, the edit: the retention work lands on the same team as the audit-log project, so the audit-log project is the thing being edited — its delivery moves three weeks, and the finance director who was promised it hears that from Sofia the same afternoon, with the regulator letter as the reason. Second, the record: the retention work is committed on the urgent path with its exception — the regulator's date is the why, scope confirmed with legal only at headline level is the missing evidence, the CTO's name is on the risk, and "the regulator extends the deadline" is the condition that would change it. Third, nothing else moves: the other commitments keep their dates, because the subtraction was taken from one named place instead of a little from everywhere.

At quarter end the record shows two urgent asks, both with exceptions, one displacement each — and the audit-log slip has an explanation attached, dated week seven, instead of being discovered.

The team whose yes has an address

None of this makes a team slower to say yes. Sofia said yes to legal inside a day. What it changes is that the yes is legible: this, instead of that, accepted by them. The alternative — absorbing the ask into overtime and optimism — feels more accommodating for about five weeks, until the things it silently taxed come due at once. A team that edits in the open can take urgent work every quarter and keep its word. A team that only adds cannot do either for long. How commitments get made, displaced and counted is the subject of the commitment overview.