How to Present Data to Stakeholders

The dashboard is built and the numbers are right. Now someone has to look at it, understand it, and decide something, which is a different skill from the one that built it.

The most common way an analyst loses the room is opening with methodology. The stakeholder wants the answer. How you got there only becomes interesting once they doubt it.

---

Start with the Decision, Not the Data

Open with "here's the dashboard I built" and walk the charts top to bottom, and you have given the room a tour when they came for an answer.

The question I ask before presenting is the one worth asking before building: what will you do differently after seeing this? If nobody in the meeting can answer it, you are presenting a report, and a report can be sent instead of presented.

A weak opening sounds like this: "This dashboard shows our sales performance across five regions with monthly trending and quarterly segmentation."

A strong one sounds like this: "We're 12% behind Q1 target. The gap is concentrated in two regions. I have a recommendation for where to focus the team in April."

The dashboard is your evidence. Lead with the finding and bring the charts up behind it.

---

Know Your Audience's Decision Style

Three kinds of stakeholder turn up to these meetings, and each one wants a different length of answer.

The Glancer (C-suite, board members)

• Wants: the headline number, the direction it moved, and whether to worry
• Format: one KPI, a verdict on it, one chart behind the verdict
• Time budget: 2-3 minutes per topic

Lead with the answer and stop. The supporting material you prepared stays in your pocket until somebody asks for it, and most of the time nobody does.

The Questioner (VPs, department heads)

• Wants: the reason behind the number
• Format: the insight, then the breakdown that supports it. Expect 3-5 questions
• Time budget: 5-10 minutes per topic

The Deep Diver (fellow analysts, data-literate managers)

• Wants: methodology, data sources, edge cases, drill-downs
• Format: the summary, then an offer to go deeper. Send the dashboard link and let them explore on their own time
• Time budget: 15-20 minutes for a full walkthrough

Decide which one you are walking into before you build the material. Aim at the Deep Diver when a Glancer is in the chair and you lose the room inside two minutes.

---

The 3-Slide Framework

Three sections carry a formal presentation, whether you are clicking through slides, a live dashboard, or a screen share.

Slide 1: The Headline (What happened?)

• One sentence: "Revenue grew 8% MoM, driven by new enterprise deals"
• The key KPI, large and centred
• The direction it moved, marked green or red

Slide 2: The Context (Why did it happen?)

• Two or three charts that carry the explanation
• "New enterprise deals closed in Week 3 accounted for 60% of the increase"
• Cause, not restatement. A chart that shows the number went up repeats slide 1

Slide 3: The Recommendation (What should we do?)

• What you think the room should do next
• "Put April's outbound on enterprise. Pause SMB campaigns until Q3."
• The uncertainty, where there is any: "this assumes enterprise pipeline holds at current levels"

A fourth section means you are presenting two things. Split the meeting, or send the second one as a follow-up.

---

Use the Dashboard as a Supporting Actor

A live dashboard tempts you into demoing it. Resist that.

1. Open the dashboard to the view you need before anyone joins
2. Point at the specific visual that carries your claim rather than letting the room hunt for it
3. Narrate the chart: "this is pipeline by stage, and Stage 3 is where it drops"
4. Touch the filters when a question asks you to, and not before

Your spoken account is the presentation. The screen holds the evidence for it.

---

Anticipate the Top 3 Questions

Write down the three questions you will be asked, then answer them before anyone gets to.

1. "How does this compare to last period?" Have the comparison on the page. A number without one says where you are without saying whether that is good, and the room has to ask
2. "What's driving the change?" Have the breakdown prepared, by region, product and segment
3. "What should we do about it?" Have a recommendation, tentative if it has to be

Cover those three inside the presentation and the Q&A gets short.

You can also plant the first question. Close a section with "the natural question is where that growth came from, so let me show you." The room stays with a conversation longer than it stays with a lecture.

---

Avoid These Presentation Anti-Patterns

The Data Dump

Every chart on the dashboard, one after another, all weighted the same. The room checks out around chart four. Show the two or three visuals that carry your claim and leave the rest for anyone who wants to click through later.

The Methodology Introduction

"The data comes from Salesforce, joined with HubSpot, aggregated weekly, filtered to active accounts." The plumbing matters once somebody doubts the number, and not before. Park it in an appendix or an FAQ doc you can jump to.

The Apologetic Analyst

"The data might not be complete." "This is still a draft." "I'm not sure about this number." State the caveat and skip the apology: "this excludes APAC, which arrives two days late, so read the total as slightly low." A caveat with a size attached is information. An apology invites the room to discount everything else you say.

The Scroll of Death

A fifteen-page dashboard, scrolled end to end while the room waits for the part that concerns them. Bookmark the sections you need and jump between them.

The Decoration Tour

"I used blue for revenue and green for profit, and the gradient shows intensity." Explain a visual choice when it changes how someone reads the chart. Otherwise you are spending the room's attention on the part of the work that does the least: a dashboard has to answer its main question within about three seconds of loading, and the palette is not what moves that number. Layout does.

---

Remote Presentations: Extra Rules

Over Zoom or Teams you have already lost body language and most of the attention in the room, so the rules tighten.

• Share the tab, not the whole screen. Nobody needs to see your Slack notifications
• Use your cursor as a pointer. Circle the relevant data point while you talk about it, the remote version of walking to a whiteboard
• Pause after each finding. "Revenue is up 8%." Then stop for a second and let people catch up
• Ask a direct question every couple of minutes: "does this match what you're seeing on the ground?" The answer tells you whether anyone is still there
• Send the dashboard link in chat so people can follow along on their own screen

---

After the Meeting: The Follow-Up

Send a note within a day, carrying five things:

1. The headline insight, in one sentence
2. The recommendation you made
3. The decision the room reached, if it reached one
4. The dashboard link, so stakeholders can explore on their own
5. The questions still open

That note is the version of the meeting people quote three weeks later, and it is the only version that reaches whoever missed it.

---

The Wireframe Connection

Lay the dashboard out before you build it and you have most of the presentation already, because the layout runs in the same order the story does:

• The KPI row is your headline
• The trend chart is your context, showing how you got here
• The breakdown chart is your explanation, showing where the gap sits
• The filter panel is your Q&A safety net, for "can you filter to my region?"

The hard part of presenting is deciding what matters and where it goes. That decision has a cheaper place to happen than a live meeting, and the order is what does the work rather than the tool you draw it in.

That order is the inverted pyramid layout pattern: headline, then context, then detail. It is also why executive dashboards hold up when they are built to answer one question at a glance.

Before the next stakeholder meeting, sketch the layout in datawirefra.me (opens in a new tab) and read it top to bottom as a script. If it does not read as one, the meeting will not either.