# Issue Trees, Explained

> What an issue tree is, where it came from, when to use one - and when not to. With a worked example, and a version you can play.

Source: https://www.wavetable.net/frameworks/issue-trees

[Frameworks](https://www.wavetable.net/frameworks)

Structuring thinkingAlso called Logic tree, problem tree

# Issue Trees

Break one big question into smaller questions that don't overlap, until each is small enough to answer.

## In one look

1.  1One question at the top.
2.  2Branches that don't overlap.
3.  3Each branch small enough to answer.

No single inventor. Issue trees grew up inside the strategy firms, taught alongside Barbara Minto's rules for grouping ideas. They spread because they solve a staffing problem: split one vague client question into branches, and each branch becomes somebody's job.

The problem it solves

## The brief says "find out why."

So the team pulls every report it has. Sales blames pricing, product blames the roadmap, and three weeks in there's plenty of analysis and no answer. Drawing branches is easy. Getting them not to overlap is harder, and so is noticing the branch nobody wants.

## Try it yourself

No sign-up, a few minutes. A Q2 revenue shortfall. You move three branches until nothing overlaps and nothing's missed.

## The same question, split

A team asked why it missed its Q2 target.

-   Three weeks inSales blames pricing.becomes Three branches: fewer deals came in, fewer converted, or deals closed smaller.
-   Three weeks inProduct blames the roadmap.becomes Each branch gets an owner and a data source. Two are ruled out within days.
-   Three weeks inPlenty of analysis and no answer.becomes The third branch has it: conversion, in one segment, right after the pricing change.

## Good times to run it

-   Starting a diagnostic, like a profit drop, a churn spike or a missed forecast
-   Splitting a due-diligence question across a deal team
-   Scoping what a project will and won't cover
-   Turning "can you look into this?" into a plan with owners

## When to skip it

-   Problems nobody understands yet. The branches are guesses, and the diagram makes them look settled.
-   Small questions one person could answer by Thursday.
-   When the blocker is political. A tree won't help if the CEO has already decided.

Teams we've run sessions with:

-   ![Publicis Groupe](https://www.wavetable.net/logos/publicis-groupe.svg)
-   ![SoundCloud](https://www.wavetable.net/logos/soundcloud.svg)
-   ![WeTransfer](https://www.wavetable.net/logos/wetransfer.svg)
-   ![The New York Times](https://www.wavetable.net/logos/nyt.svg)
-   ![Columbia Business School](https://www.wavetable.net/logos/columbia.svg)
-   ![EY](https://www.wavetable.net/logos/ey.svg)
-   ![Havas](https://www.wavetable.net/logos/havas.svg)
-   ![NYC](https://www.wavetable.net/logos/nyc.svg)
-   ![MCI Group](https://www.wavetable.net/logos/mci-group.svg)
-   
-   
-   
-   
-   
-   
-   
-   
-   

## Run it with your team

That was someone else's quarter. With your own question, where two teams each think it's the other's branch, it's harder. We run it as a live session on a problem like yours, in small groups with a host.

[Consulting firms](https://www.wavetable.net/for/consulting-firms)[Professional services](https://www.wavetable.net/for/professional-services)

## More frameworks

-   [Structuring thinking**MECE**A test for any list: no item overlaps another, and nothing important is missing.](https://www.wavetable.net/frameworks/mece)
-   [Strategy**Hypothesis-Driven Thinking**Start with your best guess at the answer, then spend the time you have trying to prove it wrong.](https://www.wavetable.net/frameworks/hypothesis-driven-thinking)
-   [Decision-making**5 Whys**Ask why the problem happened, then ask why again of each answer, until you reach a cause worth fixing.](https://www.wavetable.net/frameworks/5-whys)
