Standard : Decision Lead Time

Description

Decision Lead Time measures the average time between a decision being needed and a decision being made — identifying bottlenecks caused by unclear decision rights, insufficient information, or over-centralised authority. Slow decisions are a form of organisational friction that accumulates silently: each delayed decision blocks downstream work, erodes team momentum, and signals to the organisation that moving quickly is not a genuine value.

This measure is particularly sensitive to structural factors: when decision rights are unclear, decisions escalate. When authority is over-centralised, decisions queue behind leadership bottlenecks. Decision Lead Time makes these structural issues visible and quantifiable.

How to Use

What to Measure

  • Date on which a decision need was first identified and surfaced (meeting record, written request, or decision register entry)
  • Date on which the decision was formally made and communicated
  • Elapsed time in working days
  • Reason for delay where lead time exceeds benchmark: missing information, escalation, approval chain, consultation requirement, or competing priorities

Formula

Decision Lead Time = Average (Decision Made Date − Decision Need Identified Date) across tracked decisions (in working days)

Optional:

  • By decision type: separate lead times for people decisions, investment decisions, strategic decisions, and operational decisions
  • By escalation level: compare lead times for decisions made at team level versus those escalated to senior leadership

Instrumentation Tips

  • Create a decision register or use project management tooling to capture decision requests and outcomes with timestamps
  • Define the decision need identification event clearly — the moment a team or stakeholder formally signals a decision is required, not when leadership first becomes aware of the underlying issue
  • Track decisions that are pending for longer than the benchmark and review them in weekly leadership meetings
  • Report median lead time rather than mean to reduce distortion from a small number of very long-delayed decisions

Benchmarks

Lead Time Interpretation
Under 2 working days (operational) Excellent — decisions are rapid; authority is appropriately delegated
2–5 working days (operational) Good — reasonable for decisions requiring consultation or evidence gathering
5–15 working days (strategic) Good — appropriate for complex decisions with significant consequence
Over 15 working days (operational) Poor — decisions are bottlenecked; authority or process investigation needed

Why It Matters

  • Delayed decisions are a hidden tax on team performance Every decision that is pending blocks downstream work and forces teams into waiting, workarounds, or premature action based on assumed outcomes — all of which create waste and rework.

  • Decision lead time reveals authority distribution health Long lead times concentrated in specific categories reveal where decision authority is over-centralised — enabling targeted intervention through decision rights clarification rather than generic urgency.

  • Slow decisions signal risk aversion that can paralyse innovation Organisations with long decision lead times create cultures where people avoid surfacing decisions until they become crises — suppressing the early signals that enable preventive action.

  • Fast decisions build execution momentum Teams that receive timely decisions maintain flow and momentum. Teams that frequently wait for decisions lose energy, fill gaps with low-value work, and develop learned helplessness around initiative.

Best Practices

  • Create and communicate a decision rights framework (e.g. RACI, DACI, or RAPID) that specifies who can make which categories of decision without escalation
  • Implement a decision SLA: define the expected lead time for each category of decision and make adherence visible
  • Empower team leaders to make operational and tactical decisions independently without seeking approval from senior leaders
  • When a decision escalates, capture why — over time, escalation patterns reveal where decision rights need to be redistributed
  • Conduct regular decision rights reviews to update authority levels as team capability and trust grow

Common Pitfalls

  • Conflating decision quality with decision speed — fast bad decisions are worse than thoughtful slow ones; the goal is appropriately fast decisions with sufficient evidence
  • Measuring only the decisions that reach senior leadership, missing the larger population of decisions that are delayed at team level
  • Accepting long decision lead times for categories that genuinely could be delegated to lower levels
  • Using decision lead time as a metric that incentivises hasty decisions without sufficient evidence to meet SLA targets

Signals of Success

  • Teams can make the vast majority of day-to-day decisions independently without escalation or approval-seeking
  • When escalation is needed, it happens rapidly and the senior leader makes a timely decision with clear communication
  • Decision lead times are compressing over consecutive quarters as decision rights become clearer and team authority grows
  • The organisation experiences fewer project delays attributable to pending decisions
  • [[Decision Reversal Rate]]
  • [[Evidence-Based Decision Coverage]]
  • [[Decision Escalation Rate]]
  • [[Strategy-to-Execution Lag]]

Aligned Industry Research

  • Turn the Ship Around (L. David Marquet, 2013) Marquet's account of leadership transformation on USS Santa Fe demonstrates that pushing decision authority to the lowest appropriate level dramatically reduces decision lead time and increases both execution quality and team engagement.

  • Team of Teams (Stanley McChrystal, 2015) McChrystal's account of redesigning military decision-making for complex environments demonstrates that structural investment in distributed decision authority is essential for achieving competitive decision speed in fast-moving contexts.