PART IV: Analysis: Frameworks Are Optional

One of the most important lessons for developing case-solving judgment is that you do not have to use a framework. Frameworks are tools, not requirements. Sometimes a framework will help you see something that would otherwise be difficult to identify. Sometimes a simple comparison, calculation, customer analysis, or observation from the case will produce a stronger insight than a formal framework. For example, if the case tells you that:

sales have declined;
prices have remained stable;
customer volume has fallen;
and a major competitor has entered the market,

you may not need to build a SWOT analysis to recognise that competitive pressure and declining customer demand deserve investigation. Likewise, if a financial calculation clearly demonstrates that an initiative produces a negative NPV, you do not need another framework to tell you that the investment destroys value under the assumptions used.

The key question is therefore not: "What framework haven't we used?" It is: "What do we still need to understand?"

Use a framework when it helps you answer an important question, uncover an insight, compare alternatives, or support your recommendation. Do not use one simply because:

it is familiar;
it appears in a textbook;
another team might use it;
you think judges expect it;
or you want to make the analysis look more sophisticated.

Sometimes the most sophisticated case-solving decision is knowing when not to use a framework.

The Mad Skills Rule

Use the tool that produces the best insight not the tool that looks the most impressive.

Your judges are not awarding points for the number of frameworks you complete. They are evaluating whether you understand the case, identify the important issues, develop meaningful insights, and use those insights to support a strong decision.

Chapter 6: Analysis Is Not a Fact Dump

Video: Case Analysis That Actually Wins: Build Bulletproof Support for Your Recommendation

One of the most common problems in case-solving competitions is analysis that is really just information. Teams find facts. They put those facts on slides. They add graphs. They complete frameworks. Then they make a recommendation. The problem? The analysis never actually explains why the recommendation is right.

Strong case analysis does more than describe what is happening. It explains what the information means, why it matters, and what the organisation should do. The goal is to move from:

FACTS → ISSUES → INSIGHTS → ALTERNATIVES → DECISION

That progression is what turns information into analysis.

What Is Analysis?

Analysis is the process of breaking information apart, identifying relationships and patterns, interpreting their meaning, and using those insights to support a decision. A fact by itself rarely tells the organisation what to do. For example: Customer retention has declined. That is a fact. It becomes useful only when we begin asking:

Why has retention declined?
Which customers are leaving?
When did the decline begin?
What changed?
Why are customers leaving?
What is the financial impact?
What would happen if the trend continues?

The purpose of analysis is therefore not to collect more information. It is to make information useful for decision-making.

The Analysis Ladder

A useful way to structure your thinking is the Analysis Ladder.

Step 1: Fact: What do we know?

Identify the information provided by the case or discovered through research. Example: Customer retention has declined by 12% over three years.

Step 2: Observation: What does the information show?

Describe the pattern, change, relationship, or difference. Example: Existing customers are leaving at an increasing rate.

Step 3: Insight: What does that tell us that is not immediately obvious?

Interpret the information. Example: The organisation may have an acquisition problem that is actually being created by a retention problem. This is where analysis begins to become valuable.

Step 4: Implication: Why does it matter?

Connect the insight to the organisation's objectives, performance, or decision. Example: Increasing customer acquisition without addressing retention may add customers to a system that is already failing to retain them.

Step 5: Decision: What should we do differently?

Connect the implication to an action or strategic choice. Example: Prioritise retention before significantly increasing customer acquisition spending. That is analysis.

The Difference Between Information and Insight

A useful test is to ask: "So what?" If your analysis does not answer that question, you probably have information rather than insight.

Information	Analysis
Sales declined 8%.	The decline is concentrated in the company's highest-margin customer segment.
Employee turnover increased.	Turnover is concentrated among experienced employees, increasing replacement and training costs.
A competitor entered the market.	The competitor is targeting the company's most attractive customer segment with a lower-cost proposition.
Costs increased.	The increase is being driven primarily by a change in product mix rather than overall volume.
Market growth is 6%.	The organisation is growing at only 2%, indicating that it is losing relative market position.

The difference is not the amount of data. The difference is what you conclude from the data.

From Analysis to Recommendation

Strong analysis should create a logical bridge to your recommendation. Think of the chain as:

Evidence --> What is happening? --> Why is it happening? --> Why does it matter? --> What options does this create? --> Which option is best? --> What should we recommend?

If you cannot draw that connection, the analysis may not be doing enough work.

Avoiding the Fact Dump

A fact dump usually has several characteristics:

too much information;
too many statistics;
frameworks completed without interpretation;
charts without conclusions;
facts that never influence the recommendation;
analysis that describes the past but does not inform the decision;
slides that leave the judges asking, "So what?"

The solution is not necessarily to remove the analysis. The solution is to interpret it. Instead of presenting: "Revenue increased 15%."

Ask: "Where did the growth come from?"
Then: "Is that growth profitable?"
Then: "Is it sustainable?"
Then: "What does that tell us about the decision we need to make?"

Triangulate Your Analysis

