VS-05
High Fan-Out Node — Single Issue Blocking Many
Value Stream Graph
Default severity: medium
PrioritizationProcessOutputRisk
What it detects
A single issue (node) is a dependency predecessor for more than the configured number of other issues — it is a high-fan-out blocker whose delay will cascade to many downstream items. Highest risk nodes in the graph.
Detection formula
FOR each_node N: downstream_count = COUNT(nodes reachable from N via dependency edges) IF downstream_count > config.graph.fan_out_warning_threshold // default: 5 THEN FLAG IF downstream_count > config.graph.fan_out_critical_threshold // default: 10 THEN CRITICAL — identify as critical_path_nodeExamples in practice
- Dependency links or initiative graph paths are missing, cyclic, or blocked.
- Downstream work waits on unresolved upstream dependencies.
- A team shows a single issue (node) is a dependency predecessor for more than the configured number of other issues while fan out warning threshold is set to 5.
Suggested response
Repair dependency and initiative graph links so delivery paths and handoffs are explicit.
Coaching playbook
Symptom
A single issue (node) is a dependency predecessor for more than the configured number of other issues — it is a high-fan-out blocker whose delay will cascade to many downstream items. Highest risk nodes in the graph.
Why it matters
When "High Fan-Out Node — Single Issue Blocking Many" 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 "High Fan-Out Node — Single Issue Blocking Many" 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.