Driver-tree equation with effectiveness/efficiency brackets and three supporting boxes
Download PPTX · 1 creditSLIDE LAYOUT LIBRARY
Issue Tree & Driver Tree Slide Examples
An issue tree breaks one question into the sub-questions that settle it. A driver tree does the same for a number, decomposing it into the factors that multiply or add up to it. Both are how a consulting team turns a vague problem into work that can be divided.
One editable sample, no sign-up. See how to adapt it.
+
Paste your draft to find a layout like these
⌘ VorCtrl V
or drop an image here
Search is free · searches the whole library, not just this page
No screenshot to hand?
When to use this layout
Use a tree when the slide has to show that a problem has been completely taken apart — that nothing was missed and nothing is counted twice. That property has a name, MECE: mutually exclusive, collectively exhaustive.
Driver trees are the arithmetic version. Revenue splits into volume × price; volume splits into customers × frequency. Each level should be a real identity, not a loose association, so a reader can follow the maths down the branches.
A hypothesis tree flips the direction: instead of decomposing the problem, it lays out candidate answers and the evidence that would confirm or kill each one. Use it when the point of the slide is the plan of attack, not the structure of the question.
What the layout is made of
- A root that is a question or a numberNot a topic. “Costs” is a topic; “Why did unit cost rise 12%?” is a root worth a tree.
- Branches at the same level of abstractionEvery child of a node should be the same kind of thing. Mixing a geography with a product line at the same level is the fastest way to break MECE.
- A visible split ruleSay how each level is cut — by driver, by segment, by stage. When the rule is written down, the reader can check whether the split is exhaustive.
- Two or three levels, not fiveA tree on a slide is a communication device, not the working model. Show the levels that carry the argument and keep the rest in the appendix.
FICTIONAL WORKED EXAMPLE
Worked example: organise hypotheses about falling unit sales
1. Start with the brief
A fictional team has a list of possible causes: pitch quality, team structure, low awareness, packaging, seasonal demand, quality complaints and fewer shelf slots. The question is why unit sales are falling; none of the causes has yet been established.
2. Choose the structure
Use the three-level logic tree d067: one question, three investigation branches, then testable hypotheses. It gives the team a place to organise the work before choosing which evidence to collect.
3. Read the finished slide
The sample separates sales process, brand and marketing, and the product itself. It is a starting hypothesis map, not proof of the cause or a guaranteed MECE decomposition. Define branch boundaries explicitly: for example, assign promotions to marketing rather than counting them under both marketing and sales.
What you can edit in PowerPoint
Edit the root question, each branch label, the hypothesis boxes, connector lines, explanatory panel and footer. You can add or remove branches using ordinary PowerPoint shapes. Keep the visible tree to two or three levels.
Read the full before-and-after slide makeover guides
Make this template your own
- Replace the root question with one measurable business problem and a time period.
- Choose non-overlapping branch definitions and replace the leaves with hypotheses that can be tested. Check for missing causes.
- Assign evidence and an owner to each hypothesis in your working notes. Highlight a branch only after the evidence supports it.
No account, payment or credits required for this sample. Get all three free PowerPoint templates. Use in your own presentations under our slide licence.
7 editable examples
Each one is redrawn from scratch with fictional sample data and comes as a native PowerPoint file — real shapes and text boxes you can edit, recolour and resize. Open an image for a full-size preview. Samples marked Free PPTX need no account; other downloads use 1 credit.
Where these slides usually go wrong
- Overlapping branchesIf a cost could sit in two branches, the tree double-counts and the arithmetic stops working. Test every pair of siblings for overlap before drawing.
- A tree that is really a listThree boxes hanging off a root with no split rule is a list drawn sideways. If there is no decomposition logic, use pillars and save the reader the confusion.
- Unbalanced depthOne branch exploded into nine leaves while its siblings stay unopened signals that you only investigated one path — which may be true, but say so rather than letting the drawing imply rigour you did not apply.
- No sizingA tree without numbers on the branches tells the reader how you think, not where the money is. Put the magnitude on each branch wherever you have it.
Layouts for your slide
Matched by structure, not color. Download any layout as editable PowerPoint.
Looking for similar layouts…
The search did not finish
The library is small and growing. If nothing fits, try cropping to the part of the slide you care about.
Pricing
Searching is free. 1 credit = 1 editable PPTX slide, and downloading the same slide again is free. New accounts get 2 free credits. Credits never expire.
One-time payments, no subscription. Prices in USD; taxes may apply at checkout. Payments are processed securely by our reseller and Merchant of Record, Creem. See the refund policy.
Questions about this layout
What does MECE mean in an issue tree?
Mutually exclusive, collectively exhaustive. Mutually exclusive means no two branches overlap; collectively exhaustive means together they cover the whole parent. It is what lets you claim the problem has been fully taken apart rather than partially sampled.
What is the difference between an issue tree and a driver tree?
An issue tree decomposes a question into sub-questions. A driver tree decomposes a quantity into the factors that produce it, usually through a real arithmetic identity. Issue trees guide investigation; driver trees guide calculation.
How many levels should an issue tree on a slide have?
Two or three. The deeper working tree belongs in a backup page or a spreadsheet — on a slide, the fourth level is usually unreadable at the back of the room.
Do I need numbers on the branches?
Whenever you have them. A tree with magnitudes turns a structural argument into a prioritisation argument, which is nearly always the one the audience actually wants.