Author: Taylor Warfield, Former Bain Manager and interviewer

Last Updated: October 21, 2026

 

Case interview synthesis is the skill of converting your analysis into a clear recommendation, and the strongest candidates use it at four separate points in a case rather than only at the end. This guide gives you the exact structure, the timing, word-for-word scripts, and the six mistakes that quietly cost candidates offers.

 

Before reading on:

 

Most candidates struggle to land interviews and even fewer turn them into offers. Watch my free training to learn how to triple your chances of landing interviews and increase your chances of receiving an offer by 8x.

 

👉 Watch for free

 

Key Takeaways

 

Synthesis means telling the interviewer what your findings mean and what the client should do, delivered answer first in 60 to 90 seconds.

 

• A summary repeats what you found, while a synthesis says what it means for the decision

 

• Lead with your recommendation, then give 2 or 3 reasons backed by case numbers, one risk, and one next step

 

• Synthesize four times per case: after the prompt, after each exhibit, after each calculation, and at the close

 

• Keep the closing synthesis to 60 to 90 seconds and never replay your framework

 

• Take a position even with incomplete data by making your recommendation conditional on one specific fact

 

What Is Synthesis in a Case Interview?

 

Synthesis in a case interview is the act of converting your analysis into a clear, evidence-backed answer to the client's question. Rather than restating what you found, you state what the client should do, give 2 or 3 supporting reasons drawn from case data, name the biggest risk, and propose a concrete next step.

 

The term is borrowed directly from consulting practice. Every client meeting I sat in on at Bain opened with the answer, then worked backward into the evidence. A case interview compresses that same discipline into 90 seconds.

 

Most candidates assume synthesis happens once, at the very end, when the interviewer asks for a recommendation. That assumption is the single most expensive misunderstanding in case prep. It is why a candidate can run flawless math and still receive a no-hire vote.

 

What Is the Difference Between Synthesis and Summary?

 

A summary reports what you found. A synthesis reports what it means and what the client should do about it. The gap sounds academic until you hear both versions back to back.

 

What the interviewer hears	Summary	Synthesis
Opening words	"So we looked at..."	"I recommend that..."
Organizing logic	The order you discovered things	The order that supports the decision
Use of numbers	Numbers are reported	Numbers are used as proof
Ending	Trails off or hedges	Names a risk and a next step
Signal sent	You completed the steps	You can sit in front of a client

 

This distinction has a documented origin inside consulting. Barbara Minto, the first female MBA professional hire McKinsey ever made, worked at the firm from 1963 to 1973 and noticed that consultants kept jumbling findings and conclusions in a way that pointed to no clear recommendation.

 

Her diagnosis was blunt: the problem was the thinking, not the language. People were writing before they had worked out what they actually believed. The fix became the Minto Pyramid Principle, first published in book form in 1985.

 

Minto's core rule applies directly to your close: the point at the top must be a genuine summary of the points below it. Your recommendation sits at the top, and every supporting reason has to be a reason for that recommendation, not simply something you happened to calculate. She also coined MECE, the requirement that your supporting groups be mutually exclusive and collectively exhaustive.

 

Why Does Synthesis Matter So Much to Interviewers?

 

Synthesis matters because it is the only part of the case that looks exactly like the job. Everything else is a proxy. Four reasons drive the weight interviewers place on it:

 

• It is the last thing your interviewer hears before writing the evaluation, so it colors the entire scorecard

 

• It mirrors what consultants actually do in front of clients, where nobody has 40 minutes to watch you think

 

• It reveals whether you solved the case or merely completed the steps

 

• It carries disproportionate weight in final rounds, where partners already assume you can do the math

 

Synthesis is scored separately from structuring and quantitative work, which is one of the things interviewers look for in case interviews that candidates most often overlook. You can be graded strong on analysis and weak on communication in the same interview. Those are two different boxes on the form.

 

The gap widens at the partner stage. In my experience at Bain, the ability to deliver a crisp, top-down recommendation in under a minute was frequently the difference between a yes and a maybe in the debrief. That pattern holds at the McKinsey final round interview as well, where partners care less about whether you landed the exact right answer and more about whether they would put you in a room with a CEO.

 

When Should You Synthesize During a Case Interview?

 

