Synthesis vs Summary
A summary restates what was found; a synthesis says what it all means together - the difference between listing findings and delivering an insight.
What it is
A summary recaps the pieces of analysis you did - 'we looked at the market, the costs, and the competition, and here is what each showed'. A synthesis goes one crucial step further: it combines those pieces into a single overarching message about what they mean together and what to do about it. The distinction is the gap between a competent analyst and a trusted advisor. Anyone can list findings; synthesis is the act of weaving them into a 'so what' - the one thing the decision-maker should take away. It answers not 'what did you find?' but 'what should I conclude and do?', which is the question that actually matters.
When to use it
Use synthesis at the close of any case, at the end of a chunk of analysis, and whenever you are asked 'so what does all this mean?'. It is the expected register for a final recommendation and for updating an interviewer after a phase of work. A plain summary is appropriate only in narrow moments - confirming shared facts, or recapping a long discussion before moving on - but even then a synthesizing line is usually better. Do not deliver a summary when a decision is being asked for; restating findings without a conclusion reads as an inability to commit to a point of view.
How to apply it
After gathering findings, ask yourself the forcing question: 'so what?' - and then 'so what?' again until you reach an implication for the decision. Look across the findings for the through-line: do they converge on one conclusion, or do they trade off against each other, and if so which side wins and why? Lead with that single synthesized message, then show how the individual findings support it, rather than presenting the findings and hoping the listener assembles the meaning. A useful test: if you removed the findings list and kept only your top line, would it still tell the listener what to do? If not, you have summarized, not synthesized.
Common mistakes
The dominant error is the list-in-disguise: stringing findings together with 'and' ('the market is big, and costs are high, and competition is fierce') without ever saying what that combination implies. Another is stopping at the first-order finding instead of pushing to the decision-relevant implication. People also synthesize toward a conclusion the evidence does not actually support, forcing a tidy message over an honest one. And they hedge - presenting every finding as equally weighted - which is really an inability to say which ones drive the answer.
Example
At the end of a case on whether a hospital should add a new surgical wing, a summary sounds like: 'Demand for these procedures is growing, the wing would cost 40 million, and two competitors are also expanding.' All true, all inert. A synthesis sounds like: 'They should not build the wing now - because although demand is growing, two competitors expanding at once will likely leave the region with excess capacity, and at 40 million the wing only pays off at utilization levels that oversupply makes unrealistic. The findings do not just coexist; combined, competitor expansion turns growing demand into a capacity glut, which is the fact that decides it.' The synthesis makes the findings mean something.
Practice it
Practice in the closing and mid-case update moments of cases by asking 'so what?' repeatedly until you reach a decision-relevant message, then leading with that single conclusion and using findings as support. The skill to build is finding the through-line across findings - convergence or trade-off - rather than reciting them in parallel.