The Slow Yes: How Approval Queues Tax Your Strategy
Photo: Ash Carter, Public domain, via Wikimedia Commons
Strategy reviews tend to fixate on execution velocity. Teams are asked to move faster, launch sooner, and compress timelines. Yet in many US enterprises, the binding constraint is not the speed of work. It is the elapsed time between a well-formed proposal and a clear yes or no. That gap is decision latency, and it behaves like a tax on strategy: quiet, cumulative, and rarely assigned to anyone’s budget.
The tax is easy to miss because it does not appear as a line item. It shows up as a pricing change that reaches the market a quarter late, a capital request that sits through two planning cycles, or a vendor contract that expires before the approval chain finishes. The work was ready. The decision was not.
Where the tax hides: the approval queue
Every organization has decision queues, but few have a map of them. A request enters through a business sponsor, then moves to finance, legal, security, procurement, and perhaps a regional president. Each handoff introduces a wait. The org chart shows authority. The queue shows reality.
To find the tax, trace one decision class end to end. Pick something frequent and consequential: pricing exceptions, software purchases above a threshold, sales contracts with nonstandard terms, or headcount requisitions. Record the timestamp at intake, at each reviewer, and at final disposition. Do not rely on recollection. Calendar invites and email threads are not an audit trail.
The pattern is usually consistent. Actual review time is short. Waiting time is long. A legal reviewer may spend twenty minutes on a contract that waited nine days for routing. A finance analyst may clear a business case in an hour after it sat for three weeks awaiting a sponsor’s attention. The queue, not the analysis, is the constraint.
A ledger for delay: calculating the cost
Decision delay can be priced without pretending to be precise to the dollar. The goal is comparability, not accounting perfection. Build a simple ledger for each decision class: value at stake, weeks of delay, and the rate at which value erodes or opportunity cost accrues.
Consider a pricing change expected to add $400,000 in monthly contribution margin. If the approval chain adds six weeks, the delay consumes roughly $550,000 of value before the first invoice reflects the new price. A $3 million capital request that sits for a quarter may not lose $3 million, but if the project returns 12 percent annually, the wait carries an economic cost of about $90,000. Add rework when market conditions shift and the proposal must be revised, and the ledger grows.
Three components matter. Carrying cost is the value that leaks while a decision is open. Opportunity cost is the alternative foregone because resources remain committed to the status quo. Rework cost is the effort required to refresh a stale proposal. Most finance teams can estimate all three from data they already hold. The exercise is less about precision than about making the invisible visible.
Three KPIs that make delay visible
Once the ledger exists, decision-cycle KPIs can turn latency into a managed operating metric. Three are enough to start.
First, measure decision cycle time by class, using median and 90th percentile rather than averages. Averages hide the tail, and the tail is where strategy stalls. A median of eight days with a 90th percentile of forty days tells a different story than a mean of twelve.
Second, track the queue ratio: active review time divided by total elapsed time. A ratio of 0.15 means the request is being worked on 15 percent of the time and waiting 85 percent of the time. That single number often reframes the conversation from “people are slow” to “the process is holding inventory.”
Third, maintain an aged decision inventory. Count open decisions past their agreed service level, grouped by owner and decision class. This is decision debt. Like technical debt, it compounds. Unlike technical debt, it rarely appears on a dashboard.
Designing the fix: fewer gates, clearer rights, shorter clocks
The remedy is not to rush consequential decisions. It is to remove unnecessary gates and make the remaining ones accountable. Start by naming a single accountable owner for each decision class. Committees can advise; someone must decide. Then set threshold-based delegation so that low-risk, reversible decisions do not climb the same ladder as irreversible ones.
Publish service levels for each review function and instrument them. If legal commits to three business days for standard contract language, measure it. If finance commits to five days for business cases above a threshold, measure that too. Review the queue monthly, not the decision quality alone. Both matter, but only one is usually visible.
Finally, distinguish reversible from irreversible choices. Reversible decisions can tolerate faster clocks and lighter review. Irreversible ones deserve deliberation. Applying the same approval weight to both is how organizations teach people to avoid proposing anything at all.
What to do Monday
Pick one decision class with high volume and visible strategic value. Instrument its queue for thirty days. Calculate the cost of delay with a simple ledger. Set one cycle-time KPI and one aged-inventory KPI. Bring the results to the next operating review.
The point is not to shame slow reviewers. It is to show that strategy does not lose momentum only in failed execution. It also loses momentum in the slow yes, the unanswered request, and the queue that no one owns. Measuring decision latency turns a hidden tax into a managed line item, and that is where improvement begins.