You should synthesize four times in a single case, not once. Strong candidates deliver a short synthesis after the prompt, after every exhibit, after every calculation, and at the close. Three of those four are unprompted, which is precisely why they separate candidates.

 

Moment	When it happens	Length	What it must contain
1. Prompt playback	Right after the interviewer finishes reading	15 to 20 seconds	The client situation and the objective, in your own words
2. Exhibit read	After you finish reading a chart or table	10 to 15 seconds	The one insight that matters and why it matters
3. Post-calculation	The moment you land on a number	10 to 15 seconds	What the number implies for the recommendation
4. Closing recommendation	When the interviewer asks for your answer	60 to 90 seconds	Recommendation, 2 or 3 reasons, one risk, one next step

 

Moment 1: How Do You Synthesize the Case Prompt?

 

Play the prompt back in 2 or 3 sentences that name the client, the relevant context, and the objective. Do not repeat every detail the interviewer gave you. Pick the facts that will drive the analysis and drop the rest.

 

Here's an example. "So our client is a national grocery chain with $5B in annual revenue. Margins have declined for two straight years, and our objective is to find the root cause and recommend a fix."

 

That takes 15 seconds and it anchors the entire case interview structure that follows. It also gives the interviewer a chance to correct you before you build 30 minutes of analysis on the wrong objective.

 

Moment 2: How Do You Synthesize an Exhibit?

 

After you read a chart, lead with the insight, not the description. Weak candidates narrate the axes. Strong candidates name the one thing on the page that changes the answer.

 

Weak: "This chart shows revenue by segment from 2021 through 2025, and we can see four segments here." Strong: "The story here is mix. Total revenue is flat, but that hides a 30% decline in the highest-margin segment, which explains the margin drop we're trying to solve." Reading case interview graphs quickly is only half the skill, and the synthesis is the other half.

 

Moment 3: How Do You Synthesize After Math?

 

The moment you land on a number, say what it means before the interviewer asks. A bare figure is a summary. A figure plus an implication is a synthesis.

 

Weak: "So the payback period is 2.5 years." Strong: "Payback is 2.5 years, which is inside the client's three-year hurdle, so cost is not the blocker here and I want to shift to demand." That second version does two jobs at once: it proves the case interview math and it drives the case forward without waiting for permission.

 

Mid-case synthesis is also where you update your case interview hypothesis out loud. When a finding contradicts what you expected, saying so is a strength, not an admission of failure. Interviewers are explicitly watching whether you adjust when the data pushes back.

 

Moment 4: How Do You Synthesize at the End of the Case?

 

This is the one everybody prepares for and the one most candidates still rush. Your closing case interview recommendation is a 60 to 90 second answer delivered top down, with a stated risk and a concrete next step.

 

The prompt differs by firm. In an interviewer-led case interview, which is the McKinsey format, you will be asked directly and often handed 30 seconds to organize your thoughts. In candidate-led cases at BCG and Bain, nobody may invite you, so you have to recognize that the analysis is finished and close on your own.

 

McKinsey publishes four practice cases on its careers site, and each one builds toward a decision the client has to make. Reading how the firm frames those questions tells you exactly what a close is supposed to deliver.

 

How Do You Structure a Case Interview Synthesis?

 

Use a four-part structure delivered in this exact order. The order is not stylistic. It is how consultants are trained to talk to executives who have no patience for suspense.

 

1. Recommendation: one sentence, roughly 10 seconds, stating what the client should do
   
   
2. Supporting reasons: 2 or 3 reasons, roughly 35 seconds, each tied to a specific number from the case
   
   
3. Key risk: the single biggest thing that could go wrong, plus how you would mitigate it, roughly 15 seconds
   
   
4. Next step: one concrete action that would validate the recommendation, roughly 10 seconds

 

Give 2 or 3 reasons, never 5. Listing everything you found is a prioritization failure dressed up as thoroughness. Interviewers read a long list as evidence that you could not decide which findings mattered.

 

Total time should land between 60 and 90 seconds, or roughly 150 to 200 spoken words. If you want to build these habits fast, my case interview course walks you through the full case structure and the closing script in as little as 7 days.

 

