Why Frameworks Help and Why They Fail

Frameworks are one of the first things many candidates encounter in case prep. That creates two common errors:

1. Some candidates over-rely on frameworks
2. Some candidates reject frameworks entirely

Both reactions are wrong. Frameworks are useful tools, but they are not scripts.

A framework is a structured way of thinking about a business question. Its job is to help you:

• cover the important drivers
• avoid missing obvious areas
• organize your thinking quickly

Its job is not to replace thinking. Strong candidates do not start with:

“This is a market entry case, so I will use a market entry framework.”

They start with:

“What is this client trying to decide, and what are the main factors that should drive that decision?”

If a framework helps answer that, they use it. If not, they adapt.

What It Looks Like in a Case

A good way to use frameworks is:

1. understand the client question
2. identify the business drivers that matter
3. borrow from useful frameworks where appropriate
4. tailor the structure to the case

That means frameworks support your reasoning. They do not become your reasoning.

How to Build the Habit

1. Start with the question, not the framework

Ask:

• What exactly is the client trying to solve?
• What decision needs to be made?

2. Identify the core business drivers

For example:

• profit depends on revenue and costs
• market entry depends on attractiveness, economics, capabilities, and risk

3. Customize the structure

A profitability case for an airline and a profitability case for a SaaS company should not sound identical.

4. Drop branches that do not matter

If a framework branch is irrelevant, do not force it in.

5. Use the framework to think, not to perform

Interviewers care more about logic than labels.

Example

Imagine the prompt is:

“Our client is a restaurant chain whose profits have fallen. They want to know why.”

A weaker candidate says:

“I would use the 3Cs. First, customer. Second, competition. Third, company.”

That is not necessarily wrong as a general business lens, but it is weak because it ignores the most direct business logic of the problem.

A stronger candidate says:

“Since the problem is declining profit, I would first break this into revenue and cost drivers. On the revenue side, I would test traffic, average ticket size, and mix. On the cost side, I would test food costs, labor, and occupancy costs.”

That answer is better because it starts from the problem, not the label.

What Strong Candidates Do

A strong candidate:

• uses frameworks selectively
• adapts generic models to the case
• speaks in business drivers, not framework names
• removes irrelevant branches
• stays flexible when new information arrives

What Weaker Candidates Tend to Do

A weaker candidate often:

• leads with framework names
• uses the same buckets across very different cases
• adds branches that do not matter
• sounds polished but generic
• gets stuck when the case does not fit a memorized template

Common Traps

Mistake 1: Memorizing labels without logic

If you know the name of the framework but not the business reason behind it, the structure will sound hollow.

Mistake 2: Forcing the wrong framework

Candidates often match on keywords instead of actual business questions.

Mistake 3: Treating all branches as equally important

Even a good framework still requires prioritization.

Mistake 4: Thinking frameworks are the goal

Frameworks help you get to insight. They are not the insight.

What to Remember

• Frameworks are tools for organizing business logic.
• They help when they improve coverage and clarity.
• They fail when they replace case-specific thinking.
• Strong candidates start from the client problem and adapt frameworks to fit it.