VS-09
Critical Path Node With Low DoD Score
Value Stream Graph
Default severity: medium
PrioritizationProcessOutputRisk
What it detects
A node that lies on the critical delivery path (longest path from initiative root to any unfinished leaf) has a DoD score below the configured threshold — a planning/analysis gap on a critical path node puts the entire initiative timeline at risk. critical_path = find_longest_path(G, from=initiative_root, to=unfinished_leaves) // CPM algorithm
Detection formula
FOR each_node N IN critical_path: dod_score = compute_dod_score(N, config.dod.stages) IF dod_score \< config.graph.critical_path_min_dod // default: 0.7 THEN CRITICAL — node is on critical path AND underpreparedExamples in practice
- Dependency links or initiative graph paths are missing, cyclic, or blocked.
- Downstream work waits on unresolved upstream dependencies.
- A team shows a node that lies on the critical delivery path (longest path from initiative root to any unfinished leaf) has a dod score below the configured threshold while stages is set to 0.7.
Suggested response
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Coaching playbook
Symptom
A node that lies on the critical delivery path (longest path from initiative root to any unfinished leaf) has a DoD score below the configured threshold — a planning/analysis gap on a critical path node puts the entire initiative timeline at risk. critical_path = find_longest_path(G, from=initiative_root, to=unfinished_leaves) // CPM algorithm
Why it matters
When "Critical Path Node With Low DoD Score" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Facilitation questions
- What system change would stop "Critical Path Node With Low DoD Score" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.