What Does a Strong Case Interview Synthesis Sound Like?

 

The fastest way to hear the difference is to compare a weak close and a strong close on the same case. Both candidates did identical analysis. Only one of them gets the offer.

 

Weak Synthesis: What Most Candidates Actually Say

 

"So we looked at the market and it's growing. We also looked at costs, and those came in higher than expected. On the customer side there's demand, but competitors are strong, so overall I think there's an opportunity but also some risk."

 

Four problems, all fatal. There is no recommendation, no structure, no number cited as proof, and hedging in every clause. The interviewer cannot write anything useful in the evaluation box.

 

Strong Synthesis: Market Entry Example

 

"I recommend the client enter the Southeast Asian market through organic expansion, for three reasons. First, the market is $8B growing at 15% a year, the fastest in their category. Second, they already have distribution in two neighboring markets, which cuts setup cost by roughly 40%."

 

"Third, no competitor holds more than 12% share, so there's room for a well-funded entrant. The main risk is currency volatility, which I'd mitigate with local pricing and hedging. As a next step, I'd run a pilot in Thailand to test demand before committing to a full regional rollout."

 

Notice what that close does. It commits in the first six words, it cites a real number in every reason, and it ends with something the client could actually do on Monday morning.

 

Strong Synthesis: Profitability Example

 

"I recommend the client cut the private-label line and reinvest the freed capacity into the premium line, which should recover roughly $12M of the $15M margin gap. First, private label runs at a 4% margin against 22% for premium, so the mix shift is the fastest lever available."

 

"Second, the capacity is fungible: the same three plants make both lines, so this is a scheduling change rather than a capital project. The main risk is losing the two retail accounts that buy both lines, so I'd sequence the exit account by account. The first step is a 90-day margin audit on those two accounts to size the exposure."

 

Both examples follow the same four-part order regardless of case type. That consistency is the point. You should not be inventing a closing format under pressure at minute 38.

 

How Do You Synthesize When You Are Not Sure of the Answer?

 

Give a conditional recommendation rather than refusing to commit. Name the direction you lean, state the one specific fact that would change your mind, and say how the client would get that fact. Interviewers reward a defensible position under incomplete information and penalize candidates who will not take one at all.

 

Here's the script. "Based on what we've analyzed, I'd lean toward entering, but I'd want to validate supplier capacity before a final decision."

 

"If suppliers can support 2x volume within 18 months, this is a clear yes. If not, I'd delay entry by a year and revisit."

 

That answer is decisive and honest at the same time. Compare it to "it depends on a few factors," which tells the interviewer nothing and reads as avoidance. The good news is that this is a scripted move you can rehearse before you ever need it.

 

What Are the Most Common Case Interview Synthesis Mistakes?

 

Six mistakes account for most weak closes. Each of them is a habit, which means each of them is fixable in a week of deliberate practice. They also show up on nearly every list of the case interview mistakes that lead to rejections.

 

Mistake	What it sounds like	The fix
Replaying the framework	"First I looked at market, then competition, then..."	Start with the recommendation and never mention your buckets
Refusing to commit	"There are pros and cons on both sides"	Take a stance, conditional if necessary
Listing too many reasons	Five or six supporting points in a row	Cut to the 2 or 3 that actually drive the answer
Citing no evidence	"The market seems attractive"	Attach a specific case number to every reason
Skipping the risk	Only the upside, no downside named	Name one real risk and how you would mitigate it
Running long	Three-plus minutes of talking	Cap it at 90 seconds and rehearse with a timer

 

The first mistake deserves extra attention. Walking back through your case interview frameworks at the close is the most common failure I saw as an interviewer, and it happens because candidates confuse showing their work with delivering an answer.

 

Your structure was scored 30 minutes ago. Nobody needs to hear it twice.

 

How Do You Practice Case Interview Synthesis?

 

Practice synthesis as its own drill rather than treating it as the tail end of a full case. Most candidates do 30 cases and get 30 reps of framework building but only a handful of real closing reps, because they run out of time or energy before the end. Five tips fix that imbalance.

 

Tip #1: Close every practice case out loud, even when you run out of time

 

If your practice partner cuts the case short, deliver the synthesis anyway. The close is the rep you can least afford to skip. Silently thinking "I would have said X" builds nothing.

 

