Synthesis & recommendation

In the last few chapters, you learned how to move through the case: clarify the question, build a structure, do the math, and read exhibits. Now comes the part that makes all of that work matter.

You have to tell the client what to do.

This is where many candidates get nervous, even after a strong case. They have good notes. They have useful findings. They know some things. But when the interviewer says, "So, what would you recommend?", everything suddenly feels too big to compress.

The intuition

Synthesis is not a summary.

Synthesis is turning analysis into a decision.

A summary says:

A synthesis says:

One tells the interviewer what happened in the case. The other tells the client what to do next.

And that is the moment the case becomes real. In consulting, the work does not end when the spreadsheet is right or the chart is understood. It ends when someone can make a better decision because of what you found.

Why it matters

Synthesis is one of the clearest signals of judgment.

The interviewer is asking:

• Can you answer the original question?
• Can you separate what matters from what was merely discussed?
• Can you support your answer with evidence?
• Can you be decisive without pretending the world is perfectly certain?
• Can you name the risk and the next step?

That is why a good final recommendation feels different from a student recap. It sounds like someone who can sit in front of a client and say, calmly:

You are not being judged on whether you uncovered every possible fact. You are being judged on whether you can use the facts you have to move the decision forward.

The core moves

You will not say it exactly like that every time. But it gives you a clean shape when the pressure rises.

Throughout this chapter, we will keep using the same example: a coffee chain whose profits dropped 15% last quarter. Imagine that, by the end of the case, you have learned:

1. Re-anchor: answer the question that was actually asked.

Before you recommend, remind yourself what the client wanted. Not out loud for 20 seconds; just enough to make sure your answer is aimed at the right target.

That means your recommendation needs two things: a diagnosis and an action.

If you only say, "Region B revenue fell," you diagnosed part of the problem but did not recommend. If you only say, "They should do marketing," you recommended without grounding it in the diagnosis. The best recommendations do both.

2. Answer: take a clear position.

This is the move candidates dodge most. The whole recommendation stands or falls here.

The clear version tells the client where to focus and what problem to solve. You can still be nuanced, and you can still name uncertainty, but you need a point of view.

3. Evidence: support the answer with only what matters.

You do not need every fact from the case. You need the two or three facts that make your answer feel inevitable.

Notice what is happening. The candidate is not dumping notes. They are choosing the evidence that supports the decision.

4. Risk: show judgment, not fear.

A risk is not a way to weaken your answer. It is a way to show that you understand the real world.

The useful version works because it is tied to the recommendation. Specific risks make you sound commercially aware.

5. Next step: make the recommendation actionable.

The next step answers one question:

That next step is practical. It reduces risk, names what to measure, and does not pretend the first answer has solved every detail forever.

Interim synthesis: do not save it all for the end

Final recommendations get easier when you synthesize throughout the case. Every time you turned a number into an implication in the math chapter, or said what a chart meant in the exhibits chapter, that was a small synthesis. The habit just becomes explicit here.

That is not a final recommendation. It is an interim synthesis. It keeps the case from becoming a pile of disconnected facts, and it makes the final recommendation much easier because you have been building the story all along.

What weak looks like

What strong looks like

It is not perfect, because real business never is. But it is useful. And useful is the point.

Summary vs synthesis vs recommendation

These words get blurred, so separate them before the final minute.

How to be decisive when you are not 100% sure

You will rarely have perfect information in a case. That is not a flaw in your prep; it is the point.

Phrases like "based on the analysis so far," "my current recommendation is," or "with the information we have" let you take a real position without pretending you have solved every unknown.

Common traps

The most common trap is wanting to sound complete. Do not aim for complete. Aim for clear.

Your 5-minute drill

Use the case notes below. Give yourself 60 seconds to prepare, then deliver a 30-45 second recommendation out loud.

How to use this later in CaseLab

When you begin live practice later, use this chapter as your feedback lens. You do not need to run a full mock case right now; for today, just know what good synthesis should sound like.

1. After each major finding, give a short interim synthesis.
2. At the end, give a final recommendation using answer, evidence, risk, and next step.

Later, when you do a live CaseLab rep, review whether you answered the original question, led with a clear recommendation, used the strongest evidence, named a real risk, and gave an actionable next step.