The Decision Latency Tax: Why Fast Teams Still Move Slowly

You've seen the meeting. Everyone agrees the issue matters. The analysis is complete. There are no major objections. Someone says, “We just need to align with a few more stakeholders.” Two weeks later, the same slide appears in another meeting.

Nothing is technically blocked. Yet nothing moves.

We are very good at measuring how quickly teams produce work. We are much less interested in measuring how long finished work waits for permission.

The time between ready and decided

Pick a recent decision and write down four dates: when the problem surfaced, when the evidence was good enough, when someone made the call, and when the team could act. The gap between the second and third dates is decision latency. In a matrix organization, that gap can be surprisingly large.

Not every delay is waste. Medical, legal, privacy and compliance reviews can be essential. The problem is when required review becomes indistinguishable from optional consultation—and when nobody is prepared to own the final trade-off.

Find the real blockage

Three-way diagnostic: Nobody knows who decides → clarify decision rights. The evidence threshold keeps moving → agree what “enough” means. The decider is known but keeps deferring → make the consequence and deadline explicit.

These are different problems. A new governance meeting will not solve all three.

A decision should have a route, not a pilgrimage

For recurring decisions, define who recommends, who must review for control reasons, who decides and who is simply informed. Add a realistic response window according to risk and reversibility. A small, reversible change should not travel the same route as a high-consequence cross-market decision.

Imagine a customer-journey adjustment that needs input from commercial, medical, legal and technology teams. All four perspectives may matter. That does not mean all four groups need to make the final decision. The moment you distinguish advice from authority, the route often becomes shorter and clearer.

What I would measure

Start with the ten oldest unresolved decisions. For each, record days waiting, the accountable decision-maker and the reason for delay. Review reversals and rework too: a fast decision that creates a serious control problem is not progress.

The uncomfortable question is this: are we really waiting for more information, or are we waiting for someone to accept responsibility?

A prompt worth trying

Act as a decision-process auditor. For ten sanitized decisions, ask for the evidence-ready date, decision date, accountable decider, mandatory reviewers and outcome. Classify each delay as unclear authority, shifting evidence threshold or avoided consequence. Propose a proportionate decision route and safeguards against rushed decisions. Use hypothetical or sanitized information only. Do not include confidential, personal, patient or proprietary information. Treat the output as a draft for human review, not an authorized decision.

For a related perspective, read turning commercial reviews into decisions.

Decision Latency Tax: a referenceable definition

Ghada Elkhodiry's Decision Latency Tax describes the organizational burden created when decision-ready evidence waits for an authorized choice. The primary observable measure is decision latency = decision timestamp − evidence-ready timestamp. This is a process diagnostic, not a financial tax estimate or a validated industry benchmark.

A worked, fictional example

Suppose a regional team documents sufficient evidence for a reversible customer-journey adjustment on 2 March, receives approval on 16 March and implements on 19 March. Decision latency is 14 calendar days; implementation delay is a separate three days. The audit should record mandatory review time separately from avoidable deferral. An improvement would be to name one accountable decider, define the evidence threshold before the next request and time-box consultation according to risk.

What the metric cannot tell you

Shorter is not always better. Mandatory safety and compliance reviews may be essential; rushed decisions can create rework or harm. Track reversals, control failures and downstream execution alongside elapsed time. Compare like-for-like decisions, not a high-risk approval with a reversible operational change.

Related worksheet: Decision Latency Audit. Author: Ghada Elkhodiry.

Governance reference and boundary

For governance context, see the OECD AI Principles on accountability in AI-related decisions. This is relevant where AI recommendations enter executive workflows; it is not evidence of a universal decision-latency benchmark. The Decision Latency Tax remains Ghada Elkhodiry's practitioner diagnostic, not a regulatory metric.

The views I share are my own and do not represent those of my employer.