Tip #2: Record yourself and time it with a stopwatch

 

Almost every candidate believes their close is 60 seconds when it is actually 2 minutes. Recording is the only way to catch that. Listen back for filler words and for how many seconds pass before you say the word "recommend."

 

Tip #3: Drill closes from written case summaries

 

Take the findings from any of these case interview examples, skip the analysis entirely, and deliver only the 60-second close. You can get 10 synthesis reps in the time one full case takes. This is the highest-return drill in case prep and almost nobody does it.

 

McKinsey's published Talbot Trucks case works well for this, since it ends on an investment decision that forces you to take a real position. Read the setup and the data, then close it cold without doing the intermediate work.

 

Tip #4: Write the first sentence before you speak it

 

When the interviewer gives you 30 seconds to prepare, spend it drafting the recommendation sentence word for word. Everything downstream gets easier once the top of the pyramid is fixed. Do not spend that time re-reading your notes.

 

Tip #5: Get feedback from someone who has actually interviewed candidates

 

Peers can tell you whether your math was right, but they usually cannot tell you whether your close would land with a partner. That judgment comes from having sat on the other side of the table. My case interview coaching gives you that feedback directly from a former Bain interviewer.

 

Case interview synthesis is the cheapest way to raise your score, because it is the one skill that shapes how an interviewer remembers everything else you did. Start closing every practice case out loud this week, timed, with the four-part structure. That one habit will do more for your offer odds than another twenty framework drills.

 

Frequently Asked Questions

 

What is synthesis in a case interview?

 

Synthesis in a case interview is the act of turning your analysis into a clear, evidence-backed answer to the client's question. A summary tells the interviewer what you found. A synthesis tells them what it means and what the client should do next. Interviewers score it separately from structure and math because it is the skill consultants use in front of clients every week.

 

How long should a case interview synthesis be?

 

Your closing synthesis should run 60 to 90 seconds. That is roughly 150 to 200 spoken words, which is enough for a recommendation, 2 or 3 supporting reasons, one risk, and one next step. Mid-case syntheses are much shorter at 10 to 20 seconds each. Anything past two minutes signals that you cannot prioritize.

 

What is the difference between synthesis and summary in a case interview?

 

A summary restates facts in the order you discovered them. A synthesis reorganizes those facts around a decision and leads with the answer. If your closing starts with the words "we looked at," you are summarizing. If it starts with "I recommend," you are synthesizing.

 

Should I start with my recommendation or my supporting reasons?

 

Always start with the recommendation. Consulting firms train people to communicate top down, meaning the main message comes first and the supporting arguments follow. Leading with your reasons forces the interviewer to hold every fact in memory while waiting to learn what it adds up to, which is exactly the habit consulting training is designed to break.

 

What if my analysis does not support a confident recommendation?

 

Give a conditional recommendation instead of hedging. Name the direction you lean, state the one specific fact that would change your answer, and propose how the client would get that fact quickly. Interviewers reward candidates who take a defensible position under incomplete information, and they penalize candidates who refuse to commit at all.

 

Do McKinsey, BCG, and Bain evaluate synthesis differently?

 

The standard is the same at all three firms, but the prompting differs. McKinsey runs interviewer-led cases, so you will usually be asked directly for a recommendation and often given 30 seconds to prepare it. BCG and Bain cases are more candidate-led, so you are expected to recognize when the analysis is finished and close without being invited to.

 

Everything You Need to Land a Consulting Offer

 

Need help passing your interviews?

• Case Interview Course: Become a top 10% case interview candidate in 7 days while saving yourself 100+ hours
  
  
• Fit Interview Course: Master 98% of consulting fit interview questions in a few hours
  
  
• Interview Coaching: Accelerate your prep with 1-on-1 coaching with Taylor Warfield, former Bain interviewer and best-selling author

 

Need help landing interviews?

• Resume Review & Editing: Craft the perfect resume with unlimited revisions and 24-hour turnaround

 

Need help with everything?

• Consulting Offer Program: Go from zero to offer-ready with a complete system

 

Not sure where to start?

• Free 40-Minute Training: Triple your chances of landing consulting interviews and 8x your chances of passing them