Blocks / Impedes
The source prevents the target from being achieved.
Definition
A blocks arrow says that the source prevents, hinders, or impedes the target. It is stronger than influence: the target cannot be fully achieved while the source is present.
Diagram as text: A problem blocking an outcome
Nodes:
- Root / Problem: "Lack of trust between teams"
- Root / Problem: "Teams hide problems from each other"
- Desired State / Outcome: "Teams solve problems together"
Arrows:
- "Lack of trust between teams" influences "Teams hide problems from each other"
- "Lack of trust between teams" blocks "Teams solve problems together"
- "Teams hide problems from each other" influences "Teams solve problems together"
Direction
From the blocker to the blocked node. The arrow points at what is being prevented, usually a desired state / outcome.
When to use it
During refinement, when the group is analyzing what stands between them and their goals, and the blocking nature of a relationship is central to that analysis.
If calling it "blocks" instead of "influences" would not change what the group does, keep the plain arrow.
Blocking arrows also appear in one variant of the blocked outcomes view, which lists each outcome with only the problems that block it.
How to draw it
A dashed line with a filled arrowhead. Add it to the legend as soon as the first one appears.
Examples
- "Deployment complexity" blocks "Rapid iteration"
- "Lack of trust between teams" blocks "Cross-team collaboration"
- "Technical debt in core systems" blocks "Fast feature development"
Required or optional
Optional. Use it when it sharpens the analysis.