Profit / Profitability Tree

Overview

The Profitability Tree is a consulting application of standard financial decomposition — not attributed to one person, but a standard in firm training and case interviewing. The foundational identity is elementary: Profit = Revenue − Cost. The power is in how the tree systematically breaks each driver into sub-drivers, following the logic until every branch reaches a lever that is specific, measurable, and actionable.

The analytical lineage traces partly to DuPont Analysis, developed in 1914 by Donaldson Brown at E.I. du Pont de Nemours and Company — one of the earliest formal uses of ratio decomposition to break down return on equity into its operational components (net profit margin × asset turnover × financial leverage). The Profitability Tree applies the same discipline to the P&L in the context of a specific client problem.

The profitability problem is one of the most common consulting archetypes because declining margins affect virtually every business at some point, and because the answer is almost always in the details: is this a revenue problem or a cost problem? If revenue, is it price or volume? If volume, is it market growth or market share? The tree forces the analysis to that level before any solutions are proposed.

A standard tree structure:

• Profit = Revenue − Cost
  • Revenue = Price × Volume
    • Price: average selling price, pricing architecture, product/customer mix effects
    • Volume: units sold = market size × market share; or transactions × average basket size
  • Cost = Fixed Cost + Variable Cost
    • Fixed: overhead, depreciation, R&D, G&A — costs that don't move with volume
    • Variable: cost per unit × units = COGS, direct labor, direct materials, commissions

Each branch continues until it reaches specific, measurable drivers — the level where the data either confirms or rules out that branch as the source of the problem.

When to Use It

Whenever the client's question involves profitability: "Our margins are declining — why?" "We're growing revenue but losing money." "How do we improve EBITDA by 3 points?" The Profitability Tree is the first tool to reach for because it gives the analysis structure before any data is examined, preventing the team from jumping to solutions before identifying which branch of the tree is actually broken.

How It Works

1. State the profitability question clearly — what metric is the client trying to improve? Gross margin? Net income? EBITDA? Operating margin? The right tree depends on the right metric.
2. Draw the top-level split — Profit = Revenue − Cost. Always the starting point.
3. Decompose each branch — break Revenue into Price × Volume; break Cost into Fixed + Variable (or by cost category). Apply MECE at every level: branches should not overlap, and together they should explain the full driver (see Issue Trees & MECE).
4. Follow the data to find the problem branch — which part of the tree explains the decline or gap? Once identified, go deeper into that branch specifically.
5. Apply root-cause tools on the broken branch — use 5 Whys or fishbone to understand why that driver is underperforming.
6. Size the opportunity — how much of the profitability problem does this branch explain? If fixing the identified issue restores 80% of the lost profit, you've found the primary lever.

Common Pitfalls

• Staying at the top level — concluding "it's a revenue problem" without identifying whether it's price, volume, or mix is incomplete; the tree only adds value if you go deep enough
• Non-MECE splits — branches that overlap or leave gaps produce double-counting or missed drivers; check MECE at every level
• Ignoring mix effects — average selling price can fall even if no individual product's price changes, if the sales mix shifts toward lower-priced products; mix is often the hidden driver
• Tautology instead of diagnosis — "revenue is declining because customers aren't buying" restates the problem; the tree should push past the symptom to the underlying driver
• Forgetting the cost side — teams often fixate on revenue decline and underinvestigate whether cost increases are the real or co-contributing issue

Recommended Books

• The McKinsey Way — Ethan Rasiel
• Bulletproof Problem Solving — Charles Conn & Robert McLean
• Financial Intelligence — Karen Berman & Joe Knight