Know what you are paying for.
The Five Capacity Taxes: Where the Cost of a Stalled Result Lands
Execution drag is the gap between the performance you pay for and what your operating conditions let people deliver. Skill is on the payroll. Access to it is not on any report. The Five Capacity Taxes are where that gap turns into cost. Three of them you can see in the work. The other two take evidence a 90-minute session can't produce, so they are handled differently, and the difference matters once the number reaches the executive who wasn't in the room.
A Tax can carry cost from the route itself, from the people on it having less access to their own judgment, or from both at once, which is the usual case. They overlap. The examples below are the kind of thing that makes us look harder, not a diagnosis.
01
Meeting Tax
Coordination Cost
What It Is
Coordination that eats production time. Meetings, alignment, checking, the message thread that stands in for a decision. The meetings are not the problem in themselves. The problem is that after enough of them there is no protected stretch left in which to do the work they were about.
What It Looks Like
Eight meetings on a Wednesday, three action items, forty unread messages, and a deliverable due Thursday. It goes out late, or on time with errors in it.
02
Decision Density Tax
Quality & Rework Cost
What It Is
Consequential decisions that stack up, get delayed, get escalated, or all run through the same two people. Wait, reversal, and cleanup follow. A single bad call under pressure tells you nothing on its own. Several of them, on the same kind of week, start to.
What It Looks Like
A proposal reviewed late in a heavy week goes out with a pricing error. The revision is the direct cost. The question worth asking is whether that kind of miss keeps showing up under the same load.
03
Manager Load Tax
Delay & Queue Cost
What It Is
Work, approvals, escalations, and exceptions all routed through one manager. The queue slows everything behind it, and the constant switching wears down the manager's judgment, which shows up as more caution, more review, and a longer queue. The two feed each other.
What It Looks Like
Finished on Monday, sent for review, back on Thursday. By then both people have to rebuild the context before anyone can move it.
04
Recovery Debt Tax
Attrition & Turnover Exposure
Separate exposure · Estimated only with longitudinal and turnover evidence
What It Is
Attrition exposure from sustained demand with no recovery built into it. You will not see it in one hard week or one resignation, which is why it needs turnover and longitudinal data before anyone should put a number on it.
What It Looks Like
Three delivery sprints back to back with no lighter period between them. Output slows, review cycles stretch, after-hours work stays high. That is enough to make us look, but not enough to put a figure on, and we won't.
05
Forfeited Upside Tax
Missed Future Value
Separate opportunity exposure · Client-supplied · Never added automatically
What It Is
The future value that never arrives because strategic work, customer signals, and half-formed ideas get no protected capacity and no route to action. It can only be valued from your pipeline and your assumptions, and it stays on its own line.
What It Looks Like
An account lead notices an upsell pattern. Every signal goes into the same overloaded queue as everything else. Three months later the client brings the idea to a competitor.
What the Snapshot does with the Taxes
The Stalled Priority Snapshot traces one result that should have moved. Ninety minutes, with the people who move, approve, or unblock it in the room. The read names the work-path pattern before it says anything about Taxes. Then the Tax comes in as the associated exposure, stated on its own, separate from the causal finding. It is possible to run the session and find that the route isn't the explanation at all: the outcome was never properly defined, or a vendor is setting the pace. When that happens the read says so and no Tax gets named.
The number is extra labor you can trace, with the arithmetic and the confidence level on the page. Elapsed delay is reported in days beside it, not priced into it. The Taxes are not added to each other, and nobody on the route is assessed.
Screened from path evidence
Meeting Tax · Decision Density Tax · Manager Load Tax
Waits, queues, approvals, handoffs, rework, and meeting cycles are all visible on a single route. That is enough to connect the pattern to one of these three and to design the 14-day test.
Held as downstream exposure
Recovery Debt Tax · Forfeited Upside Tax
Recovery Debt needs turnover and longitudinal data, so a Snapshot can flag it and that is all. Forfeited Upside is different. If you give us the basis, we show it, on its own line, marked as your assumption. Northline's came to about $7.5M and it never touched the labor range.
In the sample read the pattern was serial gating and the exposure was Manager Load Tax, with roughly 60 percent of the elapsed life spent in a queue. The full method, including how the Capacity Audit prices exposure with overlap controls, is in the Execution Drag white paper.
Trace the route. Name the pattern.
Show the exposure. Test one change.
Bring one result that should have moved by now. You leave with the route it actually takes, the hours you can defend, and one change to test in the next two weeks.