Issue tree: break a business problem into parts on one slide
An issue tree breaks one key question into branches and sub-branches that are mutually exclusive and collectively exhaustive, so a team can test each part separately and know nothing is missing. Consultants use diagnostic trees to find why something happened and hypothesis trees to test a proposed answer.
Exhibit. Built in Freeform mode, which draws layouts the Structured engine does not have. Freeform slides export to PowerPoint as high-resolution images today. Illustrative data.
Read the parts of a strong issue tree
- Key question
- The root is one specific question with numbers and a time frame, here a 2.7-point margin decline over two years.
- First-level branches
- Revenue per shipment, variable cost per shipment and overheads split the margin with no overlap.
- Leaf hypotheses
- Each leaf is a testable statement the team can prove or reject with data.
- Takeaway
- The bottom line names the branch to test first and why.
Use it when
- Scope a new project in the first week.
- Split a problem across team members so workstreams do not overlap.
- Show a client how the team will answer the key question.
Pick another slide when
- Avoid it in a final recommendation deck, where the reader wants the answer.
- Avoid more than four first-level branches, because the split is probably not MECE.
- Do not use it for a process, which a flowchart shows better.
Write a title that states the conclusion
Weak
Margin issue tree
Strong
Cost per shipment explains 1.9 of the 2.7-point margin decline and is where the team starts
Read more about action titles.
Build it in Slidechat
Prompt
Build a diagnostic issue tree for why Alder Logistics' EBIT margin fell from 8.1% to 5.4% since 2023. Split it into revenue per shipment, variable cost per shipment and overheads, and put our hypotheses under each branch.
- 1
Write the key question as one specific sentence with a number and a time frame.
- 2
Split the first level by a formula or a clean logic, such as revenue minus cost.
- 3
Check each level for overlaps and gaps before you go deeper.
- 4
Stop when each leaf is a hypothesis the team can test with available data.
- 5
Assign each branch to an owner and note the analysis that will test it.
Questions about the issue tree
What is the difference between an issue tree and a hypothesis tree?
A diagnostic issue tree asks why or how and breaks the question into possible causes. A hypothesis tree starts from a proposed answer and breaks it into the conditions that must be true.
How deep should an issue tree go?
Most slide-ready trees have two or three levels. Go deeper in the working file and keep the slide at the level the audience needs.
Can Slidechat draw an issue tree?
Yes. Slidechat draws issue trees in Freeform mode from a key question and a list of branches. You can also sketch the tree on the Excalidraw canvas first.
Build this slide from your own numbers
Slidechat is in private beta. Apply for one of 100 founding seats and use it free for the whole beta.