10.1 Why Frameworks Became Popular in Case Preparation
Frameworks became popular because they simplify unfamiliar business problems. For a beginner, being told to “structure the problem” can feel vague. A framework provides a starting point.
For example, a profitability framework reminds you that:
Profit = Revenue − Costs
You can then break revenue into price and volume and costs into fixed and variable components.
Why frameworks help: They show recurring business relationships and give candidates a vocabulary for organizing analysis.
The problem arises when candidates assume that every case must fit one of a small number of memorized templates.
10.2 Frameworks as Learning Tools Rather Than Scripts
The best way to use frameworks is as training devices. They help you understand the major questions that often matter in a particular type of problem.
A market-entry framework might teach you to consider market attractiveness, competition, company capabilities, economics, entry options, and risks. Over time, you should understand why those categories matter rather than merely memorize them.
Learning goal: Understand the logic behind the framework well enough that you can recreate, modify, or discard it when the situation demands.
Think of frameworks as examples of good problem decomposition, not as answers you must reproduce.
10.3 Why Memorized Frameworks Often Fail
Memorized frameworks fail when they are too generic for the problem.
Suppose a hospital asks how to reduce emergency-room waiting times. Responding with “market, competition, customers, and company” would provide little guidance. The case may be better structured around patient arrivals, staffing, process steps, room capacity, diagnostic bottlenecks, and discharge times.
Interviewers can usually recognize when a candidate is forcing a case into a familiar template.
Warning signs: Your structure uses generic labels, includes branches unrelated to the objective, or could be applied almost unchanged to many different cases.
A framework should clarify the problem. If it makes the problem less specific, it is probably being misused.
10.4 Starting from First Principles
First-principles thinking means starting with the client’s objective and asking what must be true for the desired outcome to occur.
If a client wants to increase restaurant profit, you might begin with the economics of the business: number of customers, average spending, food costs, labor costs, rent, and other operating expenses.
If a company wants to reduce delivery times, you might map the process from order receipt through fulfillment and transportation.
Useful question: “What actually drives the outcome the client cares about?”
Starting there usually produces a more relevant structure than asking which memorized framework seems closest.
10.5 Adapting Frameworks to the Situation
A familiar framework can still be useful if you tailor it to the case.
Suppose a software company is considering entering a new country. A generic market-entry structure might be adapted to include local customer demand, software adoption, competitor offerings, pricing, regulatory requirements, localization needs, sales channels, implementation capabilities, and expected economics.
Adaptation: Replace generic categories with the specific drivers, constraints, and economics of the client’s situation.
You can also remove categories that clearly do not matter. Completeness does not mean including every category you have ever learned.
10.6 Combining Different Analytical Lenses
Some cases require more than one way of looking at the problem.
A growth strategy case, for example, may involve:
- Customer lens: Which customer segments offer the greatest opportunity?
- Product lens: Which products could be expanded or introduced?
- Geographic lens: Which markets offer attractive demand?
- Economic lens: Which opportunities generate acceptable returns?
- Capability lens: Can the company execute successfully?
The goal is not to stack multiple frameworks together. Use different lenses only when they help answer distinct parts of the client’s question.
10.7 Developing Your Own Structures
One of the best ways to improve at cases is to practice building structures from scratch.
Take a business question and ask:
- Objective: What exactly are we trying to determine?
- Drivers: What variables determine that outcome?
- Questions: What would I need to know about each driver?
- Priorities: Which areas are most likely to affect the answer?
- Evidence: What information would allow me to test them?
Then compare your structure with established frameworks and ask what you missed.
Practice benefit: Over time, you begin recognizing recurring patterns without depending on memorized templates.
10.8 When Familiar Frameworks Are Genuinely Useful
Some problems have well-established structures because the underlying economics are genuinely similar across many businesses.
Profitability: Revenue and cost decomposition is almost always useful when profit is the central issue.
Market sizing: Population, customers, usage, and price often provide natural ways to build an estimate.
Pricing: Costs, competitor prices, customer willingness to pay, and economic impact are recurring considerations.
Market entry: Market attractiveness, competitive position, capabilities, economics, entry method, and risks are frequently relevant.
The key is to begin with the problem rather than the framework. If a familiar structure fits naturally, use it. If it does not, modify it or build something better.
Final principle: Frameworks should expand your thinking, not limit it. Learn the common ones because they teach useful business logic, but practice until you can structure unfamiliar problems from first principles. The goal is not to remember the right framework. It is to build the right structure for the client’s problem.
