---
title: "How to Present Data to Executives and Teams"
description: "How to present data to executives: state the insight in one sentence, reframe it for each audience and medium, and never bend the numbers to fit the ask."
canonical_url: "https://builderscamp.com/guides/other/how-to-present-data-to-executives"
date_published: "2026-09-27"
date_modified: "2026-09-27"
author: "Andre Albuquerque"
publisher: "Builders Camp"
guide_class: "other"
---

# How to Present Data to Executives: One Insight, Three Audiences

**TL;DR:** To present data to executives, lead with the insight in one sentence, state the decision you need, and show one chart whose title says the finding. Keep the numbers identical for every audience and change only the framing and the medium: the CEO gets the business consequence, the product team gets the friction, and nobody gets a version that hides the part that cuts against you.

Executives read a data presentation for one thing: what it means for a decision they own. Nancy Duarte's advice in her guide to [presenting to senior executives](https://www.duarte.com/blog/how-to-effectively-present-to-senior-executives/) is to "Lead with your findings and your recommendation" and keep the rest of the detail in an appendix you pull up only when asked. Her 10% rule sets the ratio: "If your appendix is 50 slides, create 5 summary slides, and so on."

The same insight still has to reach people who are not executives. A PM's week often includes the leadership review, a thread with engineering and a sync with marketing, all about the same number. This guide takes one insight from a fictional product and rewrites it for three audiences and three media, without changing a single figure. If what you need is a yes or no on a specific proposal, the companion guide on [how to pitch a decision to executives](https://builderscamp.com/guides/other/how-to-pitch-a-decision-to-executives) covers that structure; this page is about presenting the data and metrics themselves.

## What is the insight, before any audience?

