VS-10
Initiative Blocked at Single Point of Failure
Value Stream Graph
Default severity: medium
PrioritizationProcessOutputRisk
What it detects
The entire initiative\'s delivery graph converges through a single node — all paths from root to unfinished leaves pass through this one issue. If this node is delayed or blocked, 100% of the initiative is at risk.
Detection formula
FOR each_initiative I: G = delivery_graph(I) unfinished_leaves = \[N FOR N IN G.leaves IF N.status NOT IN terminal_statuses\] FOR each_node N IN G (excluding root and leaves): is_spof = all_paths(G, root, unfinished_leaves) contain N IF is_spof THEN CRITICAL single_point_of_failure Report: node key, owner, status, dod_score, ageExamples in practice
- Dependency links or initiative graph paths are missing, cyclic, or blocked.
- Downstream work waits on unresolved upstream dependencies.
- A team shows the entire initiative\'s delivery graph converges through a single node during analysis.
Suggested response
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Coaching playbook
Symptom
The entire initiative\'s delivery graph converges through a single node — all paths from root to unfinished leaves pass through this one issue. If this node is delayed or blocked, 100% of the initiative is at risk.
Why it matters
When "Initiative Blocked at Single Point of Failure" 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 "Initiative Blocked at Single Point of Failure" 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.