Strong case analysis rarely depends on one piece of evidence. Look for relationships between different types of information. For example:

Customer data --> Customer satisfaction is declining.
Operational data --> Service wait times have increased.
Financial data --> Customer churn is reducing recurring revenue.

Together, these provide a much stronger insight: Operational deterioration may be driving customer dissatisfaction, which is contributing to customer churn and declining recurring revenue. The insight becomes stronger because multiple pieces of evidence point in the same direction.

Analysis Should Lead Somewhere

Every major piece of analysis should have a purpose. Ask: Does this analysis help us...

understand the problem?
identify a root cause?
identify an opportunity?
eliminate an alternative?
compare alternatives?
assess feasibility?
quantify impact?
identify risk?
determine implementation requirements?
support the recommendation?

If the answer is no, ask whether the analysis belongs in the solution. Remember: You do not get points for analysing everything. You get points for analysing what matters.

The Analysis Test

Before including a piece of analysis in your solution, ask:

What is the fact?
What does it show?
What is the insight?
Why does it matter?
What decision does it influence?

If you cannot answer all five, keep analysing.

Discover Your MAD Skills Principle

Analysis is not about finding more information. It is about finding meaning in the information you already have.

The strongest case teams are not necessarily the teams with the most analysis. They are the teams that produce the most useful insights.

The Bottom Line

Analysis Is Not a Fact Dump

Analysis is not the collection of facts, charts, frameworks, and numbers. It is the process of determining what the information means and what the organisation should do.
Strong analysis moves through:

FACT → OBSERVATION → INSIGHT → IMPLICATION → DECISION

A fact tells you what you know. An insight explains what that fact reveals.
The implication connects the insight to the organisation's problem, objectives, or decision.
Analysis should ultimately influence the alternatives, recommendation, implementation decisions, or risk assessment.
Do not include analysis simply because you completed it. Ask whether it changes or strengthens the decision.
The most important question after any piece of analysis is:

"So what?"

If you cannot answer it, you have information, not insight.

Chapter 7: Choosing the Right Framework

MasterClasses: Framework-specific videos are available in the second MasterClass -- Case-Solving Toolkit: Frameworks, Analysis & Essential Skills.

Frameworks are among the most recognisable tools in case solving. SWOT. PESTLE. Porter's Five Forces. Value Chain. VRIO. Business Model Canvas. McKinsey 7S. The problem is that many teams learn frameworks as if they were checklists. They see a case and immediately ask: "Which framework should we use?" That is the wrong starting point. The better question is: "What do we need to understand?" Only then should you decide which framework might help.

Frameworks Are Thinking Tools

A framework provides a structured way to examine a problem. It helps you organise information, identify relationships, ask better questions, and compare different aspects of a situation. But the framework itself is not the answer. Frameworks are lenses, not solutions.

A SWOT analysis does not tell you what to recommend.
Porter's Five Forces does not tell you whether the organisation should enter a market.
A Value Chain analysis does not automatically identify the competitive advantage.

The value comes from what you discover and what you do with it.

Start With the Question

Before selecting a framework, complete this sentence: "We need to understand ______ because ______." For example:

We need to understand why profitability is declining so management can determine whether the problem is pricing, volume, cost, or product mix. That question might lead you toward financial analysis rather than a SWOT analysis.
Or: We need to understand whether this industry is attractive because management is considering entering the market. That question may lead you toward Porter's Five Forces.

The question determines the lens.

Choosing the Right Lens

Different frameworks help answer different types of questions.

SWOT

What question does it help answer? What are the organisation's key internal strengths and weaknesses, and what external opportunities and threats should influence its strategy? SWOT examines:

Internal

Strengths
Weaknesses

External

Opportunities
Threats

The danger is treating SWOT as four boxes to fill. The real objective is to identify strategic implications. For example: Strong brand + a growing premium market = an opportunity to expand into a higher-value segment.

Value Chain Analysis

What question does it help answer? Where does the organisation create value, incur cost, or possess capabilities that could create competitive advantage? Use it to investigate:

activities;
costs;
capabilities;
sources of value;
sources of inefficiency;
competitive advantage;
missing capabilities.

The insight might be: The company is not losing competitiveness because of its product. It is losing competitiveness because its distribution system creates significantly higher costs than competitors. That insight can influence the recommendation.

Porter's Five Forces

What question does it help answer? How attractive and competitive is the industry? Porter's Five Forces examine:

rivalry;
buyer power;
supplier power;
threat of new entrants;
threat of substitutes.

The objective is not to rate every force "high" or "low." The objective is to understand what these competitive pressures mean for the organisation's strategic choices.

PESTLE

What question does it help answer? What external forces could materially affect the organisation or its strategic options? PESTLE examine:

Political
Economic
Social
Technological
Legal
Environmental

Again, do not simply list trends. Ask: Which external changes matter to this organisation, and what should it do about them?

Financial Analysis

Financial analysis is another form of structured analysis. When management needs to understand the financial consequences of a decision, tools such as:

