Tree of Influence

A diagramming and facilitation technique for mapping how problems, actions, and desired outcomes influence each other.

A tree made of sticky notes: brown paper roots and trunk, a canopy of green notes, and a few indigo notes among the leaves.

A Tree of Influence is a map of a complex problem space, drawn with sticky notes and arrows. An individual or group of people builds it, and the conversation it creates is the point: people see how their problems connect, find shared causes, and agree on what matters before deciding what to do.

A Tree of Influence about onboarding new hires 8 nodes and 7 arrows: 3 root / problem, 3 action / intervention, 2 desired state / outcome. A text version follows the diagram. Leaves Desired state / outcome Branches Action / intervention Roots Root / problem [P]Documentation isout of date [P]Setting up alaptop takes aweek [P]Senior peoplehave no time tomentor [A]Write a one-pagestarter guide [A]Automate laptopsetup [A]Assign each newhire a buddy [O]New hires shipsomething intheir firstmonth [O]New hires feelwelcome andconfident Legend [P] Root / Problem [A] Action / Intervention [O] Desired State / Outcome Flow: roots (bottom) → outcomes (top).
Diagram as text: A Tree of Influence about onboarding new hires

Nodes:

Arrows:

How to read a tree

The notation at a glance

The notation at a glance Notation samples. A text version follows the diagram. [P]Root / Problem Something wrong or difficult [A]Action /Intervention A step between problems and outcomes [O]Desired State /Outcome A state the group wants to reach [D]Artifact /Deliverable Something that exists or should exist Influences The default arrow Blocks / Impedes Prevents the target Attacks An artifact targets a problem
Diagram as text: The notation at a glance

That is the whole visual vocabulary: 4 colors of sticky note and 3 kinds of arrow. Most trees use only 3 colors and the plain arrow. See colors and shapes and arrow styles.

A Tree of Influence is a tool for understanding problems. It should not be mistaken for a project plan, a backlog, a decision record, or a status tracker. It can feed all of those, but its job ends when the group understands the problem space well enough to act. Read more about its scope.

Where to start