i used to dump a wall of facts at the end of cases and watch interviewers’ eyes glaze. over time i learned to compress the conclusion into a tight narrative: situation (1 sentence), key insight (1 sentence with the metric that moved), recommendation (1 sentence), and two short next steps. weaving the data point into the insight — not tacking it on — makes the whole thing believable. telling it like an exec means fewer words, clearer trade-offs, and a credible path to action. what’s one line you always include in your final synthesis?
most people think storytelling means flowery language. it doesn’t. keep it brutal: one-line problem, one-line insight with the metric, one-line ask. i’ve heard syntheses that read like white papers and the interviewer sighed. your job is to make the recommendation immediate and actionable, not poetic. if you can’t say it in three lines, you haven’t processed the case.
here’s what lands: ‘we believe X is the root cause because metric Y moved by Z%; recommend A implemented by Q timeframe.’ that format has corners and keeps you honest. save the nuance for follow-ups.
i always try: situation, insight with number, one clear rec. keeps me concise and less nervous.
i add a ‘next step: quick test’ line to show i’m pragmatic. seems to help!
Executive synthesis is a discipline. I coach candidates to structure it as: context in one clause, the critical finding quantified in one sentence, the recommendation with implied impact in one sentence, and a single near-term action to de-risk the recommendation. For example: ‘market share fell 4pp in Q4 (context) because price elasticity rose 25% (finding). we should test a targeted price promotion expected to restore 2pp margin within 3 months (recommendation); run a 4-week pilot in top three regions to validate (next step).’ This communicates insight and a pragmatic path forward.
i used to end answers with a list of ‘possible reasons’ until a mentor told me to ‘tell one story.’ after that, i started ending with a single quantified insight and a tiny next step. once, an interviewer asked me to repeat my last line — i did, cleaner the second time — and that clarity turned the rest of the discussion. it’s amazing how repeating the same one-liner cements credibility.
in a recent mock i opened my close with ‘we should prioritize price because margin fell 6% and drove 80% of the profit decline’ and then gave one pilot step. that single sentence changed the interviewer’s tone from skeptical to practical. story + data = trust.
Quantify the primary claim in your synthesis. Frame it as: baseline impact, observed delta, causal link, expected outcome of your recommendation. For instance: ‘current margin at 12% vs. target 18%; price erosion explains ~70% of the gap; a targeted 5% price recovery should increase profit by ~X%; recommend a regionally targeted price test.’ This communicates the logic chain and the magnitude of expected benefit, which interviewers appreciate more than abstract recommendations.
Follow-up habit: state a confidence level for your recommendation (low/medium/high) based on available data, and a single metric you’ll monitor during the pilot. that signals that your conclusion is testable and grounded in measurable outcomes.