Before you build a single slide, ask one question: what decision does this data need to support? Not what the data shows, not what is interesting in it, but what choice it is supposed to help someone make. It is the most useful of all the data presentation tips I teach, because it changes what you keep, what you cut, and how you stand in the room.
What decision should the room make?
Most data presentations fail before anyone opens PowerPoint. They fail at the goal. People sit down to build and silently set the target as "show what the data says." That feels responsible, and it is also the trap. When showing is the goal, every chart earns a place. Nothing gets cut, because everything is technically true, so you walk in with thirty slides and walk out with no decision.
Your audience did not block ninety minutes to admire your spreadsheet. They came to decide something, or to feel confident that someone has. The numbers are evidence, and evidence is in service of a verdict. If you skip naming the verdict, you hand the room a pile of evidence and ask them to assemble the case themselves while you talk.
This is the front end of data storytelling, and it is part of the broader Story-Driven Data™ approach I use with executives. You do not need the whole system to start. You need four moves, in order, before you touch a slide.
Four moves to make before you build
Write the decision in one sentence
Finish this sentence on paper: "After this presentation, the room should decide whether to ____." Fund the plant. Kill the product. Move the launch. If you cannot finish the sentence, you are not ready to build. You are ready to go ask whoever called the meeting what they need to walk out knowing.
Find the one number that moves that decision
Every decision turns on one figure more than any other: the number that, if it moved, would change the answer. For a new plant it might be projected capacity utilization rather than the twelve other metrics on the dashboard. Find that number and build the presentation to deliver it cleanly.
Put the recommendation first
When I work with groups on data storytelling, they talk and talk and make their recommendation all the way at the end. The other people are dizzy waiting. Flip it over.
Flip it over and have the recommendation right at the beginning.
One group did that with their top director, and he said they did not even need to say any more, it sounded great. Directors tend to want the answer, and the audience can always ask for the detail. Recommendation first, reasons after.
Write a "which means" line under every chart
For any chart that survives, write one sentence underneath: "which means." Sales dipped in the Northeast, which means we are losing accounts we assumed were locked. The chart is the what. The "which means" is the so-what, and the so-what is what your audience can use. A chart with no such line is decoration. Cut it or finish it.
Give the big numbers some context
I see it in training rooms all the time: the data dump. We give everybody all these numbers but no context, and a listener's brain starts to shut off at a certain point, even when they care about the topic. This is where an analogy or a story comes in. Pause on a big number and put it in perspective. In one clip I show, a guest says an annual trade figure is slightly more than the GDP of a major country, and suddenly a huge number is graspable.
Data on its own is just a data dump usually. We need a story around it for us to say, I get that, now I really understand.
A simple way to slide into a story is the phrase "for example." Stories are memorable, they are visual, and they give evidence. Pick one that carries the data rather than decorating it.
Build a case, not a report
A report lists what happened. A case argues toward a decision. Structure it like a story arc: the issue or pain early, the tension, then the resolution. In all dramas, something has to happen. If you went to work, came home, ate and went to bed, that would be a terrible movie. Open with the problem the decision solves, and balance it with a concrete positive so the audience does not tune out. Playing to the pain is a good opener, and the positive makes it believable.
Try it on your next deck
Open the file, go to slide one, and write the decision sentence at the top before you change anything else. Then delete every slide that does not help the room make that one choice. You will cut slides, and the cutting will feel good, because for the first time you have a rule for what stays.
If you want help turning your team's data into decisions the room actually makes, get a quick quote and we will talk about what your presentations need. To go deeper on the method behind this, read what is data storytelling and see how the pieces fit together.
One question, asked before you build. It is the cheapest upgrade you will ever make to a data presentation.