Decision Latency

Chapter 20

Organisations rarely measure how long ambiguity survives.

They measure delivery dates, budget variance, uptime, defect rates, cycle time. They measure activity at the edges of execution. What they do not measure is the interval between when a consequential choice becomes visible and when authority closes it.

That interval is decision latency.

It is not the time required to write a document or hold a workshop. It is the duration between recognition and binding resolution. In healthy systems, this interval is bounded. In dysfunctional ones, it expands — and the expansion is rarely visible until cost has already accumulated.

As latency grows, three symptoms appear.

Parallel work increases. Teams proceed on assumption because clarity has not arrived. Multiple interpretations of the same constraint emerge simultaneously. Redundant analysis runs in parallel. The organisation appears industrious. It is compensating for delay.

Risk migrates outward. When a decision is not made centrally, it is made locally. Trade-offs that should have resolved at one altitude fragment across many. Coherence erodes not through rebellion but through necessity. Delivery pressure forces choice in the absence of formal resolution.

Escalation frequency rises. Questions that should have terminated below circulate upward. Senior leaders absorb a steady flow of issues that feel operational but are structural symptoms of latency they cannot see from altitude.

These are not cultural failures.

They are temporal ones.

Latency accumulates quietly. A week becomes a month. The decision, still technically open, shapes behaviour long before it is formally resolved. Dependencies harden. Positions polarise. By the time authority converges, the cost of convergence has already been paid — in rework, drift, and shadow decisions that filled the vacuum.

The absence of a decision is not neutral. It is a structural choice with compounding consequences.

Organisations often defend high latency as rigour. Complex problems require extended consultation. Sometimes true. But in most cases, what expands is not insight; it is surface area. Stakeholders are added because their exclusion carries political cost. The decision grows heavier as it moves, not sharper. Rigour becomes the alibi for drift.

Decision latency is therefore a leading structural signal.

When latency is short and bounded, ambiguity expires predictably. Teams know when clarity will arrive. Work sequences with confidence. Escalation becomes scarce because lower levels resolve what they are empowered to resolve.

When latency is long and elastic, ambiguity persists. Teams hedge. Local optimisations multiply. Authority becomes reactive. The organisation reads as cautious. It is structurally stalled.

The diagnostic is simple.

How many significant decisions remain open beyond thirty days?
How many revisit forums they have already passed through?
How many require more than one escalation before binding?

These are not performance metrics. They are structural readings.

High latency predicts downstream instability — exception growth, integration friction, burnout among those expected to deliver clarity without authority.

Low latency does not guarantee correctness.

It guarantees movement.

Velocity, at its structural core, is the rate at which ambiguity expires.

Where ambiguity has no defined lifespan, latency rules. Where latency rules, dysfunction is not visible in any single decision — it is distributed, systemic, and self-reinforcing.

Decision latency is not a by-product of complexity.

It is a property of design.