Tree of InfluenceRoot / Problem
A problem, root cause, or undesirable current state in the problem space.
Definition
A root / problem node is something that is wrong, broken, or causing difficulty. It is the starting point of influence in the tree: root / problem nodes influence other nodes, and they are what the rest of the tree grows from.
A node's type comes from its role in the graph, not from how its text is worded. A root / problem node can be a crisp statement ("Lack of technical leadership") or an observation backed by data ("About 55% of fixed bugs are new regressions"). What makes it a root / problem node is that it has outgoing arrows and few or no incoming arrows from other problems.
Problems can also influence other problems, forming chains. The deepest root sits at the start of the chain.
Diagram as text: A chain of problems leading to an outcome
Nodes:
- Root / Problem: "Each deployment needs many custom steps"
- Root / Problem: "Every deployment is different"
- Root / Problem: "Not every variation can be tested"
- Desired State / Outcome: "Releases are routine and predictable"
Arrows:
- "Each deployment needs many custom steps" influences "Every deployment is different"
- "Every deployment is different" influences "Not every variation can be tested"
- "Not every variation can be tested" influences "Releases are routine and predictable"
When it appears
Root / problem nodes often appear first, during Seed, when participants describe what is wrong or what is making things hard. More of them surface during Connect, when the group asks "what causes this?" about nodes already on the board.
How to draw it
| Property | Convention |
|---|---|
| Shape | Rectangle or sticky note, the same shape as every other node |
| Color | Dark brown, #6B3A2A, with white text |
| Position | Bottom of the tree (vertical orientation) or left (horizontal orientation) |
| Text marker | [P], when the accessibility markers are in use |
During Seed, nodes may stay uncolored until their type is clear. Apply the color during refinement.
Examples
- "Production quality issues"
- "Skill gaps in team leadership"
- "Deployment complexity prevents rapid iteration"
- "Reluctance to give direct feedback"
- "About 55% of fixed bugs are new regressions"
These come from real trees in very different domains: software delivery, team leadership, and organizational trust.
Common mistakes
Solutions disguised as problems. "Need better tooling" reads like a problem, but it is a solution statement. Ask the group "what problem does that solve?" and put the answer on the board as root / problem nodes. Left unchecked, this mistake grows into solution-dumping.
Required or optional
Required. Every Tree of Influence has root / problem nodes. They appear in every observed tree, in every domain.