Live
Problem Framer
Turn a messy problem into one clear question you can actually answer.
Think Better · Tool
Issue Tree Builder
Break one big question into smaller questions you can investigate. Build the tree visually, check its structure, and take it with you.
- Time
- 10–15 min
- You'll leave with
- A structured issue tree
- Skill
- Think Better
- Privacy
- Your work stays in your browser
Continue from your Problem Framer
One question. You'll break it down in the next step.
Welcome back. We restored your last tree from this device.
Futureback review
Check my structure
Look at your first level of branches, then each group underneath. Answer honestly. Only you know the problem.
How the Issue Tree Builder works
What is an issue tree?
An issue tree breaks one big question into smaller questions until each branch becomes something you can investigate.
Why consultants use issue trees
Complex problems are difficult because everything feels connected. Issue trees create structure.
Instead of asking “Why is the business struggling?”, you investigate smaller questions: is it revenue or costs? If it's revenue, is it price or volume? Each answer narrows the search, and each branch can become someone's piece of work.
A good issue tree
- Branches answer the parent question. Every branch is a possible part of the answer to the box it hangs from.
- Branches don't unnecessarily overlap. Each issue has one clear home.
- Together they cover the important parts of the problem. Nothing big is missing.
- Branches become more specific as you move down. Broad at the top, concrete at the bottom.
- The lowest useful branches are things you can actually investigate. With data, a conversation or a quick test.
No overlaps, no gaps. That's what consultants mean by MECE. Use Check my structure above for a quick self-review.
Tips while you build
- Start broad, then break it down. Your first branches should represent the major components of the problem.
- Aim for 2–5 branches. Too few may miss something important. Too many usually means the structure can be simplified.
- Keep splitting until you can investigate it. “Revenue” is too broad to analyse directly. “Average selling price declined” is something you can investigate.
Not sure what your key question is yet? Start with the Problem Framer.
Read the method
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.
Think Better
What MECE Actually Means
MECE sounds like jargon. It's really just two simple checks that stop you double-counting or missing something important.