Issue Tree Examples: 10 Case Interview Structures Explained

What makes an issue tree work

How to build an issue tree in 2 minutes

10 Issue Tree Examples — worked MECE structures

Each of these 10 issue tree examples uses a clean 2–3 level decomposition. Read them, then build your own on a fresh case with our structure drill.

1. Example 1

   1. Profitability decline — A $500M CPG client's profit is down 15% YoY. What's driving it?

   Approach

   Profit Decline
   ├── Revenue (Price × Volume × Mix)
   │   ├── Price (list price, discounting)
   │   ├── Volume (units sold)
   │   └── Product Mix (high vs low margin SKUs)
   └── Cost
       ├── Fixed Cost (plant, overhead, SG&A)
       └── Variable Cost (COGS, materials, labor)
   

   Profit = Revenue − Cost is mathematically MECE, so the top split cannot leak. Revenue decomposes cleanly into P × V × Mix; cost splits into fixed and variable. See the profitability framework for the full decomposition.

   Answer

   Start by asking whether the drop is revenue-driven or cost-driven (ask for both trends). If revenue, test the price vs volume vs mix hypothesis — 80% of CPG profit declines trace to mix shift or price erosion.

2. Example 2

   2. Market entry — Should a European grocery chain enter the US ready-meal market?

   Approach

   Enter US Ready-Meal Market?
   ├── Attractiveness
   │   ├── Market size & growth
   │   ├── Profitability (margins, 5-force dynamics)
   │   └── Competitive intensity
   ├── Fit
   │   ├── Our capabilities (brand, supply chain, R&D)
   │   └── Synergies with existing business
   └── Execution
       ├── Cost to enter (capex, distribution)
       └── Speed / time-to-scale
   

   Attractiveness × Fit × Execution is the cleanest market entry split because the three buckets are independent — a market can be attractive but a poor fit, or a great fit but too costly to execute. See the full market entry framework.

   Answer

   Test attractiveness first (don't waste time on fit if the market is shrinking). Then fit — can we actually win here? Then execution. Most candidates skip execution and get burned by payback period questions.

3. Example 3

   3. Cost reduction — A manufacturer needs to cut costs 10% in 12 months. Where should they look?

   Approach

   Cost Base
   ├── Direct Costs (tied to unit production)
   │   ├── Materials / COGS
   │   ├── Direct labor
   │   └── Manufacturing overhead
   └── Indirect Costs (not tied to units)
       ├── SG&A (sales, G&A)
       ├── R&D
       └── Corporate overhead
   

   Direct vs indirect is MECE by accounting definition. Splitting by "people vs things" or "fixed vs variable" also works but is less actionable for cost programs.

   Answer

   Size each bucket first — the 80/20 usually lives in materials (40–60% of direct cost). Then ask which cost lines grew fastest vs benchmark. Don't commit to a lever before seeing the size-weighted opportunity.

4. Example 4

   4. M&A target evaluation — Our $2B software client is considering acquiring a $300M competitor. Should they?

   Approach

   Should we acquire TargetCo?
   ├── Strategic Fit
   │   ├── Product / technology complementarity
   │   ├── Customer overlap & cross-sell
   │   └── Talent / leadership
   ├── Financial Return
   │   ├── Valuation vs standalone value
   │   ├── Synergies (revenue + cost)
   │   └── Deal structure / financing cost
   └── Integration Risk
       ├── Cultural / org fit
       ├── Tech stack integration complexity
       └── Customer / employee retention risk
   

   The three pillars are independent: a target can be a perfect strategic fit but a terrible financial return, or great returns with fatal integration risk. All three must clear the bar.

   Answer

   Financial return is the gating question — if the IRR doesn't clear WACC + risk premium, strategic fit is irrelevant. Then pressure-test synergy assumptions (80% of deals under-deliver on synergies).

5. Example 5

   5. New product launch — A consumer electronics client wants to launch a premium earbud. Will it succeed?

   Approach

   Launch Success?
   ├── Demand
   │   ├── TAM & segment size
   │   ├── Willingness to pay
   │   └── Unmet need / job-to-be-done
   ├── Supply
   │   ├── Manufacturing capacity
   │   ├── Distribution / channel access
   │   └── Unit economics at launch volume
   └── Competition
       ├── Direct competitors (Apple, Sony, Bose)
       └── Substitutes & response risk
   

   Demand × Supply × Competition is the classic launch triangle — all three must be green. Demand-only analysis is the #1 reason launches fail in case answers and in real life.

   Answer

   Start with demand sizing (TAM × share), then check whether supply economics work at that volume, then stress-test against competitive response. Premium earbuds usually die on competitive response, not demand.

6. Example 6

   6. Pricing strategy — A SaaS client is setting price for a new tier. What should they charge?

   Approach

   Optimal Price
   ├── Customer Value (ceiling)
   │   ├── Economic value delivered
   │   └── Willingness to pay (segments)
   ├── Competitor Price (reference point)
   │   ├── Direct alternatives
   │   └── Substitute / DIY options
   └── Cost-Plus Floor (floor)
       ├── Variable cost per seat
       └── Target gross margin
   

   The three-lens pricing tree is MECE by economic logic: value is the ceiling, cost is the floor, competitor price anchors the reference. The right price lives inside that band.

   Answer

   Quantify value first — a strong value number gives you pricing power regardless of competitor price. If value >> competitor price, you have room to price at a premium. If value ≈ cost, reconsider the offering.

7. Example 7

   7. Capacity expansion — A steel producer is deciding whether to build a $200M new plant. Go or no-go?

   Approach

   Build New Plant?
   ├── Demand Forecast
   │   ├── Market growth vs current capacity
   │   └── Our share trajectory
   ├── Unit Economics
   │   ├── Contribution margin per ton
   │   └── Utilization assumptions
   ├── Capital Cost
   │   ├── Upfront capex + ramp cost
   │   └── Payback / NPV at hurdle rate
   └── Opportunity Cost
       ├── Alternative investments
       └── Do-nothing baseline (lose share?)
   

   Demand × Unit economics × Capital × Opportunity cost is MECE because each answers a different question (will anyone buy it, will each ton be profitable, can we afford it, is it the best use of capital).

   Answer

   Don't skip opportunity cost — the best candidates compare expansion vs. buying a competitor, licensing, or returning capital. A positive NPV project can still be a bad decision.

8. Example 8

   8. Market share loss — Our client's share dropped from 25% to 20% in 18 months. Why?

   Approach

   Share Loss (25% → 20%)
   ├── Our Performance
   │   ├── Product (quality, features)
   │   ├── Price (positioning)
   │   └── Distribution / marketing
   ├── Competitor Performance
   │   ├── New entrants
   │   └── Incumbent moves (pricing, product, M&A)
   └── Market Shift
       ├── Segment mix (growing segments we don't play in)
       └── Channel mix (online vs offline shift)
   

   "Us vs them vs market" is the cleanest MECE split for share loss — it separates what we did wrong, what competitors did right, and what the market did to us (which isn't anyone's "fault").

   Answer

   Ask for the data to isolate each bucket. Often 30–40% of share loss is structural market shift (not our fault, but we ignored it). The remaining 60–70% splits between our execution and competitor moves.

9. Example 9

   9. Breakeven analysis — A startup has $2M in fixed costs and a $50 contribution margin per unit. How many units to break even?

   Approach

   Breakeven Units = Fixed ÷ (Price − Variable)
   ├── Fixed Cost Base
   │   ├── Rent, salaries, overhead
   │   └── Upfront capex (amortized)
   ├── Price per Unit
   │   ├── List price
   │   └── Discount / promo impact
   └── Variable Cost per Unit
       ├── COGS / materials
       └── Direct labor + variable shipping
   

   Breakeven is a formula, not a traditional tree — but the inputs (Fixed, Price, Variable) each decompose into MECE drivers. This is classic mece practice for quant cases.

   Answer

   $2M ÷ $50 = 40,000 units. Then sanity check: is 40k units 5% or 50% of TAM? Breakeven is meaningless without that context — tie it to realistic share capture.

10. Example 10

    10. Competitive response — A competitor just cut price 20%. How should our client respond?

    Approach

    Response Decision
    ├── Customer Impact
    │   ├── Price elasticity by segment
    │   └── Switching cost & loyalty
    ├── Financial Impact
    │   ├── Lost margin if we match
    │   └── Lost volume if we don't
    ├── Strategic Positioning
    │   ├── Our value proposition (premium vs value)
    │   └── Brand / signaling risk
    └── Response Options
        ├── Match price
        ├── Partial match + value add
        ├── Hold price + invest in differentiation
        └── Exit the segment
    

    Impact × positioning × options is MECE because the first three diagnose the threat and the fourth lists the moves. Candidates who jump straight to options lose points.

    Answer

    Diagnose before you prescribe: size customer switching risk and margin loss from matching. Then pick the response that fits your positioning — premium brands rarely win a price war by matching.

Common issue tree mistakes

5 mistakes that tank your issue tree

The same issue tree drill failures show up over and over in mock interviews. Here's the shortlist.

• Overlapping branches (not mutually exclusive)
  Branches share items — e.g., "revenue, cost, and operations." Fix: pick one clean dimension (math, lever, or customer segment) and split along it only.
• Missing branches (gaps — not collectively exhaustive)
  Leaving out a critical dimension — e.g., market entry without execution cost. Fix: ask "could something live outside these branches?" If yes, add a branch.
• Splitting by symptom instead of driver
  "Sales are down because fewer customers and lower spend" is a symptom description. Fix: split by acquisition vs retention vs pricing — the levers you can actually pull.
• Going four or five levels deep on a 30-minute case
  Over-engineering eats your clock. Fix: cap at level 3 during structure, then only drill further when the interviewer asks for it.
• Using a generic framework as your issue tree
  Porter's 5 Forces, 4Ps, or 3Cs are not MECE for every problem. Fix: build a case-specific tree; borrow from frameworks only for the top-level split inspiration.

Issue tree examples — FAQ

What is an issue tree in a case interview?

An issue tree is a visual decomposition of a case interview problem into MECE sub-problems. You draw it during the structure phase of the case to break a big, ambiguous question (e.g., 'why is profit down?') into specific, testable branches (revenue vs cost → price, volume, mix, etc.).

How is an issue tree different from a framework?

Frameworks (Profitability, Porter's 5 Forces, 4Ps) are generic templates. Issue trees are case-specific — you build them on the spot from the prompt. A framework can inspire your top-level split, but your tree should always be tailored to the actual case facts.

How MECE does an issue tree need to be?

Strictly MECE at the top level — if level 1 overlaps or has gaps, the whole analysis breaks. Level 2 and level 3 can be slightly softer in practice (interviewers understand you're working under time pressure), but mutual exclusivity at the top is the hard bar.

Should I draw the issue tree or keep it mental?

Draw it. Even in voice-only interviews, sketch it on paper for yourself. Candidates who verbalize a clear tree ('I see two buckets — revenue and cost — and under revenue I want to look at price, volume, and mix…') consistently score higher than candidates who think it through silently.

What's the best way to practice issue trees?

Quantity + feedback. Build 20–30 issue trees on real case prompts, then compare to a reference answer. Our case structure drill gives you a timer, a prompt, and live AI feedback on whether your top-level split is MECE and the right dimension — better than guessing alone.

Keep going — related case interview resources

• Issue tree case interview guide
  Full walkthrough of how to build, draw, and pressure-test an issue tree live in the case.
• MECE principle, explained
  Why MECE matters, how to spot overlap and gaps, and the 5 most common MECE failures.
• Case interview frameworks complete guide
  The 12 frameworks to know — and when to skip them and build from scratch.
• Hypothesis-driven problem solving
  How to pick which branch to investigate first and drive the case forward.
• Profitability framework
  The canonical revenue vs cost decomposition every candidate should memorize.
• Market entry framework
  Attractiveness × Fit × Execution — with worked examples across industries.