What is Synthesis in Case Interviews?
Synthesis is delivering a clear recommendation in 30-60 seconds that summarizes your analysis and tells the CEO what to do. It's not a summary of everything you discussed—it's the answer to the original question, supported by 2-3 key reasons.
Quick Facts
| Duration | 30-60 seconds |
| When | End of case (interviewer asks "what do you recommend?") |
| Structure | Recommendation → 2-3 reasons → risks/next steps |
| Common Mistake | Summarizing the case instead of answering the question |
| Weight | 10-15% of case evaluation |
The Synthesis Formula
Use this structure every time:
| Component | Time | Example |
|---|---|---|
| 1. Recommendation | 5-10 sec | "My recommendation is to enter the market." |
| 2. Key Reasons | 20-30 sec | "Three reasons: First... Second... Third..." |
| 3. Risks/Next Steps | 10-15 sec | "Key risk is... I'd want to validate..." |
Good vs. Bad Synthesis
❌ Bad: Summary, Not Synthesis
"So we looked at the market size and found it was $2B. Then we analyzed the competition and saw there are 3 major players. We also looked at the client's capabilities and found they have strong distribution. The profit margin would be around 15%..."
Problem: Recaps the analysis but doesn't answer the question.
✅ Good: Action-Oriented Synthesis
"My recommendation is to enter the market. Three reasons: First, the $2B market is growing 8% annually with fragmented competition. Second, our client's existing distribution network provides a cost advantage of 15% versus new entrants. Third, we can achieve 15% margins within 2 years. The main risk is competitor response—I'd recommend a pilot in the Midwest before full rollout."
Why it works: Leads with the answer, supports with evidence, acknowledges risk.
Common Mistakes
| Mistake | Fix |
|---|---|
| Summarizing instead of recommending | Start with "My recommendation is..." |
| Being too long (2+ minutes) | Limit to 3 reasons, 60 seconds max |
| Forgetting the original question | Write it down at the start; answer it directly |
| Hedging too much ("It depends...") | Take a stance; acknowledge risks separately |
| No next steps or risks | Always mention what you'd validate |
Frequently Asked Questions
What if I don't have enough information to make a recommendation?
Make a recommendation anyway with the information you have. State your key assumption: "Assuming the market research confirms X, my recommendation would be..." Interviewers want to see you take a stance.
Should I use numbers in my synthesis?
Yes. Numbers make your recommendation concrete: "$5M profit in year 1" is stronger than "significant profit opportunity." Reference key calculations from your analysis.
How do I prepare for synthesis during the case?
Track key findings as you go. After each analysis area, note the main insight. When asked to synthesize, you'll have your 2-3 reasons ready without scrambling.
Related Terms
Practice Your Synthesis
AI-powered case simulations that prompt you for synthesis and give real-time feedback on your delivery.
Start Practicing