Decision Latency

Decision latency is the time a meaningful decision spends between being raised and being acted on, treated as a measurable P&L cost rather than a soft culture problem. Slow decisions look like caution. In practice, they are hidden expense. Every day a real decision sits unresolved, the business pays in delay, rework, and attention. A team can look productive and still be dragging the business down if every meaningful decision takes too long.

What it exposes

Decision latency shows up as stalled launches, expired opportunities, duplicated work, and growing frustration in the teams closest to the customer. When leaders do not measure it, they blame execution when the real problem is delay.

The underlying failure is implicit authority. Nobody knows who can make the call, so everyone escalates, and a simple operational decision takes a day instead of an hour because it bounces between three people who each assume someone else owns it. Ambiguous ownership is the most expensive architecture in your company.

It also exposes why headcount fails as a fix. Headcount is an input; throughput is an outcome. Adding engineers to a system that takes weeks to decide adds more waiting, not more output.

How to use it

Track four numbers with the same seriousness as revenue:

• time from issue raised to decision made
• time from decision made to action taken
• escalations per decision class
• decisions reopened after approval

Once those numbers are in the open, patterns become hard to deny: which teams move fast, which questions keep getting rerouted, where the organization burns time on decisions that should have been routine.

Then reduce it: define who owns each decision class, set decision boundaries before the crisis, reduce the number of people required for routine calls, and make escalation fast when the decision is truly material. Review decision latency weekly alongside cycle time, change failure rate, and recovery time. For the board, decision latency maps to organizational agility: “strategic decisions take 2 days to reach execution, not 2 weeks.”

Essays

• Decision Latency as a P&L Variable: The Leadership Metric Nobody Owns
• The Throughput Engineer: Why Headcount Is a Lagging Metric

Questions

How do you measure decision latency?

Track four numbers: time from issue raised to decision made, time from decision made to action taken, escalations per decision class, and decisions reopened after approval. Make them visible — once they are in the open, patterns become hard to deny.

How do you reduce decision latency?

Define who owns each decision class, set decision boundaries before the crisis, reduce the number of people required for routine calls, and make escalation fast when the decision is truly material. Routine decisions should be quick; risky decisions should be explicit.

Why is decision latency a P&L variable?

Every day a real decision sits unresolved, the business pays in delay, rework, and attention — stalled launches, expired opportunities, duplicated work. Slow decisions look like caution, but they are hidden expense.