Tree of Influence
Menu: Reference

The shortcut

The tree collapses into direct problem, action, outcome paths with no depth.

Description

The tree becomes a set of simple, direct paths: one problem, one action, one outcome. "Technical debt, so refactor, for better quality." Each path is valid on its own, but together they add nothing.

A tree made of shortcuts 6 nodes and 4 arrows: 2 root / problem, 2 action / intervention, 2 desired state / outcome. A text version follows the diagram. [P]Technical debt [A]Refactor [O]Better quality [P]Low morale [A]Team offsite [O]Improvedengagement Legend [P] Root / Problem [A] Action / Intervention [O] Desired State / Outcome Flow: roots (left) → outcomes (right).
Each path is valid, but the tree says nothing the group did not already know.
Diagram as text: A tree made of shortcuts

Nodes:

  • Root / Problem: "Technical debt"
  • Root / Problem: "Low morale"
  • Action / Intervention: "Refactor"
  • Action / Intervention: "Team offsite"
  • Desired State / Outcome: "Better quality"
  • Desired State / Outcome: "Improved engagement"

Arrows:

  • "Technical debt" influences "Refactor"
  • "Refactor" influences "Better quality"
  • "Low morale" influences "Team offsite"
  • "Team offsite" influences "Improved engagement"

Why it matters

The insight in a Tree of Influence lives in the structure between the ends: underlying causes, sub-problems, hidden dependencies, prerequisites. A tree of shortcuts looks complete but is no more useful than a to-do list. The group leaves knowing only what it knew when it walked in.

How to spot it

How to correct it

  1. Expand each path with questions:
    • For a problem: "What causes this? What makes it worse?"
    • For an action: "What does this involve? What has to be true for it to work?"
    • For an outcome: "What else contributes to this? What could prevent it?"
  2. Add the answers as new nodes, and redraw the arrows through them.
  3. Challenge assumptions: "What could go wrong? What are we taking for granted?"
  4. Pick one shortcut and run a 5-minute deep dive on it. The structure that emerges belongs on the board.

Here is the morale shortcut after asking "what causes low morale?":

One shortcut expanded with its causes 5 nodes and 5 arrows: 3 root / problem, 1 action / intervention, 1 desired state / outcome. A text version follows the diagram. [P]Prioritieschange everyweek [P]Wins are neverrecognized [P]Low morale [A]Team offsite [O]Improvedengagement Legend [P] Root / Problem [A] Action / Intervention [O] Desired State / Outcome Flow: roots (left) → outcomes (right).
Asking "what causes this?" surfaces the structure. The offsite now looks like a weak answer to the real causes.
Diagram as text: One shortcut expanded with its causes

Nodes:

  • Root / Problem: "Priorities change every week"
  • Root / Problem: "Wins are never recognized"
  • Root / Problem: "Low morale"
  • Action / Intervention: "Team offsite"
  • Desired State / Outcome: "Improved engagement"

Arrows:

  • "Priorities change every week" influences "Low morale"
  • "Wins are never recognized" influences "Low morale"
  • "Low morale" influences "Team offsite"
  • "Low morale" influences "Improved engagement"
  • "Team offsite" influences "Improved engagement"

The offsite is still on the board, but now everyone can see that it does not touch either cause.