Most advice on how to give a presentation is really advice on how to make slides: use bigger fonts, fewer bullets, better images. None of it is wrong. All of it is beside the point, because the deck is not the presentation. You are. The slides are a visual aid for an argument you are making out loud, and if the argument is muddled or you have never actually said it, no amount of design will save you.
A presentation is a specific job, and it is not the same as general public speaking. Public speaking is about being able to speak clearly under pressure. A presentation adds a second problem on top of that: you have to take a body of material — a project update, a proposal, a set of findings — and shape it into something a room can follow in the time you have. This guide is about both problems, in order: first build a thing worth delivering, then rehearse it until you can deliver it.
What makes a presentation good, not just polished?
A good presentation has one clear point and gets the audience there without making them work. Polish is a distant second. A beautifully designed deck that leaves people unsure what you were asking for has failed; a plain one that ends with the room nodding at a clear decision has succeeded. The test is not "did that look impressive?" but "can someone repeat my point back in one sentence?"
Almost every weak presentation shares the same fault: it is a data dump, not an argument. The presenter has assembled everything they know and marched the audience through all of it, hoping the point will emerge on its own. It never does. An audience cannot hold twelve facts and infer your conclusion in real time. Your job is to do that work for them — to decide what the facts mean and lead them to it.
Before you open your slide software, finish this sentence out loud: "The one thing I want this room to remember is ______." If you cannot fill the blank in a single clause, you are not ready to build slides. You are ready to think.
How do you structure a presentation?
Structure a presentation as a spine: a single conclusion, plus the three or four points that lead a listener to it. Write the conclusion first, then work backwards — what would someone need to accept, in what order, to arrive there? Those steps are your sections. Three or four is plenty. More than that and the audience loses the thread; you are back to a data dump with nicer transitions.
The spine is not the deck. It is a few lines you can write on an index card or the back of an envelope:
- The conclusion. What you want to be true in the room when you finish — a decision made, a budget approved, an idea understood. One sentence.
- The setup. Why this matters now, in one or two sentences. Give the audience a reason to spend attention before you ask for it.
- The two or three load-bearing points. Each one is a step from the setup to the conclusion. Not everything you know — only what the argument needs.
- The ask. What you want the room to do next. Say it plainly. Presentations that end with "so, yeah, that's it" waste the one moment people are most ready to act.
Once the spine holds up when you say it out loud with no slides at all, then you build slides — one idea per slide, in the order of the spine. The slide supports the sentence you are saying; it is not the script. If a slide is doing the talking, you have become the person reading their own deck, and the room has started checking email.
A fast structure test: try to deliver the whole thing in ninety seconds from the index card, no slides. If you cannot, the argument is not clear yet — and slides will hide that from you, not fix it. This is the same discipline behind a good elevator pitch: one idea, said cleanly, in order.
Why does rehearsing out loud matter so much?
Rehearsing out loud matters because presenting is a motor skill, and you cannot train a motor skill in your head. Silent practice — reading your slides, running the talk mentally — feels productive and trains almost nothing. In your head, every sentence is smooth. Spoken aloud, the same sentences ramble, double back, and fill with "um." The gap between the two only appears when you open your mouth, and a live audience is the worst place to discover it.
There is a second reason. The thing that breaks under pressure is not your knowledge of the material — it is your ability to assemble clear sentences while a room watches and your heart rate climbs. Reading the deck a fourth time does nothing for that. Saying the talk out loud, start to finish, standing up, trains exactly the skill that fails. Each full run is one rep. Do at least three. The first will be worse than you expect; that is the point of doing it in private rather than in front of the people who matter.
Do not confuse knowing your slides with knowing your talk. You can click through a deck flawlessly and still stumble the moment you have to say the words connecting one slide to the next — because you have never actually said them. Rehearse the words between the slides, not just the slides.
A tight rehearsal loop looks like this. Say the whole thing out loud. Record it on your phone. Play it back and find the single weakest moment — a rushed section, a point that did not land, a place you lost yourself. Fix only that one thing. Run it again. Three to five passes and the talk stops being something you hope to get through and becomes something you can deliver. If you want a tool built around that exact loop — out-loud reps, honest feedback, realistic pressure — that is what the best public speaking app is for.
How do you handle nerves and questions on the day?
Handle nerves by having rehearsed enough that the talk runs on rails when your mind goes blank — preparation is the only reliable cure, not willpower in the moment. And handle questions by treating them as the most valuable part of the session, not a threat to survive. The Q&A is where the room tells you what they actually care about. A presenter who welcomes questions looks far more credible than one who races to the end to avoid them.
Nerves are normal and they never fully disappear; the goal is not to feel calm but to be able to perform while not calm. Deep preparation does most of the work — when the words are drilled, you can deliver them on autopilot while the adrenaline burns off. For the underlying fear itself, the same reps-based approach applies as with any fear of public speaking: exposure, not avoidance.
For questions, three habits carry most of the weight:
- Pause before answering. A two-second silence reads as thoughtful, not slow. It also buys you time to hear the real question rather than the first words of it.
- Answer the question they asked, briefly, then stop. Over-answering out of nerves is how you talk yourself into a corner. Say the answer and let the room come back if they want more.
- "I don't know, I'll find out" is a strong answer. Bluffing a number you are unsure of is the fastest way to lose the room's trust. Admitting a gap calmly does the opposite.
None of this requires natural charisma. It requires composure, and composure comes from reps — the same way you build any other kind of confidence when speaking. You are not trying to be a different person on stage. You are trying to be a well-rehearsed version of yourself.
Key takeaways
- The deck is not the presentation — you are. Build the argument first; slides are a visual aid for it, not a substitute.
- Write a spine, not a script. One conclusion plus three or four load-bearing points that lead the room to it. Cut everything else.
- One idea per slide, in the order of the spine. If a slide is doing the talking, you have started reading your own deck.
- Rehearse out loud, standing up, at least three times. Silent practice trains almost nothing; the words between slides are what fail.
- Welcome questions. Pause, answer what was asked, and say "I'll find out" rather than bluff. Composure comes from reps, not charisma.
Frequently asked questions
How do I structure a presentation if I have a lot of material?
Cut it to a spine: one conclusion and the three or four points that lead there. A lot of material is not a reason to include a lot of material — it is a reason to decide what it means and present only that. Move the rest to an appendix or a follow-up document the audience can read later.
How long should I spend on slides versus practising?
Far less time on slides than most people do, and far more rehearsing out loud. A rough split: build the spine, make simple slides, then spend the majority of your remaining time saying the talk aloud, start to finish. Polished slides you have never spoken over lose to plain slides you have rehearsed three times.
What if I go blank in the middle of presenting?
Pause, look at your current slide, and say the one point that slide exists to make. That is why the spine matters — each slide anchors one idea, so a blank moment becomes "what is this slide for?" rather than "what was I saying?" Rehearsal makes the recovery automatic. A short silence looks composed; it is far less visible to the audience than it feels.
How do I make a presentation less boring?
Have a point and get to it. Most boring presentations are boring because they are a data dump with no argument — the audience cannot tell where it is going or why they should care. A clear conclusion, stated early and paid off at the end, is more engaging than any animation. Cut anything that does not move the argument forward.
Should I memorise my presentation word for word?
No. Memorising a script makes you brittle — one dropped line and you are lost, and it usually sounds recited. Instead, know your spine cold and rehearse until the words come naturally each time, slightly different but always on point. You want to know what you are saying, not recite what you wrote.