The first time I presented a campaign performance report to senior management, I used seventeen slides. The data was clean, the charts were colour-coded, the commentary was thorough.
The MD looked at two of them and asked: ‘So are we profitable on this or not?’
That question — that specific, blunt question — changed how I present analytics.
The problem with data-first presentations
Most analyst-built reports make the same mistake: they lead with the data and hope the audience will draw the right conclusion. Open rate: 24.3%. Click-through: 3.1%. Unsubscribe rate: 0.8%. Revenue attributed: £X. The analyst has done the work. The numbers are accurate. The presentation is useless.
Senior stakeholders don’t want data. They want decisions. They want to know what happened, whether it was good or bad, why, and what you’re doing about it. Everything else is noise.
The problem isn’t the data. It’s the order.
Decision first, then the number
The framework I use now, for any analytics presentation to a senior audience, runs like this:
- Lead with the decision. What do you need the person in the room to agree to, approve, or understand by the end? State it in the first thirty seconds. “I want to show you why we should increase investment in email automation and reduce spend on paid retargeting.”
- Show one number. Not seventeen metrics. Not a dashboard. One number that makes the case. “Last quarter, email-acquired customers had a 40% higher average order value than paid social.”
- Explain the so what. What does that number mean for the business? What does it cost to ignore it? “If we continue splitting budget evenly, we’re underinvesting in our highest-value acquisition channel.”
- State what you’re doing about it. Come with a recommendation, not a question. “I’d like to shift 20% of the paid social budget to email list growth activity from Q2. Here’s what I’d need to run it.”
The data sits behind this structure — ready to answer questions, not lead the conversation. Senior stakeholders ask better questions when you don’t drown them in metrics first.
What to cut
When I review analytics presentations before they go to leadership, there are a few things I cut almost every time.
Volume metrics without context. “We sent 340,000 emails this month” means nothing without a comparison. Last month? Last year? Industry average? If you can’t tell the audience whether that number is good or bad, take it out.
Metrics the audience can’t act on. Bounce rate, time on page, scroll depth — these are optimisation inputs, not boardroom metrics. If changing that number doesn’t directly affect revenue or cost, it doesn’t belong in a senior presentation. It belongs in an analyst’s working document.
Methodology explanation. How you built the attribution model is not a C-suite conversation. If they ask, answer. Don’t pre-empt it with four slides on data sources and exclusion logic.
The visual question
Charts are often the wrong choice for senior presentations. A single, well-formed sentence communicates faster and more precisely than most visualisations. ‘Email revenue per send is up 18% year-on-year’ beats a line chart — unless the line chart tells a story the sentence can’t (a spike, a cliff, a trend reversal).
When you do use visuals, use them to answer a question, not to fill slides. Ask yourself: if I removed this chart, what would the audience not understand? If the answer is ‘not much’, remove it.
What this looks like in practice
For a quarterly campaign performance review, my current structure is one page — literally one page:
- The headline: one sentence on whether performance is up or down vs last quarter and vs target.
- The why: two to three sentences explaining the main driver.
- The so what: one sentence on the commercial impact.
- The action: what we’re changing or testing next, and what approval or budget we need.
The backup slides exist — a full data appendix I can flip to if someone asks a specific question. But the default is one page. Meetings that used to run forty minutes on performance review are now ten, because the question and the answer are in the same place.
Senior stakeholders don’t distrust data. They distrust presentations that make them do the analytical work themselves. Do the work for them — translate the numbers into a decision — and they’ll trust you for it.
