JH
Jonathan Haber
Barbara Minto / McKinsey

How do you use issue trees to break down complex problems and find the real drivers?

Decomposing problems completely, finding the key drivers, and avoiding analytical blind spots

Short answer

Issue trees (also called logic trees) are hierarchical diagrams that decompose a problem or question into its constituent parts, following the MECE principle (mutually exclusive, collectively exhaustive). Developed and used extensively at McKinsey, they are a standard consulting and analytical method for ensuring all problem dimensions are covered without overlap. The evidence base is professional practice rather than experimental — these are structured thinking tools, not psychologically studied interventions.

Most complex problems look intractable when viewed as a whole. Issue trees break them into smaller, answerable questions arranged hierarchically — each branch answers "why?" or "what?" about the one above it. The discipline of building the tree reveals missing branches (dimensions you hadn’t considered) and overlapping branches (dimensions you’re double-counting). Below are the practices for building and using issue trees effectively.

The practices (7)

Why it works

Issue trees branch from a root question; every branch is an answer to that question or an answer to "why?" or "how?" about a branch above it. If the root question is vague, the tree branches toward different implied questions simultaneously, producing a structurally valid-looking tree that solves the wrong problem. The discipline of precise question definition forces alignment on what the analysis is actually for before effort is invested.

How to do it
  1. 1Write the problem as a specific question: "Why did revenue decline 15% in Q3?" not "Revenue is a concern."
  2. 2Check that the question specifies: the decision-maker, the time horizon, and the type of answer needed (explanation, decision, recommendation).
  3. 3Test the question with the primary audience: "Is this the question you most need answered right now?"
  4. 4Revise the question until a direct one-sentence answer would be genuinely useful, then start the tree.
Evidence
Anecdotal

Precise problem definition as a prerequisite for effective analysis is a foundational principle in management consulting and structured problem-solving methodologies. Its value is logically demonstrable: a misframed problem cannot be correctly solved. Direct experimental evidence is absent; the principle is established professional practice.

Honest caveat: Problem definition is itself a judgment call; the "right" question can only be assessed in retrospect. An overly narrow question can exclude important problem dimensions.

Common mistake: Starting to build branches before the root question is written down, which means each branch answers a slightly different implicit version of the question.
Go deeper on this practice →

Practice this with IX Coach

Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.

Start with IX Coach →

Related practices