Case Interview Synthesis: 60-Second Recommendation Template + Examples

Case interview synthesis is your 60-second closing recommendation that follows the Pyramid Principle: lead with your answer ("I recommend X"), support it with 2-3 reasons backed by case evidence, acknowledge risks, and suggest next steps. Interviewers weight recommendation clarity at roughly 40% of the synthesis score.

Why Synthesis Matters More Than You Think

Synthesis is the single most under-practiced skill in case prep. Candidates spend hours on frameworks and mental math for case interviews but wing the closing. Here's why that's a mistake:

• It's the last thing the interviewer hears. Recency bias means your synthesis disproportionately shapes their evaluation.
• It tests a core consulting skill. Partners present recommendations to CEOs. If you can't synthesize, you can't do the job.
• It reveals whether you actually solved the case. A vague synthesis signals that you followed the steps but never connected the dots.

For a structured approach to building strong foundational skills before synthesis, review our guide on how to practice case interviews.

The Synthesis Framework

The pyramid principle, developed by Barbara Minto while at McKinsey in the 1960s–70s and published in The Pyramid Principle: Logic in Writing and Thinking (Pearson, 1987), says you lead with the answer, then support it with grouped arguments. Every level of the pyramid answers "why?" or "how?" for the level above it. In a 60-second synthesis, the structure looks like this:

Framework

Pyramid Principle for Synthesis

1. 01

   Recommendation

   Clear answer to the case question

2. 02

   Reason 1

   Strongest supporting argument + evidence

3. 03

   Reason 2

   Second supporting argument + evidence

4. 04

   Risks & next steps

   Key risk + what to validate next

Part 1: The Recommendation (10 seconds)

State your answer clearly and directly. Use language like:

• "I recommend that the client enter the European market through a joint venture."
• "Based on our analysis, the client should not acquire Company X."
• "The client should raise prices by 8-10% on the premium product line."

Avoid hedging: "It depends" or "There are pros and cons" is not a recommendation.

Part 2: Supporting Reasons (30-40 seconds)

Give 2-3 reasons that directly support your recommendation. Each reason should:

1. State the insight: "First, the market is large and growing at 12% annually."
2. Cite the evidence: "We saw that the European market is $5B with projected growth driven by regulatory tailwinds."
3. Connect to the recommendation: "This makes it attractive enough to justify the investment."

Keep to 2-3 reasons. More than that dilutes your message and suggests you can't prioritize.

Part 3: Risks and Next Steps (15-20 seconds)

Acknowledge the main risk and what you'd want to do next:

• Risk: "The main risk is regulatory uncertainty in Germany, which could delay entry by 6-12 months."
• Next step: "Before committing, I'd recommend the client conduct detailed regulatory due diligence and identify potential JV partners with local expertise."

This shows maturity and realism, you're not blindly advocating.

Good vs. Bad Synthesis: Side by Side

Bad synthesis (what most candidates do):

"So we looked at the market and it's growing. We also looked at costs and they're higher than expected. On the customer side, there's some demand. The competitors are strong but there might be an opportunity. Overall, I think there's potential but also risk."

Problems: No clear recommendation, no structure, no evidence, hedging throughout.

Good synthesis (market entry):

"I recommend the client enter the Southeast Asian market through organic expansion, for three reasons. First, the market is $8B and growing at 15% annually, making it the fastest-growing region in their category. Second, the client already has distribution infrastructure in neighboring markets, reducing setup costs by an estimated 40%. Third, the competitive landscape is fragmented, no player holds more than 12% share, creating space for a well-resourced entrant. The main risk is currency volatility, which I'd mitigate with local pricing and hedging. As a next step, I'd recommend a pilot launch in Thailand to test demand before a full regional rollout."

This takes about 60 seconds to deliver and covers all four elements. Notice how the supporting reasons draw from core frameworks like the profitability framework to structure the economic logic.

Growth case synthesis example:

