14.1 Why Cases Cannot Be Solved by Analyzing Everything
A real business problem may contain dozens of potential drivers. A case interview compresses that complexity into a short conversation, so trying to investigate everything is impossible.
Suppose profits are declining. You could examine pricing, volume, product mix, customers, competitors, labor, materials, logistics, rent, marketing, technology, and many other areas. Working through all of them equally would consume the entire interview.
Core principle: The goal is not exhaustive analysis. The goal is sufficient analysis to identify the most important drivers and support a sound decision.
Strong candidates continuously ask which question is most likely to move the case forward.
14.2 Identifying High-Impact Branches
Once you have a structure, identify which branches could have the greatest effect on the client’s objective.
If a retailer wants to improve profit by $50 million, a cost category worth only $2 million annually is unlikely to be the first place to focus. Pricing, labor, or sourcing may offer much larger opportunities.
Useful question: “If this branch turns out to be important, could it materially change the answer?”
High-impact branches are not always the largest categories, but they should have the potential to affect the recommendation meaningfully.
14.3 Using Magnitude to Prioritize
Magnitude is one of the fastest ways to determine what deserves attention.
Look for the largest revenue streams, cost categories, customer segments, geographies, or operational bottlenecks. A 5 percent change in a $1 billion business may matter more than a 50 percent change in a $2 million activity.
Practical habit: Estimate the size of the issue before conducting detailed analysis.
If an opportunity is too small to meet the client’s objective, you can often eliminate it quickly. This is especially useful in growth, cost-reduction, and profitability cases.
14.4 Using Probability to Prioritize
Magnitude alone is not enough. You should also consider how likely an explanation or opportunity is to be relevant.
Suppose a company’s profits fell immediately after a major supplier increased prices. Procurement costs may deserve attention before less likely explanations such as corporate overhead.
Priority logic: Focus first on issues that combine meaningful potential impact with a reasonable likelihood of explaining the problem.
Do not confuse probability with certainty. You are choosing where to investigate first, not deciding the answer before seeing the evidence.
14.5 Using Client Context to Prioritize
The case prompt often contains information that helps determine what matters most.
If the client says customer retention has deteriorated, investigate retention rather than immediately analyzing every possible growth lever. If the company has reached maximum factory utilization, capacity may deserve priority in a growth case.
Client context includes:
- Recent changes: What happened just before the problem appeared?
- Known constraints: What limits the available options?
- Management concerns: What issues are already considered important?
- Strategic priorities: What outcomes matter most to the organization?
Good prioritization: Combines business logic with the specific facts of the case.
14.6 Developing Shortcuts Without Becoming Careless
Efficient problem solving often requires shortcuts. You may round numbers, use estimates, eliminate obviously unattractive options, or test a representative segment before expanding the analysis.
The important distinction is between simplification and sloppiness.
Good shortcut: Rounding $498 million to $500 million when estimating a percentage impact.
Careless shortcut: Ignoring a major cost category because it makes the calculation easier.
State important assumptions and check whether your approximation could materially change the answer. If not, move forward.
14.7 Knowing When to Move On
A common case-interview mistake is continuing to analyze a question after it has already yielded the necessary insight.
You should consider moving on when:
- The hypothesis has been confirmed or rejected: Additional analysis is unlikely to change that conclusion.
- The issue is too small: Its maximum possible impact would not matter.
- The result is clear: More precision would not change the recommendation.
- A higher-priority question remains: Time would be better spent elsewhere.
Strong transition: Briefly synthesize what you learned, explain what it means, and identify the next most important question.
14.8 Avoiding Analytical Rabbit Holes
An analytical rabbit hole occurs when you spend too much time investigating an interesting detail that does not materially affect the client’s decision.
This often happens because the analysis feels intellectually satisfying. A candidate notices an unusual customer segment or complicated cost pattern and keeps exploring it even though the issue is small.
To avoid this, regularly reconnect your analysis to the objective.
Ask yourself: “If I knew the answer to this question, what would I do differently?”
If the answer is “probably nothing,” stop.
You should also watch for diminishing returns. The first few minutes of analysis may provide most of the insight, while additional work adds only minor precision.
Final principle: Prioritization means making deliberate choices about where to spend your limited time. Use magnitude, probability, client context, and decision relevance to determine what matters most. The 80/20 mindset is not about cutting corners. It is about applying rigor where rigor matters and avoiding analysis that will not change the answer.
