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 them on slides, add graphs, complete frameworks, then make a recommendation. The problem? The analysis never 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 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 becomes 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~~doesn't 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~~doesn't 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 whether this analysis helps 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~~don't 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~~Don't 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.