"I recommend the client pursue a three-phase growth plan targeting $200M in incremental revenue over 3 years. First, cross-sell the premium product to the existing enterprise base, our analysis shows a 25% attach rate is achievable, generating $80M. Second, expand into the mid-market segment where we currently have zero presence but strong product fit, adding $70M. Third, evaluate a tuck-in acquisition of [competitor] to accelerate geographic coverage, contributing $50M. The main risk is mid-market channel build time. I'd mitigate by partnering with an established reseller in year one. As a next step, I'd pressure-test the 25% attach rate assumption with a 90-day pilot."

Notice the pattern: specific numbers, phased approach, quantified risk, and a concrete next step. Both examples follow the same pyramid structure regardless of case type.

For growth and expansion closes, reuse the same logic with market entry framework, growth strategy cases, and pricing strategy cases. For more worked walkthroughs, see case interview examples.

Practice Prompt: Build Your Own Synthesis

Try it yourself: Your case: A PE firm is evaluating a $200M hospital chain acquisition. You found: strong revenue growth (12% CAGR), but margins declining due to nurse labor costs (+22% in 3 years), and the management team has no turnaround experience. Write your 60-second synthesis before reading on.

Take 60 seconds. Say it out loud. Then compare to the model answer below.

What makes this work: it takes a clear stance (pass), quantifies the reasoning, and turns the "pass" into a conditional that shows commercial judgment, not just risk aversion.

How to Practice Synthesis

Technique 1: Synthesize Every Case You Practice

After every practice case, take 60 seconds to deliver a synthesis out loud. Record yourself and listen back. Ask:

• Did I lead with a clear recommendation?
• Did I give exactly 2-3 supporting reasons?
• Did I mention a risk and next step?
• Was it under 90 seconds?

Technique 2: Synthesize During the Case

Don't wait until the end to start thinking about synthesis. As you work through each branch of the case, mentally note:

• "This is probably going to be my strongest reason for recommending X."
• "This data point contradicts my initial hypothesis, I need to adjust."

By the time the interviewer asks for your recommendation, you should already know it.

Synthesis Scoring Rubric (What Interviewers Notice)

Interviewers weight synthesis dimensions unevenly. Based on patterns across MBB feedback (corroborated by IGotAnOffer's case interview prep guide and caseinterview.com's synthesis guide): Recommendation clarity (40%) > Evidence quality (25%) > Risk handling (20%) > Next steps (15%). Most candidates over-invest in listing evidence and under-invest in the recommendation and risk framing, exactly backwards.

Common Synthesis Mistakes

Interactive Synthesis Drills

Test Your Understanding

Test yourself

1 / 3

Question 1 of 3

What should be the first thing you say in your synthesis?

• AA summary of your analysis approach
• BYour recommendation
• CThe key risk
• DA clarifying question

Related Skills

Synthesis is the final step. Build the earlier skills that feed into a strong closing:

• MECE principle explained -- the structuring standard that ensures your synthesis covers the right ground
• Profitability framework -- the most common case type, where synthesis ties diagnosis to quantified actions
• Case interview examples -- 12 fully worked cases with end-to-end synthesis examples
• Case interview questions -- the 6 question types you will face, including recommendation questions

Sources and Further Reading (checked February 7, 2026)

• Minto, Barbara. The Pyramid Principle: Logic in Writing and Thinking. Pearson, 1987. Minto developed the pyramid/MECE framework at McKinsey in the 1960s–70s; this remains the standard reference for consulting communication. See also: McKinsey Alumni: "MECE: I invented it, so I get to say how to pronounce it".
• CaseInterview.com, synthesis in case interviews: caseinterview.com/synthesis-in-case-interviews
• IGotAnOffer, case interview prep guide: igotanoffer.com/blogs/mckinsey-case-interview-blog/case-interview
• McKinsey interviewing resources: mckinsey.com/careers/interviewing
• Management Consulted case interview resources: managementconsulted.com/case-interview