Glossary
What is an issue tree?
Issue tree: An issue tree breaks one central question into sub-questions, level by level, until each branch can be answered with a fact, an analysis or a decision.
An issue tree (also called a logic tree) turns one big question into smaller ones. The key question sits at the root. Each level below splits it into sub-questions that are MECE: no overlaps and no gaps. You keep splitting until a branch can be settled with one analysis, one number or one decision.
There are two common kinds. A why tree diagnoses ("Why did the margin fall?"). A how tree looks for solutions ("How can we release €4m of cash?").
A worked example
A toolmaker wants to release €4m of cash within twelve months. Working capital is inventory plus receivables minus payables, so the first level is MECE by definition:
- Reduce inventory
- Finished goods
- Work in progress
- Raw materials
- Collect cash faster
- Shorten customer payment terms
- Chase overdue invoices
- Pay suppliers later
- Renegotiate supplier terms
Every leaf is something a team can size and test. Sizing shows where to start. On the slide below, €11.2m sits in inventory and receivables, and finished goods alone exceed the benchmark by about €1.6m.
How to build an issue tree
- Write a specific key question. Include the metric, the scope and the deadline: "How can we release €4m of cash within twelve months?"
- Split by one logic per level. Use a formula, a process or a clear set of categories, never two at once.
- Run the MECE test. Could any item sit in two branches? Does anything fall outside all of them?
- Stop at answerable branches. A leaf is done when one analysis or one decision settles it.
- Size and prune. Estimate which branches matter most and analyze those first.
Issue trees on slides
The full tree rarely belongs in the main part of a deck. Show it once, on the approach slide or in the appendix, so readers see what you examined and what you ruled out. Then let each branch become a section and each leaf a slide with an action title.
An issue tree starts from the question; the pyramid principle starts from the answer. Use the tree to find the answer and the pyramid to present it.
Typical mistakes
- Overlapping branches, such as "Sales" and "Marketing" next to "Customers".
- Two logics on one level, for example regions next to products.
- Leaves nobody can test, such as "Improve the culture".
- A tree so deep that nobody reads it. Prune it.
- A tree with no answer at the end. The tree is a means; the deck needs the conclusion.
Next step: put numbers on the branches with a driver tree.
FAQ
Frequently asked questions
What is the difference between an issue tree and a decision tree?
An issue tree structures a problem: it splits a question into sub-questions so that an analysis covers everything. A decision tree evaluates a choice: it maps options, chances and payoffs, often with probabilities. Use the first to organize the work and the second to pick between options.
How many levels should an issue tree have?
Usually two to four. Stop when each branch can be answered with one analysis, one data point or one decision. Deeper trees tend to turn into task lists.
What is the difference between an issue tree and a driver tree?
An issue tree is made of questions and stays qualitative. A driver tree is made of metrics and calculates, because each box is a formula of the boxes below it. Draw the issue tree when you do not yet know what to measure, and the driver tree once you do.
What is a hypothesis-driven issue tree?
It starts with an answer instead of a question. You state what you believe is true, then branch into the conditions that must hold for it to be true. Each branch becomes a test, and you drop the hypothesis if a test fails.
Keep reading
Storyline and structure
- GuideStructure a presentation
How to structure a presentation for work: lead with the answer, match the order to your purpose, use skeletons for decisions, updates, pitches and proposals.
- Free toolAction title checker
Paste your slide titles and get a score for each: verb, number, so-what and length, with a rewrite hint. Free, runs in your browser, English and German rules.
- GlossaryAction title
An action title is a slide headline written as a full sentence that states the slide's conclusion. Definition, before-and-after examples and rules.
- GuideAction titles
Write slide headlines as full sentences. Six rules for action titles, twelve before-and-after examples and a quick test you can run on any deck.
- Free toolOutline builder
Free presentation outline builder: pick occasion, audience, goal and length, then edit a slide-by-slide storyline of action titles and open it as your brief.
- GlossaryKey message
A key message is the one idea you want your audience to remember and act on after a presentation or a slide. Definition, examples and how to write it.
Where to go next
- TemplateConsulting presentation
A consulting presentation template with 9 slides: executive summary, situation, causes, options, recommendation, roadmap, business case and decision.
- ProductAI PowerPoint generator
Give the AI your brief, approve the page plan and export a .pptx you can keep editing.
- ConvertNotes to slides
Paste, attach or speak rough notes, answer a few questions and approve a page plan.
Less theory, more finished slides
Describe the deck you need. The AI plans, writes and designs it, and hands you an editable PowerPoint.
Build your first deck freeFree plan, no card needed