What it is and is not

Where the Tree of Influence ends and other tools begin.

What it is

A Tree of Influence maps and explores a complex problem space. What it produces is understanding: a visual, evolving picture of problems, their causes, how they relate, the outcomes people want, and the actions and artifacts that connect them.

It is:

A map of a problem space. Many interconnected problems at once, without assuming a single root cause.
A thinking tool. One person can use it to untangle a situation alone.
A facilitation technique. A group can use it to build shared understanding, from a handful of people to a room of 30 or more.
A living document, while it is useful. It can be updated across planning cycles, or retired once it has done its job.

It works across domains: software and technical debt, team delivery, organizational trust, and the messy overlaps between them.

It is also unpretentious. It started as a joke between two facilitators, and it remains a thinking tool to try and adapt, not a methodology to certify in.

Where it ends

The tree's job ends at understanding. Once the group knows what matters and why, the work moves on to something else.

The group now knows what matters and why. Who runs the buddy program, and when laptop automation ships, is decided elsewhere, with this tree as input.

Diagram as text: The finished onboarding tree, where the tree's job ends

Nodes:

Root / Problem: "Docs are stale"
Root / Problem: "Documentation is out of date" (2 votes)
Root / Problem: "Each team onboards differently"
Root / Problem: "Setting up a laptop takes a week"
Root / Problem: "Senior people have no time to mentor" (3 votes)
Root / Problem: "New hires are afraid to ask questions" (2 votes)
Action / Intervention: "Automate laptop setup"
Action / Intervention: "Assign each new hire a buddy" (1 vote)
Desired State / Outcome: "New hires ship something in their first month" (4 votes)
Desired State / Outcome: "New hires feel welcome and confident"

Arrows:

"Each team onboards differently" influences "Documentation is out of date"
"Setting up a laptop takes a week" influences "Automate laptop setup"
"Senior people have no time to mentor" influences "New hires are afraid to ask questions"
"Senior people have no time to mentor" influences "Assign each new hire a buddy"
"Documentation is out of date" influences "New hires ship something in their first month"
"Automate laptop setup" influences "New hires ship something in their first month"
"New hires are afraid to ask questions" influences "New hires feel welcome and confident"
"Assign each new hire a buddy" influences "New hires feel welcome and confident"

Everything after that point takes the tree as input but is not part of it: assigning owners, planning projects, estimating effort, tracking progress, and ruling parts of the tree out because of budget or other constraints.

Decompose, the last step of a session, is where this handoff begins. Subgroups take ownership of parts of the tree and start the bridge from understanding to action. That bridge leads out of the Tree of Influence.

What it is not

A tree can feed all of the tools below. It should not try to replace any of them.

It is not	Because	What it gives that tool instead
A project plan	It assigns no tasks, owners, or deadlines	The problems worth planning around
A backlog	It does not order work for execution	Priorities, and the reasons behind them
A decision record	It maps the landscape decisions are made in, not the decisions themselves	The context of each decision
A status tracker	Each version is a snapshot of the present. Resolved problems are deleted, not marked done	What changed between versions
A solution-design tool	It maps problems. Solutions on the board are part of the situation, not the answer	Causes for solutions to aim at
A polished publication	It is a thinking tool. Its value is the understanding, not the look	A shared picture people can point to

For how the Tree of Influence compares with other frameworks, such as Ishikawa diagrams and the Current Reality Tree, see compared with other frameworks.

Signs a tree is turning into something else

Nodes carry owners, due dates, or status labels such as "done" or "in progress."
Resolved problems stay on the board, marked instead of removed.
The group spends more time arranging the layout than talking about the problems.
The conversation is about how to implement things, not about what is going on.
Most of the board is solutions. See solution-dumping.

When you see these, the tree has probably done its job. Move that work to the tool built for it, and keep the tree as its input.

Boundaries still being explored

So far, the Tree of Influence has mostly been used by the people who developed it, so these boundaries come from their experience. New ones will appear as other people use it and stretch it in directions nobody planned. If you find one, share it.