Start by writing the insight once, in plain words, before you decide who hears it. Cole Nussbaumer Knaflic of *storytelling with data* calls this the Big Idea and, in her post [what's the Big Idea?](https://www.storytellingwithdata.com/blog/2014/02/whats-big-idea), explains that it boils down the so-what of your communication "even further: to a single sentence."

Rotaly is a fictional shift-scheduling app. Its PM has found this (all numbers illustrative):

- Trial-to-paid conversion fell from 14 to 11 percent over the last 8 weeks.
- Signups rose 20 percent over the same period, after a new campaign.
- Almost all of the drop sits in trials where the team tried to connect an Outlook calendar. Since a login change 8 weeks ago, that step fails for about 1 in 3 Outlook users, against 1 in 25 for Google Calendar users.
- Conversion for Google Calendar users also dipped, by half a point, which the calendar bug does not explain.

The Big Idea: **Trial conversion fell 3 points because Outlook users cannot connect their calendar; fixing that step is worth more than any change to the campaign.**

That sentence is the anchor. Every version that follows says the same thing with a different emphasis.

## How do you reframe one insight for three audiences?

Each audience owns a different decision, so each needs a different first sentence. The numbers underneath do not move.

| Audience | What they own | What they need first | Rotaly's opening line |
|---|---|---|---|
| CEO or leadership team | Revenue, priorities, headcount | The business consequence and the ask | "We are losing about 30 paying accounts a month to a calendar bug; I need two engineers for two weeks to fix it." |
| Engineering and product peers | The flow and the fix | Where it breaks, how sure you are | "The Outlook connect step fails 1 in 3 times since the login change; here is the funnel and three session recordings." |
| Marketing | Traffic and spend | Whether their numbers are the cause | "The campaign's signups are fine; they convert badly because many use Outlook, and the product is failing them." |

The CEO line converts the rate into accounts, because a 3-point conversion drop is abstract until someone multiplies it by volume. At Rotaly's roughly 1,000 trials a month, 3 points is about 30 accounts. Say how you got the number, so nobody has to trust it blind.

The engineering line leads with location and evidence, because that audience will check your work and act on the detail. The marketing line answers the question they are already worried about: whether the drop is their fault. Getting that answer first keeps the conversation from turning into a defence of the campaign.

## What must stay the same in every version?

The objective of a presentation decides what you emphasise. It must never decide what the data says. This is the line between framing and spin, and it is easy to cross without noticing when you want a particular outcome.

Four things stay fixed across all three Rotaly versions:

- **The same time window.** If the leadership deck shows 8 weeks, the engineering thread does not show the 3 worst weeks.
- **The same baseline and axis.** A conversion chart starting at 10 percent makes a 3-point drop look like a collapse. Start the axis at zero, or say plainly that it does not.
- **The same denominator.** "Conversion" means trials that became paid accounts, in every version.
- **The part that cuts against you.** The half-point dip for Google users is inconvenient, because it suggests the bug is not the whole story. It goes in every version, with the note that it is being looked into.

Leaving out the half-point dip would make the ask cleaner. It would also mean that when someone finds it later, every other number in the deck loses credibility. For the bias that makes this so tempting, see [confirmation bias in data](https://builderscamp.com/guides/glossary/confirmation-bias-data).

## How do you present the same data on a slide, in Slack and live?

The medium changes how much detail fits and what the reader does with it. Rotaly's insight in three formats:

**The executive slide.** One chart, two lines: conversion for Outlook trials and for Google trials, over 8 weeks, with the login change marked. The chart title is the insight, not the metric: "Conversion fell 3 points, almost all from Outlook users who cannot connect their calendar." The ask sits on the same slide. Everything else, including the session recordings and the campaign breakdown, goes in an appendix. Knaflic's advice applies slide by slide: "if your communication medium is slides, each slide should have a clear Big Idea."

**The Slack message.** People skim written updates hard. In [Jakob Nielsen's analysis](https://www.nngroup.com/articles/how-little-do-users-read/) of real browsing data, users had time to read at most 28 percent of the words on an average web page, and 20 percent was more likely. That study measured web pages in 2008, not chat messages, so treat it as a direction rather than a rule. What it still shows is that the first line carries almost all the weight:

> Trial conversion is down from 14% to 11% in 8 weeks, and almost all of it is Outlook users failing to connect their calendar (fails 1 in 3 since the login change).
> Proposal: 2 engineers for 2 weeks on the connect step. Est. ~30 paying accounts/month recovered.
> Google users also dipped 0.5 pts; not explained yet, looking into it.
> Funnel and recordings: [link]

**The live walkthrough.** In a room, you can build the story in sequence. Show the funnel from signup to paid, step by step, and stop at the calendar step for Outlook users. Let the drop sit on screen before you explain it. Then show the before and after around the login change, then the ask. The pause is the point: a live audience remembers the moment they saw the drop more than any number you read out.

## How do you write a chart title that states the insight?

Write the title last, after you know the Big Idea, and make it a sentence with a verb. Compare:

| Descriptive title | Insight title |
|---|---|
| Trial conversion by week | Trial conversion fell 3 points in 8 weeks |
| Calendar connection success rate by provider | Outlook connections fail 8 times as often as Google since the login change |
| Signups by channel | The campaign brought in more Outlook users, which is why its conversion looks weak |

An insight title does two jobs. It tells a skimming executive what to see before they read the axis, and it commits you to a claim the chart must support. If you cannot write a true insight title for a chart, the chart probably does not belong in the main deck.

## When is this approach the wrong one?

The strongest objection is that leading with a single insight flattens uncertainty. Some analyses do not have one answer: the data is mixed, the cause is unclear, and forcing a Big Idea would overstate what you know. In that case the honest one-sentence version is about the uncertainty itself ("Conversion fell 3 points and we have two candidate causes; here is what would tell them apart by Friday"), and the ask is for time or data, not a decision.

The other limit is the audience that wants the method first. Some data-literate executives and most analyst peers will not accept a conclusion until they have seen how it was reached. For them, keep the insight up front but move the method from the appendix into the main flow.

## Where can you practise turning data into a story?

For the definition and a framework for building a data story, see [what is data storytelling](https://builderscamp.com/guides/glossary/data-storytelling); for drafting with an assistant, see [AI for executive summaries](https://builderscamp.com/guides/tools/ai-for-executive-summaries) and [AI for product presentations](https://builderscamp.com/guides/tools/ai-for-product-presentations). If the number you are presenting is a funnel step, the [product funnel](https://builderscamp.com/guides/glossary/product-funnel) glossary entry covers how to define each stage consistently.

[Turning Data Into Storytelling](https://builderscamp.com/bootcamps/turning-data-into-storytelling) is a one-week bootcamp with 2 live sessions and 9 microlessons, directed by Andre Albuquerque and part of the Product Leadership Track and the Data & Analytics Specialist Track. Its published topics include connecting metrics to user behaviour and business outcomes, narrative structures for insights, chart selection and visual clarity, executive-ready summaries, handling objections and uncertainty, and turning insight into decisions and owners. Its practical challenge gives you Netflix's quarterly data and asks you to build a narrative for management, investors, markets and employees, choosing the right medium and format for each.

Builders Camp runs live and self-paced bootcamps in product management and AI product building. See the Turning Data Into Storytelling bootcamp for dates and the full syllabus.

## Frequently asked questions

### How do you present data to executives?

Open with the insight in one sentence and the decision you need, show one chart whose title states that insight, and keep the supporting analysis in an appendix for questions. Executives want the implication for the business first and the method only if they ask.

### How should a chart title look in an executive presentation?

It should state the finding, not the metric. 'Trial conversion by week' makes the executive work out the point; 'Trial conversion fell 3 points, all of it from Outlook users' tells them before they read the axis.

### How is presenting data to a CEO different from presenting it to a product team?

A CEO needs the business consequence, usually revenue, risk or a deadline, and the decision being asked for. A product team needs where in the flow the problem happens and how confident you are, because they will act on the detail.

### How many slides should an executive data presentation have?

As few as the decision needs. Nancy Duarte's 10% rule is a useful ceiling: if your appendix is 50 slides, create 5 summary slides, and let questions pull the rest.

### Is it acceptable to frame data differently for different audiences?

Yes, as long as only the emphasis changes. The numbers, the time window, the baseline and the uncomfortable parts stay the same for everyone; if a frame only works by hiding something, it is spin.

### How do you present data in a Slack message to an executive?

Put the insight and the ask in the first line, the one number that proves it in the second, and a link to the detail at the end. Assume the first line is the only one read.

### What if the data does not support what you want to ask for?

Present what the data says and change the ask. An executive who later finds the part you left out will discount every chart you show them after that.

## Sources

- [Nancy Duarte, Duarte: How to effectively present to senior executives](https://www.duarte.com/blog/how-to-effectively-present-to-senior-executives/)
- [Cole Nussbaumer Knaflic, storytelling with data: what's the Big Idea?](https://www.storytellingwithdata.com/blog/2014/02/whats-big-idea)
- [Jakob Nielsen, Nielsen Norman Group: How Little Do Users Read? (2008)](https://www.nngroup.com/articles/how-little-do-users-read/)

## How this guide was made

Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.