Decision dependency count
How many other decisions or entities a decision depends on or feeds.
Formula
Decision dependency count
count(upstream decisions + downstream decisions + affected systems + policies + owners)
Unit
count
Direction
Context dependent
Cadence
For high-impact decisions before approval.
Worked Example
Pricing decision dependency review.
Upstream decisions
4
Affected systems
6
Policy checks
3
Calculation
4 + 6 + 3
Result
13 dependencies
Interpretation
This decision needs explicit sequencing and orchestration.
Recommended action
Create a dependency map before final approval.
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 a decision sits inside a broader chain of commitments and constraints.
Manual assessment method
Map upstream decisions, downstream decisions, affected systems, owners, policies, and workflows for a critical decision.
Lapemo calculation path
Supported by parent-child decision links and downstream entity references when decision lineage is captured.
Interpretation Bands
Healthy
Low and declining
Gaps are being removed on cadence.
Watch
Flat
The operating model is not improving.
Risk
Rising
Debt is accumulating faster than teams are resolving it.
Critical
Concentrated in critical work
Escalate for owner action.
Required inputs
- Decision record
- Upstream/downstream links
- Affected systems
- Policies
- Owners
Data sources
- Decision log
- Architecture map
- Control map
- Platform inventory
Common pitfalls
- Treating high dependency as bad by default
- Missing downstream operational effects
Recommended actions
- Map sequencing
- Assign dependency owners
- Review downstream impacts
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.