Profitability Tree

The tree starts at the top with Profit and splits into two branches: Revenue and Costs. Revenue then splits into Price × Quantity (volume), and Quantity can split further by product line, segment, or region. Costs split into Fixed Costs (rent, salaries, equipment) and Variable Costs (materials, per-unit labor, shipping) — and variable costs can be expressed as cost-per-unit × quantity. This gives a complete, MECE (Mutually Exclusive, Collectively Exhaustive) map: every dollar of profit change must come from price, volume, fixed cost, or variable cost. Because the tree is exhaustive, you can confidently rule out branches and zero in on the driver.

When given a declining-profit case, draw (or verbalize) the tree, then ask diagnostic questions to walk down it: 'Has the decline come from revenue or costs?' If revenue, 'Is it a price problem or a volume problem?' If volume, 'Which product or segment is shrinking, and is it us or the whole market?' This systematic narrowing is the entire point — interviewers are testing whether you can isolate the root cause rather than guess randomly. A strong candidate uses the tree to drive the data requests: each question prunes a branch until the problem is localized to, say, 'volume is down 15% in the North American consumer segment because a new competitor entered.'

The profitability tree is superior to memorized frameworks (like a generic '3 Cs' or '4 Ps') for profit cases because it's quantitative and exhaustive — it forces the math to add up and guarantees you won't miss a driver. The 3 Cs (Company, Competitors, Customers) and Porter's Five Forces are qualitative lenses better suited to market-entry or competitive-strategy cases. The mark of a polished candidate is choosing the right structure for the prompt: a profitability tree for 'profits are down,' a market-sizing structure for 'how big is this market,' and a tailored issue tree for open-ended strategy questions. Don't force a memorized framework onto every case.

The biggest mistake is jumping to solutions ('they should cut costs') before diagnosing where the problem is — the tree exists precisely to prevent this. Another is forgetting that revenue and cost branches must be analyzed in absolute terms and rates: a profit drop could come from flat revenue but rising per-unit costs, or stable margins but collapsing volume. The polish is layering in 'is it internal or external?' at each branch — a volume decline driven by a market-wide downturn calls for a very different recommendation than one driven by losing share to a specific competitor. Always tie the diagnosis back to a quantified, actionable recommendation.