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.
A deck that lists everything is a filing cabinet
Picture a deck with fourteen slides, every metric in its own neat box, color-coded. When it ends, someone asks, "So what are we supposed to do with this?" The presenter handed the room a filing cabinet and asked them to do the detective work. That has nothing to do with the data being wrong.
Your audience does not remember a list of 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, but 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 will not. They are tired, they are checking the time, and they have three meetings after yours. When you make people do the synthesis, they reach different conclusions from each other, and they reach them slowly. Decisions stall.
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 does not move a decision forward, it did not do its job, no matter how clean the dashboard looked.
Every movie works this way, and so can your quarterly review
This is the setup-conflict-resolution shape, and it is the backbone of the data storytelling techniques I coach inside Story-Driven Data™. It is the same arc every film uses, scaled down to fit a boardroom.
In all dramas, written literature, movies, there needs to be some conflict. I went to work, came home, ate and went to bed. That would be a terrible movie.
Something has to happen. There needs to be an issue or a problem. Some people call it conflict, but I feel pain gets to it a little faster.
Setup, conflict, resolution in a boardroom
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 is it. You are planting the expectation on purpose, because a story needs a baseline before it can have a surprise. Skip it and your big finding lands with no contrast, like a punchline with no joke in front of it.
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 is tension, and 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? Say it out loud rather than making people infer it.
Resolution
End with a recommendation, not a conclusion. "Sales are down" is a conclusion. "Sales are down, and here is the one thing I would do about it this week" is a recommendation. One leaves the room holding a problem. The other hands them a next step.
The resolution can be small. It can even be "we need thirty more days of data before we commit, and I would hold the budget flat until then." That still counts. You have told the room what you think should happen next.
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 have ended on a conclusion. Rewrite it as a recommendation, even a cautious one.
Why a summary slide is the wrong ending
Many people end on a slide called Summary that lists what the data showed. Then they sit down, and leadership is left to argue about what it all means. A conclusion describes the past. A recommendation points at the future. A presentation that ends in description quietly tells the room, "I did the looking, you do the deciding." You are the one who lived in the data, and you have a view. Share it.
My rule: 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.
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 have a filing cabinet, and a ten-minute rewrite will turn it into something the room remembers.
If you want a faster path, that is what I do with executives every week. Get a quick quote and we will 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.