Decision latency
The time it takes a decision to move from raised to decided and executed.
Formula
Raised-to-decided cycle time
average(decided timestamp - raised timestamp)
Unit
days
Direction
Lower is better
Cadence
Monthly by decision type.
Numerator
Total elapsed days across decisions
Denominator
Number of decisions sampled
Worked Example
Portfolio team samples 20 consequential decisions from the last month.
Total elapsed days
210
Decisions sampled
20
Calculation
210 / 20
Result
10.5 days average latency
Interpretation
Decision flow is slow enough to affect execution cadence.
Recommended action
Segment latency by decision type and inspect owner coverage for the slowest group.
Why it matters
This metric helps leaders see whether the decisions layer is healthy enough to support execution and AI readiness.
What it reveals
Where execution is slowed by delayed, unresolved, or poorly governed choices.
Manual assessment method
Select a decision sample and record when each decision was raised, decided, communicated, and executed.
Lapemo calculation path
Supported by decision timestamps; derivation can calculate raised-to-decided and decided-to-executed time.
Interpretation Bands
Healthy
Within decision-type SLA
Decisions move at the expected cadence.
Watch
1-25% over SLA
Inspect repeat delays.
Risk
26-75% over SLA
Decision debt is slowing work.
Critical
>75% over SLA
Escalate decision architecture redesign.
Required inputs
- Decision raised date
- Decision date
- Decision type
- Decision owner
Data sources
- Decision log
- Meeting notes
- Governance workflow
- Product intake board
Common pitfalls
- Mixing strategic and operational decisions
- Ignoring decided-to-executed lag
Recommended actions
- Clarify decision rights
- Create decision SLAs
- Review aging decisions weekly
Measure Before You Scale
Measure the operating model before AI amplifies it.
Use the Metrics Library to understand what to diagnose, what to monitor, and where Lapemo can turn framework metrics into operating intelligence.