Think Better
How to Build an Issue Tree
An issue tree breaks one big question into smaller ones until each branch is something you can actually check.
The short version
Put your key question on the left. Then ask: what are the three to five main parts of this? Those become your first branches.
Keep breaking each branch down until you reach questions you can answer with data or a conversation. 'Why are profits down?' becomes revenue and costs. Revenue becomes price and volume. Volume becomes new and existing customers.
A good tree has no overlaps and no gaps. It also tells you how to split the work: each branch can become someone's job.
Try it now. Put this into practice with the Issue Tree Builder.
What the full guide will cover
- What an issue tree is (and isn't)
- Choosing the first split
- How deep to go
- Diagnostic trees vs solution trees
- Turning a tree into a work plan