Tree of Influence
Menu: Reference

Arrow styles

The default arrow and the optional refined styles.

The default arrow

Every connection starts as a solid line with a filled arrowhead, pointing from source to target. It means "this influences, leads to, or has some effect on that."

Use it for every connection during construction. If a tree uses only this arrow and nobody feels the need for more, the tree is complete.

Refined styles

During refinement, a group may decide that some connections deserve a different line. Two refined styles are available.

The 3 arrow styles Notation samples. A text version follows the diagram. Influences The default arrow Blocks / Impedes Prevents the target Attacks An artifact targets a problem
Diagram as text: The 3 arrow styles
  • Influences arrow, solid: the default arrow.
  • Blocks / Impedes arrow, dashed: prevents the target.
  • Attacks arrow, dotted: an artifact targets a problem.
Relationship Line Points from, to Use it when
Influences Solid Cause to effect Always, by default
Blocks / Impedes Dashed Blocker to blocked node The source prevents the target, and that matters to the analysis
Attacks Dotted Artifact to the problem it targets An artifact explicitly aims to resolve a problem

Here is a small tree that uses all three:

A tree that uses every node type and arrow style 5 nodes and 5 arrows: 2 root / problem, 1 action / intervention, 1 artifact / deliverable, 1 desired state / outcome. A text version follows the diagram. [P]Documentation isout of date [P]Setting up alaptop takes aweek [A]Write a one-pagestarter guide [D]One-page starterguide [O]New hires shipsomething intheir firstmonth Legend [P] Root / Problem [A] Action / Intervention [O] Desired State / Outcome [D] Artifact / Deliverable Influences Blocks / Impedes Attacks Flow: roots (bottom) → outcomes (top).
Diagram as text: A tree that uses every node type and arrow style

Nodes:

  • Root / Problem: "Documentation is out of date"
  • Root / Problem: "Setting up a laptop takes a week"
  • Action / Intervention: "Write a one-page starter guide"
  • Desired State / Outcome: "New hires ship something in their first month"
  • Artifact / Deliverable: "One-page starter guide"

Arrows:

  • "Documentation is out of date" influences "Write a one-page starter guide"
  • "Write a one-page starter guide" influences "One-page starter guide"
  • "One-page starter guide" influences "New hires ship something in their first month"
  • "One-page starter guide" attacks "Documentation is out of date"
  • "Setting up a laptop takes a week" blocks "New hires ship something in their first month"

When to add a style

Introduce a second line style only when the group brings it up and agrees that the distinction matters. Do not introduce it in advance.

A useful rule of thumb: one style is fine. Two means something real surfaced. Three means you are probably classifying the diagram instead of understanding the problem.

"Leads to" and "causes" are drawn with the same solid line as "influences." The difference between them lives in the conversation, not in the lines. Drawing a separate style for every shade of meaning adds noise without adding insight.

No two-headed arrows

Every arrow has exactly one head. If two nodes seem to influence each other, do not draw a two-headed arrow. Look for a hidden cause between them instead. See cycles and graph shape.