The Decision Latency Problem: How Much Does a Slow Company Lose?

Companies admire fast competitors while approving through five layers. Decision latency is the elapsed time from question asked to decision committed — not announced, committed with budget and owner.

Constrange indexes decision latency by type: pricing exception, hire, product launch, vendor switch, strategic pivot. Latency varies by type; aggregate averages lie.

Decision Cost models economic loss as Opportunity times Delay — rough but directional. Unmeasured latency feels like culture. Measured latency becomes a redesign project with ROI.

Where latency hides

Waiting for perfect information is the polite form of delay. Most decisions need sufficient information, not complete.

Consensus culture adds sequential approvals without parallel work. Each layer waits for the previous layer to polish slides.

Escalation without default — if no decision by date X, outcome Y — allows passive veto.

Formula showing decision cost as opportunity multiplied by delay — Decision Cost = Opportunity × Delay — measure both terms.

Decision Latency Index — example targets
Decision type	Median latency	Cost driver
Pricing exception	Under 5 days	Lost deal or excess discount
Standard hire	Under 21 days	Vacancy cost, project slip
Product launch go/no-go	Under 14 days	Competitor window
Vendor change	Under 30 days	Lock-in renewal
Strategic pivot	Under 45 days	Organisation thrash

Building the index

Timestamp decisions from request to commit in workflow tool or calendar audit. Sample monthly by type.

Interview decision requesters on outcome — deal lost, project delayed, cost incurred. Tag economic impact bands.

Publish median and ninetieth percentile — tail latency hurts more than median suggests.

Request date and commit date
Decision type taxonomy
Outcome tag — win, loss, neutral, unknown
Layers involved count

Redesigning governance

Delegate thresholds clearly — below X, manager decides; above X, forum with SLA.

Pre-approved rules replace case-by-case — discount bands, hire levels, standard architecture choices.

Decision forums with standing agenda slots — waiting for quarterly board kills deals.

Opportunity decay

Model decay for time-sensitive decisions — pipeline value times weekly slip probability.

Talent markets decay faster than sales pipelines. Slow hire decisions lose candidates to faster rivals.

Regulatory and seasonal windows are hard deadlines — latency past window equals zero opportunity.

“A delayed yes is often a no with extra meetings.”Constrange

Culture and accountability

Name decision owners, not recommendation owners. Recommendations without decision rights inflate latency.

Reward clean no's faster than slow maybes — ambiguity consumes more than rejection.

Retros on high-latency decisions quarterly — process fix, not blame ritual.

Default outcomes

Implement default-on-expiry — pricing reverts to standard, requisition expires, project proceeds with stated assumptions — to break passive blocking.

When slowness is correct

Irreversible high-blast-radius decisions deserve latency — capital structure, safety systems, major M&A.

Label slow types explicitly so fast types are not contaminated by same process.

Do not use irreversible argument for reversible operational choices — that is avoidance.

Questions worth putting in the next leadership review

Where does our data on decision latency and cost actually live — and who owns updating it?
What decision would we make differently if we trusted the number?
Which incentive or reporting line is working against the outcome we want?
What is the smallest test that would change our mind in ninety days?

Strategy work that stops at the slide deck is expensive theatre. The useful version is slower, messier, and more specific: name the constraint, measure the gap, assign an owner, and set a date when the number gets reviewed again.

Track calendar days in approval chains for top ten deals — sales feels latency before index exists.

Compare latency before and after pre-approval rules — ROI is often immediate.

Survey managers on decisions waiting over thirty days — queue visibility reduces latency.

Measure rework from reversed decisions — flip-flop is latency plus cost.

Publish decision SLAs internally — sunlight changes behaviour.

The numbers in this article are illustrative ranges from client work and published benchmarks — not universal laws. Your organisation will have its own shape. The discipline is to measure yours rather than borrow someone else's headline.

Finance, operations, and commercial teams often use the same words with different definitions. Before any index or ratio goes on a dashboard, agree what counts in the numerator and who certifies it monthly.

Boards respond to frameworks when they see a decision attached. Pair every metric with a threshold and a pre-agreed action. Measurement without a trigger is reporting; measurement with a trigger is management.

Avoid benchmarking envy. Another company's attractive ratio may reflect a business model you do not have. Compare yourself to your own prior quarters first; external peers second.

Short-term fixes that improve a ratio while weakening the underlying economics are more common than admitted. When a metric moves, ask what behaviour it rewarded and whether that behaviour survives a bad quarter.