A few years ago, I delivered what I genuinely thought was one of my best presentations. The slides were clean. My timing was solid. I had rehearsed enough that I moved through the content without any hesitation. At the end, there was a brief round of applause and several people came up to say kind things.

Three weeks later, nothing had changed. The recommendation I had presented was still sitting in a queue somewhere. The decision-makers had nodded and moved on.

I have thought about that presentation many times since. I understand now what happened – and it had nothing to do with the slides or the delivery. The problem was that I had structured the entire thing as a monologue. I had designed it to be received, not responded to. And people received it, exactly as designed, and then went back to their day.

That experience fundamentally changed how I think about what a presentation is actually for.

The Question That Changed How I Prepare

Since then, when I start preparing any significant presentation, I ask myself a single question before I open any software: what do I need the audience to do differently after this conversation?

The word “differently” is doing a lot of work there. It rules out vague outcomes like “understand our strategy” or “be aware of the project status.” Those are not actions. They are mental states that look identical from the outside to not having listened at all.

When I force myself to answer the question honestly – what specific behavior, decision, or commitment do I need from this audience – the entire structure of the presentation changes. I stop organizing around what I know and start organizing around what the audience needs to believe in order to act.

This is a harder way to prepare. It requires knowing your audience’s current position well enough to identify the gap between where they are and where you need them to be. It requires deciding which arguments are actually necessary and which are just comfortable to include because you spent time on them. And it requires building an ending that asks for something, rather than summarizing what was said.

Why Most Presenters Organize Around Themselves

The structure-around-the-presenter pattern is extremely common in corporate settings, and it makes a certain kind of sense. You are the one who did the work. You are the one who knows the material. Organizing around your own knowledge and journey through the subject feels natural.

The difficulty is that your journey through the material is almost never the right journey for your audience. You started from uncertainty and worked toward a conclusion. Your audience is starting from their own existing knowledge, priorities, and concerns – which may be very different from yours. Walking them through your analytical journey means asking them to care about problems you have already solved, in the order you happened to encounter them.

What the audience actually needs is to understand the conclusion, understand why it matters to them specifically, understand the key evidence that supports it, and understand what they are being asked to do about it. That sequence is almost the reverse of the natural “I’ll show you how I got here” approach.

I work on this in detail in business storytelling training – specifically the question of how to restructure a presentation so the audience’s needs drive the narrative rather than the presenter’s knowledge organizing it.

The Danger of the Detailed Slide as a Safety Net

There is one habit I see in almost every professional who has been trained in a rigorous analytical environment – consulting, finance, engineering, law – and that is the instinct to put everything on the slides. Every assumption, every data point, every caveat, every supporting calculation.

I understand this instinct. In written reports, completeness is a virtue. In analysis, leaving something out feels like intellectual dishonesty. And in some professional cultures, a presentation with sparse slides suggests that you have not done the work.

But I have found, both in my own experience and in working with hundreds of participants in presentation training, that comprehensive slides and persuasive presentations pull in opposite directions. The more complete the slide, the less the presenter is needed. And when the presenter is not needed, the relationship between speaker and audience dissolves – what remains is a person standing next to a document that could have been emailed.

The slides that work best in actual presentation settings are the ones that are deliberately incomplete. They create a question in the audience’s mind that only the presenter can answer. They make the person in the room necessary.

A Structural Habit That Made My Presentations More Honest

One of the most useful changes I made to my own preparation was adding a single slide near the beginning that I never used to include: a slide that states, in plain language, what I am asking for and why now. Not a title slide, not an agenda – a slide that says, “Here is the decision I need from you today, and here is what happens if we make it or delay it.”

Putting that slide early does something uncomfortable and useful at the same time. It removes my ability to hide behind the analysis. I can no longer treat the presentation as an exploration and hope the audience arrives at my conclusion on their own. I have to commit to the ask, out loud, before I have earned it with evidence – and then spend the rest of the time earning it.

That discomfort turned out to be the point. When the ask comes first, every subsequent slide has a job: it either supports the decision or it does not belong. The structure forces a kind of honesty about what is essential. Anything that does not move the audience closer to the decision becomes visibly optional, and most of it can be cut or moved to an appendix.

What Actually Changed

I would like to say that once I understood all this, my presentations started landing every time. That would not be true. Audiences are complicated, timing matters, and plenty of good recommendations fail for reasons that have nothing to do with how they were presented.

But the failure mode changed. I stopped losing decisions because no decision was ever clearly requested. I stopped delivering polished monologues that left the room exactly as it entered. When a recommendation of mine gets rejected now, it usually gets rejected on its merits – because I made the ask clear enough to be argued with. And a recommendation that can be argued with is a recommendation that can also be accepted.

That is the shift, in the end. A presentation is not a performance you complete and a room receives. It is a request you make of specific people, built so that saying yes is the easiest reasonable response. Everything else – the slides, the timing, the delivery I was once so proud of – only matters to the extent that it serves that request.

If you take one thing from this: before your next presentation, write down the single sentence that describes what you want your audience to do differently. If you cannot write that sentence, no amount of polish will save the presentation. And if you can, you have already done the most important part of the work.