Essay · capacity

The cost of a no lands somewhere else.

Nobody deletes the work when the headcount is declined. The cost moves onto budgets the person who declined is not measured on.

The staffing request comes back declined. The calendar does not change.

Next week still has the same intervals on it, against the same forecast, and the work those people were going to cover is still sitting inside them. The decision changed a budget. It did not change the queue.

The saving is easy to find. One line, one budget, one owner's name beside it, and it gets reported. The cost never lands anywhere in particular. It arrives in pieces, on other people's sheets, across the following weeks.

The decision has one address. The bill has several.

Where the money actually went

Follow the pieces to the sheets they land on.

Premium hours land in the operations budget in a different month, coded as overtime rather than as headcount, which is how a staffing cost gets filed as an execution problem. A shift somebody was asked to move lands on that person. Nothing was spent, and something was drawn down anyway. An operation can only ask so many times before the answer changes.

A coaching block that came off the calendar lands on an agent who has now been told twice that this week is the week, and then on the leader who has to tell them a third time. Development time goes first when a schedule tightens, and nobody counts it going, because the cost arrives later and lands on someone else's line.

Work that did not finish inside its interval crosses into the next one and arrives looking like new volume. Nothing on the sheet marks where it came from.

None of that reaches the budget that recorded the saving. The decline was real and the arithmetic behind it was probably sound as far as it went, but the line it saved and the lines it spent are kept by different people and reconciled by nobody. Attrition is the slowest item on the list, arriving quarters later as a hiring line nobody connects to a staffing conversation. The canceled coaching block and that hiring line are the same money reaching the operation by two routes. That chain is long enough to need its own argument.

The levers already have names

The cost is countable, and it depends on a sheet written before the shortfall arrived.

Nothing on the sheet is clever. Each move on it carries five things: what the move is, who can authorize it, what condition triggers it, what the operation owes back afterward, and what changed the last time it was pulled. Premium hours carry a name and an hour of the day past which buying them stops being worth it. Borrowed capacity is written down with its repayment attached, because capacity borrowed from development is taken off somebody's calendar, and that debt comes due whether or not anyone recorded it.

The fifth item is the one that gets dropped. It is also the one that makes the other four worth writing down. Without it the sheet is a runbook, and a runbook only tells you what you are permitted to do. With it the sheet accumulates prices, and a price is the thing you can quote back when the next request arrives.

The moves are ordered, cheapest first, and the last one on the list puts the cost onto the customer. Read that order forward and it is a price list for a decline. Whoever says no is choosing a position on it, usually without knowing the list exists.

Against that sheet, a decline reads as a forecast: these moves, roughly this often, at these authorities, with these repayments owed. Every item already carries a name and an owner somebody agreed to in advance, so none of it has to be argued from first principles in the room.

The record that works when the answer is yes

The person receiving the request is usually not the person holding the money. They decide whether it reaches the room where the money is.

What they are being asked to spend is their own credibility, on somebody else's argument, in a room where they will be the one standing there. The question in their head is not whether the number is right. It is whether they will be embarrassed for having let it in.

A single ask with a consequence attached reads as a threat whether or not it was meant as one. What travels better is a set of options, each carrying the operational result it produces and the consequence somebody would be accepting by choosing it. That hands the gatekeeper something other than my recommendation to carry. They can walk in, lay the trade out, take a different option than the one I argued for, and the sheet still holds.

This sits one degree from a paper trail, and everybody can smell the difference. A document produced later, when things have gone badly, so that a signature can be pointed at, is a blame instrument. Nobody is fooled and nobody forgets who wrote it.

So the test before writing one: what is this worth on the day everything goes fine? If the smaller number turns out to have been the right call, the same record should say so, with the approver's name against a correct decision. A record written afterward, by one party, with no agreed check in it, is the thing a skeptic is right to worry about, but a record written before, carrying both sides' assumptions and a date to reopen them, is doing a different job.

The clause that makes it honest

One objection survives all of that, and it is the good one. The consequence is a projection. I do not know that the attrition arrives, or that the development time gets canceled as often as the model says. Somebody signs the list, the quarter runs fine, and their credibility has paid for insurance against something that never showed up.

The answer goes in at the time of the ask and nowhere else. Name the evidence being watched, name the week it gets read, and say out loud that if it has not moved by then the model was wrong and you will say so.

That sentence is what separates disclosure from coercion. It also moves the reputational bet onto the person making the ask, which is where it belongs. They are the one claiming to know something.

What would change my mind: an operation that writes the levers down, prices its declines, runs the checks on schedule, and finds that the priced consequences keep failing to appear. That would mean the pricing is reading its own assumptions back to itself, and the honest move then is to retire it. The check costs a calendar entry. Run it on a decline of your own before carrying one into somebody else's room.

Want to talk about this? Email me.