Survival Guide for Your First Case Interview

(Or: everything you learned in this series, now put together into one game plan)

You’ve already seen, separately, analytical thinking, conceptual thinking, quantitative thinking, communication, and SWOT and Porter’s Five Forces. This is the guide that pulls it all together into one step-by-step process, for when you have a real case in front of you.

Step 1: listen to (or read) the whole case before reacting

The most common mistake, under time pressure, is starting to think about solutions before you’ve finished understanding the whole problem. Take a moment to make sure you understand: what exactly is the question being asked? Sometimes the case mentions a lot of information, but the real question is more specific than it looks at first glance.

“Quickly solving the wrong question is worse than calmly solving the right one.”

Step 2: structure the problem before you opine (analytical thinking)

Break the problem into MECE categories (mutually exclusive, collectively exhaustive). If the case is about a sales drop, for example, split the possible causes into internal, market, and external factors, like we saw before. You can say it out loud: “To analyze this, I’m going to look at it from these angles…”

Step 3: form an initial hypothesis (conceptual thinking)

With your structure already built, propose a tentative explanation of what you think is happening, and what evidence you’d need to confirm or rule it out. This gives your analysis direction, instead of investigating everything with no clear path.

Step 4: use the data you have (and estimate what’s missing)

Work with the numbers and data the case gives you. If key information is missing, don’t freeze up — estimate with logic, like in the “how many pianos are there in Quito” exercise. Show your reasoning step by step, not just the final result.

Step 5: apply a framework if it helps (SWOT / Five Forces)

If the case calls for it, use SWOT to organize the company’s strengths and weaknesses, or Porter’s Five Forces if the problem is about how competitive the entire industry is. Don’t force a framework if it doesn’t naturally fit the problem — only use it when it actually adds clarity.

Step 6: build a clear recommendation

With all the analysis above, arrive at a specific, actionable recommendation. Avoid vague answers like “they should improve their marketing” — be specific: “they should increase their digital ad budget targeting customers aged 18-25 by 20%, based on that segment growing fastest according to the case data.”

Step 7: communicate with a pyramid structure

Present your recommendation first, then the 2-3 main arguments supporting it, and have the detailed evidence ready in case they ask for more. Don’t tell your whole research story in chronological order — go straight to the conclusion.

Step 8: prepare to defend it, not to memorize it

Anticipate the hardest questions you could get about your recommendation, and have a thought-out answer for each one. If someone points out a real weakness in your analysis, acknowledge it maturely — showing you can think in real time, adjusting your position with new information, is worth more than pretending you have no doubts.

The whole thing summarized in one mental table

• Understand the real problem before reacting.
• Structure it with MECE.
• Propose a clear hypothesis.
• Calculate or estimate with logic.
• Use frameworks (SWOT, Porter) if they add clarity.
• Recommend something specific and actionable.
• Communicate with the conclusion first.
• Defend your analysis calmly and honestly.

“No business case gets solved with a magic trick. It gets solved with an orderly process, applied calmly, even while the clock is running.”

With this guide, you now have the complete map for facing any business case put in front of you — at the Olympiad, or at any future point in your career where you have to solve a complex problem with incomplete information and not enough time.