ratio analysis;
comparative analysis;
budgeting;
ROI;
NPV;
IRR;
pro forma statements;
valuation;
sensitivity analysis

can help answer important questions. For example:

What happens to revenue?
What happens to costs?
What happens to margins?
What investment is required?
When does the organisation recover its investment?
How sensitive is the result to changing assumptions?

The objective is not to produce a spreadsheet full of calculations. The objective is to answer the strategic question: Is the financial impact large enough to matter to this organisation and this audience? The deeper financial tools are explored throughout Case Finances & Excel Mastery: Turn Numbers into Compelling Insights.

Framework Selection by Case Question

A useful starting point is to think about the question you are trying to answer.

Question	Potential Tool
What is happening inside and outside the organisation?	SWOT
What external forces could affect the business?	PESTLE
How competitive is the industry?	Five Forces
Where is value created or lost?	Value Chain
What capabilities create competitive advantage?	VRIO
How does the organisation create and capture value?	Business Model Canvas
Is the organisation internally aligned?	McKinsey 7S
What is happening financially?	Financial analysis
How attractive is an investment?	ROI / NPV / IRR
How robust is the recommendation?	Sensitivity / Scenario Analysis

These are starting points, not rules. A case may require several tools. A case may require none of them.

The "So What?" Test

After completing any framework, ask: So what? Then ask it again. For example:

SWOT finding

The organisation has a strong brand.

So what? This may allow the company to enter a premium segment more easily.
So what? The premium segment has higher margins and is growing faster than the core market.
So what? A premium extension may provide a stronger growth opportunity than competing directly on price in the existing segment.

Now the framework has produced an insight.

Avoid Framework Overload

One of the easiest ways to weaken a case solution is to use too many frameworks. A team may produce:

SWOT;
PESTLE;
Five Forces;
Value Chain;
VRIO;
BCG;
Ansoff;
Business Model Canvas;

and still not answer the case. More frameworks do not necessarily create better analysis. In fact, framework overload can:

consume valuable case time;
create redundant analysis;
increase slide count;
distract from the central issue;
encourage fact collection rather than insight generation;
make the recommendation feel disconnected from the analysis.

The goal is not to demonstrate how many frameworks your team knows. The goal is to use the fewest tools necessary to answer the most important questions.

The Framework Selection Test

Before using a framework, ask:

What question am I trying to answer? Be specific.
Will this framework help me answer it? If not, choose another tool.
What information do I need? Identify the evidence required to use the framework effectively.
What insight could this framework produce? Do not assume the answer before doing the analysis.
What decision could that insight influence? Connect the analysis to the case decision.
Can I explain the "So What?" If you cannot explain why the finding matters, the framework may not be adding value.

Frameworks Should Connect

Strong case solutions rarely contain isolated frameworks. Instead, insights from one analysis can lead to another. For example:

Five Forces --> Industry rivalry is increasing. --> Customer Analysis --> Customers are becoming more price-sensitive. --> Value Chain --> The organisation has a significant cost disadvantage. --> Financial Analysis --> Reducing costs could materially improve margins. --> Alternatives --> Cost leadership becomes a viable strategic option. --> Recommendation --> Invest in operational efficiency rather than competing through additional product features.

The frameworks are not the solution. They are helping the team build the logic that leads to the solution.

Discover Your MAD Skills Principle

Don't start with a framework. Start with a question.

Then choose the tool that gives you the best chance of answering that question.

The Bottom Line

Choosing the Right Framework

Frameworks are thinking tools, not answers.
Do not automatically use SWOT, PESTLE, Five Forces, or another familiar framework simply because you know how to complete it.
Start with the strategic question:

What are we trying to understand?

Then select the framework or analytical tool that helps answer that question.
SWOT can help identify important internal and external strategic implications.
Value Chain analysis can reveal where value is created, lost, or constrained by capabilities.
Five Forces can help explain competitive pressures and industry attractiveness.
PESTLE can identify external forces that may influence the organisation and its strategy.
Financial tools should help determine whether the impact is large enough to matter and whether the recommendation makes economic sense.
You do not need to show every framework you use. Show the insights that matter.

Before using a framework, ask: What question does it answer? What insight will it produce? What decision will that insight influence? If you cannot answer those questions, reconsider using it.

MadMAD Skills Drill

Select three facts from a case. For each one, complete the Analysis Ladder.

Stage	Question
Fact	What do we know?
Observation	What does the information show?
Insight	What does it tell us that isn't immediately obvious?
Implication	Why does it matter?
Decision	What should we do differently because of it?

Then apply the So What? Test. After every statement, have another teammate ask: "So what?" Keep answering until you reach something that affects:

the problem;
an alternative;
the recommendation;
implementation;
risk.

Framework Challenge: Now identify one framework you might use. Before using it, answer: What question will this framework help us answer? If the team cannot answer that question, don't use it.

Can you draw a clear line from: FACT → INSIGHT → DECISION? If not, you probably have information rather than analysis.