The major consulting frameworks explained — when to use them, how to adapt them, and how not to misuse them.
If you've never done a case interview before, the first one can feel like someone handed you a puzzle with half the pieces missing and asked you to solve it out loud.
The good news: case interviews follow patterns. Once you understand those patterns and the frameworks behind them, cases stop feeling like tests of brilliance and start feeling like structured conversations. This guide explains the major frameworks, when to use them — and how not to misuse them.
Before frameworks, it's worth being clear on what consulting firms are actually evaluating.
Case interviews exist because consulting work is fundamentally about breaking down ambiguous business problems with incomplete information, identifying what matters most, and communicating a recommendation clearly. The interview simulates that in a compressed format.
Firms like McKinsey, BCG, Bain, Deloitte, and KPMG use cases to assess:
Frameworks are tools that help with structured thinking. They're not answers in themselves.
Memorising a framework and applying it verbatim to every case.
Interviewers can smell a templated answer. When a candidate hears "our client's profits are declining" and immediately launches into "I'll analyze revenue, costs, and market position" — without pausing to think about the specific situation — it signals that they're pattern-matching to a memorized script rather than actually thinking.
The right approach is to use frameworks as a starting structure — a way to organize your thinking — and then adapt them to what's specific about the case in front of you.
With that said, here are the frameworks worth knowing.
When to use it: When the case involves declining profits, margins, or EBITDA.
The core structure is simple:
Profit = Revenue − Costs
When profits fall, the question becomes: is it a revenue problem, a cost problem, or both?
Revenue side:
Cost side:
The goal is to disaggregate the problem until you find where the gap is, then hypothesize a cause.
Example: "Our client, a restaurant chain, has seen profits fall 15% over 18 months despite stable revenue."
Your direction: Revenue seems stable, so focus on costs. Ask about food costs, labor costs, occupancy costs. Has the cost structure changed? New leases? Wage increases? Supply chain issues?
When to use it: When a company is considering entering a new market, launching a new product, or expanding geographically.
This is a two-part question at its core: Should they enter? And if yes, how?
Assess the market:
Assess the client's capabilities:
Entry options:
Most strong case answers include a concrete recommendation. Don't just analyze — conclude.
When to use it: When a company is considering acquiring another company or merging.
This one has three core questions:
Strategic fit: Why does the acquirer want this target? Cost savings? Revenue synergies? Entering a new market? Acquiring technology or talent?
Financial assessment: Is the target financially sound? What is it worth? What are the synergies (revenue + cost)? Does the math work at the proposed price?
Integration risk: Post-merger integration is where most M&A deals fail. Are the cultures compatible? Are the systems compatible? How long will integration take, and what's the cost?
For fresher-level cases, interviewers don't expect a full valuation model. They want to see you identify the right questions and show that you understand the risks on both sides.
When to use it: When a case asks how to price a new product, whether to raise prices, or why pricing is going wrong.
There are three lenses to apply:
Cost-plus pricing: What does it cost to make, and what margin do you need? This sets the floor.
Competitor-based pricing: What are comparable products priced at? Can the client price at a premium? At parity? The answer depends on brand strength and differentiation.
Value-based pricing: What is the customer actually willing to pay? What problem does this product solve, and how much is solving that problem worth to them?
In practice, the best pricing strategy combines all three — especially for new products where there's no historical data.
Not every case fits a standard framework. For novel situations, the issue tree is your best tool.
An issue tree is a way of breaking a big question into smaller, mutually exclusive, and collectively exhaustive (MECE) sub-questions.
Example: "Why is our client's market share declining?"
A simple issue tree:
Each branch gets broken down further until you find what's actually driving the problem.
The key principle of MECE — mutually exclusive, collectively exhaustive — means your branches don't overlap and together they cover all possibilities. This is the foundation of consulting logic.
Step 1: Clarify the objective — Before diving in, make sure you understand what the client actually wants. "Maximize profits" is different from "achieve a 20% profit margin within 2 years." Ask one or two clarifying questions.
Step 2: Take 30–60 seconds to structure — Tell the interviewer you want a moment to organize your thoughts. Use this time to choose a framework and adapt it to the case.
Step 3: State your structure out loud — "I'd like to approach this by first looking at the revenue side, then costs, and then see if there are any external factors at play. Does that make sense?"
This isn't just politeness — it shows structured thinking before you've done any analysis.
Step 4: Work through the branches — Go through each part of your structure, asking for data where needed, and synthesizing as you go. Don't wait until the end to have a view — share hypotheses along the way.
Step 5: Conclude with a recommendation — Summarize what you found and give a recommendation. Even if the data is incomplete, make a directional call: "Based on what we've discussed, I'd recommend X. The key risks are Y and Z, and I'd want to test A before full implementation."
Most cases have some quantitative element — usually market sizing, profitability calculation, or growth projection math.
You're allowed (and expected) to think out loud during the math. Saying "I'll estimate the market at roughly 50 million urban households, multiplied by an average spend of ₹2,000 per year, so roughly ₹100 billion market size" is good form.
A few things that help:
If you're wrong, that's okay. If you can't explain how you got there, that's the problem.
If you're just starting out, master these three before anything else:
Once those feel natural, add M&A, pricing, and any sector-specific frameworks for industries you're targeting.
The most effective practice is with a live case partner — someone who can interrupt you, challenge your assumptions, and give you feedback on your communication in real time. Reading cases alone helps. Doing cases with a real person is what actually prepares you.
Nexrum offers structured case interview coaching with consultants and case partners who give real-time feedback. Start practising with live cases today.