The data storytelling techniques that make a presentation stick all rest on one shape: setup, conflict, resolution. Set the expectation, show where reality broke from it, then end with a recommended action. Do that and people remember the point instead of the pie charts.
I watched a product lead present quarterly numbers to her leadership team last spring. Fourteen slides, every metric in its own neat box, color-coded. When she finished, the room went quiet, and then someone asked, "So what are we supposed to do with this?" She had handed them a filing cabinet and asked them to do the detective work. That's the most common mistake I see, and it has nothing to do with the data being wrong.
Why this matters (and what most executives get wrong)
Here's what I tell clients: your audience does not remember numbers. They remember tension and its release. A deck that lists revenue, then churn, then headcount, then pipeline is technically complete and emotionally dead. Each slide is true. None of them adds up to a story, because nobody told the room why this number sits next to that one.
The filing-cabinet deck assumes the audience will assemble meaning on their own. They won't. They're tired, they're checking the time, and they have three meetings after yours. When you make people do the synthesis, two things happen. They reach different conclusions from each other, and they reach them slowly. Decisions stall.
There's research behind why structure beats volume here. Harvard Business Review's work on the decision-driven organization makes the case that the unit that matters in a company is the decision, not the data point. If your presentation doesn't move a decision forward, it didn't do its job, no matter how clean the dashboard looked.
This is the part nobody wants to hear. Most of the effort in a data deck goes into being thorough. Almost none goes into being followed. Thoroughness is table stakes. The shape is what carries the room.
The 3-step structure
This is the setup-conflict-resolution shape, and it's the backbone of the data storytelling techniques I coach inside Story-Driven Data™. It's the same arc every film uses, scaled down to fit a boardroom. You can teach it to yourself in an afternoon. Here are the three parts.
Setup
Ten to thirty seconds. Tell the room where we are and what we expected. "Coming into Q2, we forecast flat conversion and a small lift in average order value." That's it. You're planting the expectation on purpose, because a story needs a baseline before it can have a surprise. Skip this and your big finding lands with no contrast, like a punchline with no joke in front of it.
Most presenters rush past the setup or skip it entirely. They open on the chart. But the chart means nothing until the room knows what they were supposed to see.
Conflict
This is where reality diverged from the plan, or where an opportunity nobody saw is hiding in the numbers. I call it the eyebrow moment. "Conversion held flat, like we expected. But average order value didn't lift two percent. It dropped nine." Now there's tension. Now the room is awake.
The conflict is also where you make the stakes plain. What does this number cost us if we ignore it? What does it unlock if we move? Don't make people infer the stakes. Say them out loud. The eyebrow moment is the single most underused beat in business presenting, and it's the one your audience will actually remember on the drive home.
Resolution
End with a recommendation, not a conclusion. There's a real difference. "Sales are down" is a conclusion. "Sales are down, and here's the one thing I'd do about it this week" is a recommendation. One leaves the room holding a problem. The other hands them a next step.
The resolution doesn't have to be a grand strategy. It can be small. It can even be "we need thirty more days of data before we commit, and I'd hold the budget flat until then." That still counts. You've told the room what you think should happen next, and that's the whole job of the final beat.
"Sales are down" is a conclusion. "Sales are down, and here's what we do" is a recommendation. End on the recommendation, every time.
The mistake most executives make
They end on a conclusion and call it a day. The last slide says "Summary" and lists what the data showed. Then they sit down, and leadership is left to argue about what it all means. I've watched smart, senior people torpedo their own credibility this way, not because their analysis was weak, but because they stopped one beat too early.
A conclusion describes the past. A recommendation points at the future. Executives are paid to decide, and a presentation that ends in description quietly tells the room, "I did the looking, you do the deciding." That's backwards. You're the one who lived in the data. You have a view. Share it.
Here's my rule, and I'll die on this hill: every data presentation ends with a recommended action. Even when the honest answer is "don't act yet." "I recommend we wait for more data" is a recommendation. "Here's the data" is not. The difference is whether you put a stake in the ground or hand the room a shrug.
Before your next deck goes out, read your final slide out loud. If it describes what happened instead of telling the room what to do next, you've ended on a conclusion. Rewrite it as a recommendation, even a cautious one.
Case study: the St. Louis advisory firm whose clients stopped zoning out
A few years ago I worked with a financial advisory firm in St. Louis. A lot of their staff were on the younger side and did not yet have years of practice explaining to clients why they should act on a recommendation. They ran quarterly reviews with most of their clients, and the pattern was always the same. The client would say okay, okay, okay, visibly zone out, and just wait for the meeting to end.
We installed the setup-conflict-resolution shape. Set the expectation, name what changed and what is at stake, then land on a clear recommendation. When the advisors reported back, the difference was obvious. Clients were engaged. They asked real questions. And together, advisor and client actually decided on the right way forward, which is the entire point of the meeting.
Just like any good piece of Hollywood storytelling, the conflict connected on an emotional level and the resolution drove the point home. The firm did so well with it that they brought me back to work with their senior leaders, who figured they could use a few new frameworks too.
Filing cabinet versus movie: the difference at a glance
| The filing cabinet | The movie |
|---|---|
| Organized by category (revenue, then churn, then headcount) | Organized by tension (expectation, then surprise, then action) |
| Every metric gets equal weight | One finding gets the spotlight |
| Audience assembles the meaning | Presenter delivers the meaning |
| Ends with a summary slide | Ends with a recommended action |
| Room leaves with questions | Room leaves with a decision |
The filing cabinet isn't lazy. It's usually the opposite, the product of someone who worked hard to include everything. But completeness and clarity are not the same thing, and a deck that respects the audience's attention picks one story and tells it well.
What to do next
Take your next data deck and run it through three questions. Did I set the expectation before I showed the surprise? Did I name the conflict and the stakes out loud? Did I end on a recommended action instead of a summary? If any answer is no, you've got a filing cabinet, and a ten-minute rewrite will turn it into something the room remembers.
If you want a faster path, that's what I do with executives every week. Get a quick quote and we'll work on your actual deck, not a generic template. And if you want the broader foundation first, start with data storytelling and how it changes the way leadership hears your numbers.