Profitability framework: profit-related questions
Use this when the case centers on why profit changed, whether to invest in something, or how to improve financial performance. Signals it's the right fit include phrases like 'profits have declined', 'should the company invest in', or 'how can this business improve its bottom line'. Build out the revenue and cost trees and use the data given to isolate which side of the equation is actually driving the issue, rather than analyzing both sides equally once the data points clearly toward one.
Market entry framework: should we enter this market
Use this when a company is deciding whether to launch a new product, enter a new geography, or expand into a new segment. A market entry structure typically covers: market attractiveness (size, growth, competition), the company's ability to compete (capabilities, resources, brand fit), financial viability (cost to enter, expected returns, payback period), and implementation risk (how it would actually execute the entry). Each of these is a distinct lens, and skipping one, especially implementation risk, is a common gap in otherwise solid answers that interviewers notice quickly.
M&A framework: should we acquire this company
Use this for acquisition or investment cases. Structure around: the target market's attractiveness, the target company's competitive position within it, the strategic and financial fit between acquirer and target (including expected synergies), and the price versus value question, whether the deal makes sense at the proposed valuation. This overlaps with market entry but adds the specific dimension of evaluating an existing company rather than a fresh entry, which means due diligence style questions about the target's actual performance become more central.
When to build a custom structure instead
Not every case fits neatly into profitability, market entry, or M&A. Operational cases (should we change our supply chain), organizational cases (should we restructure this team), and pricing cases (how should we price this new product) often need a structure built specifically for the situation rather than pulled from a memorized template. In these cases, go back to first principles: what are the two or three genuinely distinct dimensions of this specific problem, and build your structure from there, checking it's MECE as you go rather than forcing it into a framework that doesn't quite fit.
When a memorized framework actively hurts you
Forcing a case into a framework that doesn't fit is one of the more visible mistakes an interviewer will notice. If you find yourself stretching a branch of your structure to awkwardly fit information that doesn't belong there, that's a sign you picked the wrong starting framework, or that you need to adapt it more than you have. It's always better to build a structure that's slightly less polished but genuinely fits the case than to force-fit a textbook framework that doesn't, since interviewers can tell the difference between genuine reasoning and pattern-matching to a memorized template.
Frameworks for pricing and operations cases specifically
Pricing cases often benefit from a structure around cost-based pricing, value-based pricing, and competitor-based pricing, weighing which approach fits the specific product and market. Operations cases often benefit from breaking the process into stages, such as input, production, and distribution, and identifying where the bottleneck or inefficiency actually sits. Neither of these is as universally taught as profitability or market entry, which is exactly why building them from first principles, rather than trying to recall a named framework, tends to produce a stronger answer.
Signal words that hint at which framework fits
Part of choosing the right framework quickly comes down to listening carefully to how the case prompt is worded. Words like decline, dropped, or margin usually point toward profitability. Words like launch, enter, or expand point toward market entry. Words like acquire, buy, or merge point toward M&A. Words like price, charge, or fee point toward a pricing structure. This isn't a foolproof shortcut, since some cases blend signals deliberately, but training yourself to notice these cues quickly speeds up the first minute of a case, when you're deciding how to start structuring your answer.
Building your own personal framework notes, not someone else's
Rather than memorizing someone else's framework diagrams word for word, it helps to build your own short notes on each major framework in language that makes sense to you specifically. Writing out the profitability tree or market entry structure in your own words, based on cases you've actually practiced, tends to stick better under pressure than reciting a template you copied from a guide but never internalized. This personal version is also easier to adapt on the fly, since you understand the logic behind each branch rather than just the branch names themselves.
Fluency matters more than memorization
The goal of learning these frameworks isn't to be able to recite them from memory under any condition, it's to become fluent enough that you can adapt them quickly to whatever specific case shows up. Fluency shows up as being able to explain, in your own words, why a given framework fits a given situation, and being able to bend it slightly when the case doesn't match the textbook version exactly. Candidates who've only memorized framework names without this deeper fluency tend to freeze when a case doesn't fit neatly into what they studied, while candidates with real fluency simply adapt.
A simple way to test your own framework fluency
A useful self-check is to try explaining a framework, such as the profitability tree, to someone with no business background, using plain language and no jargon. If you can do this smoothly, you likely understand it well enough to adapt it under interview pressure. If you find yourself stumbling or falling back on memorized terminology you can't actually explain simply, that's a sign to spend more time genuinely understanding the logic behind the framework rather than just its name and structure on paper.