Nobody wants your analysis. Watch a stakeholder open a deck of fourteen slides and jump straight to the one that says what to do — the other thirteen were method, and method is not what they came for. They want to make a decision, and the analysis is a means to it. Take that seriously and everything about how you communicate changes — structure, units, length, even which work you do in the first place.
Answer first, evidence second
Technical training teaches you to present the way you worked: data, methods, caveats, then conclusion. Decision-makers need the opposite order. Lead with the answer and the recommended action; support it afterwards.
Before: “We analysed 14 months of transaction data using a gradient boosting classifier with grouped cross-validation, achieving an AUC of 0.86…”
After: “We can cut manual review workload roughly in half without missing more fraud than today. To ship it, we need X. Here’s the evidence.”
If the audience remembers one sentence, you get to choose which. Choose it deliberately and say it first — everything after that sentence is for the skeptics, and it should exist, in the appendix.
Translate every metric into their units
AUC, F1, and log loss are your internal instruments, not communication devices. Stakeholders own headcounts, euros, and hours — convert into those:
- Not “precision is 0.81 at our operating point” but “of every five accounts we flag, four are real fraud; one wastes about ten minutes of review time.”
- Not “the model improves RMSE by 12%” but “forecast error drops enough to cut safety stock by ~€40k per warehouse.”
- Not “recall is 0.65” but “we catch two of every three fraudulent accounts; the third slips through — here’s what that costs today.”
This translation is real analytical work — you must find out what a false positive costs, which means talking to the review team. That conversation routinely changes the model’s threshold, and occasionally the whole project. It’s not a presentation chore; it’s requirements discovery in disguise.
Say uncertainty like a human
“The 95% confidence interval spans 1.2 to 8.4 percentage points” is accurate and useless to most rooms. Try: “Our best estimate is a 5-point lift. It could plausibly be as low as 1 or as high as 8. Even the low end pays for the work, which is why we recommend shipping.” Ranges, scenarios, and what-would-change- the-conclusion statements carry uncertainty without requiring a statistics course. Never delete uncertainty to seem confident — decision-makers who get burned once by your overconfidence discount everything you present after.
And when results are inconclusive or negative, say so plainly and fast. “The test didn’t move the metric; we recommend not rolling out; here’s what we’d try next” builds more credibility than any amount of silver-lining excavation. Your long-term asset is that people believe your numbers.
Match the artifact to the audience
One analysis, several renderings: a three-sentence summary with the decision (for the executive), one page with headline numbers in business units plus key charts (for the working meeting), and the full notebook (for the reviewer). The mistake is sending artifact three to audience one — it reads as “I did lots of work”, and lands as homework.
A structure that survives contact with real meetings: Decision needed → Recommendation → What we found (three bullets, business units) → What it costs / risks → What would change our mind. If the meeting gets cut to five minutes, the first two lines carry everything.
It’s a skill, so practice it
Rewriting a finding for a non-technical reader is a rep, like any other rep. Show drafts to non-analysts and watch where their eyes stall. The question “how would you have said this to your exec?” teaches more than most courses, and the only way to get the answer is to ask someone who was in the room.
The work isn’t finished when the notebook runs. It’s finished when someone makes a better decision than they would have without you — and can repeat your reasoning to their boss in their own words.