How to give a presentation

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.

Here is the whole process in order:

1. Write your conclusion as one sentence before you open any slide software.
2. Build a spine: the setup, the two or three load-bearing points, and the ask.
3. Size the material to the clock — cut until it fits with room to breathe.
4. Build simple slides, one idea each, in the order of the spine.
5. Run it out loud from the spine alone, no slides, to test the argument.
6. Record a full run, find the single weakest moment, and fix only that.
7. Do a timed dress run standing up, with the real deck and the real room if you can.
8. Do a tech and logistics check the day before, not ten minutes before.
9. Deliver it: settle your pace, pause at the section seams, and finish the ask cleanly.
10. Take questions as the most useful part of the session, not the part to survive.

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.

This guide covers the fundamentals that hold regardless of setting. If your session is over a call rather than in a room, pair it with how to give a virtual presentation for the parts that are genuinely different online — the tech rehearsal, an opening built for a distracted audience, and what to do when the connection drops.

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 — and if you are writing out full sentences rather than speaking from that card, how to write a speech covers the word budgets and the read-aloud drafting method that keep a script sayable:

1. 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.
2. 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 first thirty seconds carry more weight than any other part of the talk, so it is worth reading our guide on how to start a presentation before you write this line.
3. 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.
4. 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 — our guide on how to end a presentation covers the exact wording and where to place Q&A so your close is not the last thing to get improvised.

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.

How long should a presentation be, and how many slides?

Make it as long as the argument needs and no longer, and plan for roughly one to two minutes per slide. The most quoted benchmark is Guy Kawasaki's 10/20/30 rule — ten slides, twenty minutes, no font under thirty points — written for startup pitches but useful anywhere as a ceiling to argue against rather than a law to obey.

The number that actually matters is not the slide count. It is words per minute against the clock. A typical conversational rate is

~150 wpm

Source: National Center for Voice and Speech

so a ten-minute slot is roughly 1,500 spoken words — and that is before questions, pauses, or the thirty seconds you will lose to a laptop that will not wake up. Most people write two to three times that much material and then speed up to fit, which is exactly the failure mode described in how to stop talking too fast.

Some working numbers to plan against:

Slot	Aim to fill	Load-bearing points	Rough slide count
5 minutes	4 minutes	1–2	3–5
10 minutes	8 minutes	2–3	5–8
20 minutes	16 minutes	3–4	8–12
45 minutes with Q&A	30 minutes	3–4, with examples	12–18

What should your slides actually do?

Slides should carry what your voice cannot: a number that needs to be seen, an image, a diagram, a before-and-after. Everything else belongs in your mouth, not on the wall. The moment a slide contains your full sentence, the audience reads it faster than you can say it, finishes ahead of you, and stops listening.

Four rules that hold across almost every setting:

• One idea per slide. If you need "and" to describe what a slide is about, it is two slides.
• Six words or a picture. A headline that states the point, or a visual that makes it. Not both, and not a paragraph.
• Big enough to read from the back row. Thirty points is the usual floor; if you are squinting at your own laptop, the room is lost.
• No slide you have not said out loud. An unrehearsed slide is where you will stall, because you have never built the sentence that connects it to the one before.

The slide you are most attached to is usually the one to cut. Fondness for a slide is almost always about the work that went into it, not the work it does for the audience.

If you already know you narrate your bullets and can't seem to stop, that is a filing problem rather than a discipline problem — how to stop reading off your slides covers how to split the deck from your script and set up presenter view so your words live somewhere only you can see.

The one thing worth spending a slide's worth of time on instead is a short, true incident that makes a load-bearing point concrete — storytelling in public speaking covers the structure and the length budget for that.

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.

A clear spine can still fall flat if the delivery does — a well-structured talk read in a flat, unchanging voice loses the room just as fast as a muddled one. If that sounds familiar, see how to stop sounding monotone for the pitch, pace, and pause habits that make rehearsed material sound alive instead of recited.

How do you rehearse before you give a presentation?

Rehearse on a timeline, not in one panicked block the night before. Cramming five run-throughs into the last evening produces a talk you have memorized and cannot deliver; spacing the same five reps across a week produces one you own — and for the tail end of that timeline specifically, what to do the night before a presentation covers why the last evening should hold exactly one run and then stop. Each pass should have a single job, and the jobs go in order — argument first, then delivery, then conditions.

What each pass is for:

• T−7, write the spine. Conclusion, setup, two or three points, ask. No slide software. If it does not survive being said in ninety seconds, keep cutting.
• T−5, first out-loud run. From the index card only. This is where you find the sentences you cannot actually say — the ones that read fine and collapse in your mouth.
• T−3, record and review. Full run with slides, recorded on your phone. Play it back once and find the single weakest moment. Fix that one thing and run it again, not five things at once — a broader version of the same loop is in how to practice public speaking.
• T−1, timed dress run. Standing, real deck, clicker in hand, timer running. If you can get into the actual room, do it — the sightlines and acoustics change how you pace.
• T−10 minutes, reset. Do not run the whole thing again. Say your opening line twice, breathe, and stop. Late cramming raises your heart rate and rewrites nothing.

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 deliver a presentation on the day?

Delivery on the day is mostly logistics plus three physical habits. The logistics are dull and they are where most avoidable disasters live:

• Arrive early enough to plug in, mirror your screen, and click through the first two slides.
• Bring the deck three ways: your laptop, a USB stick, and a copy in the cloud you can open on someone else's machine.
• Check the room from the back row. If the bottom of your slide is below a head, move that content up.
• Find where you will stand, and where your notes will sit so you are not looking down at a table edge.
• Silence your notifications on every device that will be visible or audible.

Then the three habits that carry the delivery itself:

Pace. Settle into a band around 140–160 words per minute and let it drop below that for anything you want remembered. Nerves add speed you will not feel, so aim deliberately slower than feels natural.

Pauses. Put a real silence at each section seam — after the setup, after each load-bearing point, and before the ask. A two-second pause reads as command of the room; it is also the thing that stops filler creeping in, which is the mechanism behind how to stop using filler words.

Eyes and hands. Hold one person's gaze for about a full sentence — three to five seconds — then move to a different part of the room; scanning constantly reads as nervous, and how to make eye contact when public speaking covers the pattern for larger rooms. Keep your hands visible and above the waist rather than clasped or pocketed, which is the short version of what to do with your hands when public speaking.

If the room is large or unmiked, the constraint changes from clarity to carry, and you need the breath support described in how to project your voice.

What do you do when something goes wrong mid-presentation?

Something usually does. The difference between a presenter who recovers and one who unravels is that the first has decided in advance what the recovery looks like.

• The tech fails. Keep talking. You rehearsed from an index card for exactly this reason — the spine is the presentation, the deck is the visual aid. Narrate the missing slide in one sentence and continue while someone else fixes it.
• You are running over. Do not speed up. Cut a load-bearing point mid-flight, say "I'll skip ahead to the part that matters for the decision," and go straight to the ask. Overrunning at pace is worse than arriving early with less.
• You go blank. Stop, look at the current slide, and say the one point that slide exists to make. The silence is far shorter than it feels — what to do when your mind goes blank covers the recovery move in full.
• Someone interrupts with a challenge. Answer it briefly if it is quick, or park it explicitly: "Good question — that's exactly where I'm going in two slides." Parking is only credible if you actually come back to it.
• You lose the room. Ask a question. Any genuine question that requires an answer resets attention faster than pushing harder through the material — and there are three other recovery moves worth having ready, set out in how to keep an audience engaged.

How do you handle nerves and questions?

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 the physical side of nerves — the racing heart and shaky hands that rehearsal alone does not always touch — pair this with a short pre-talk routine. Our guide on how to calm presentation nerves walks through a breathing technique and a ten-minute routine you can run right before you stand up.

Room size changes the delivery as well as the nerves. Everything above assumes a meeting room or a modest auditorium; once you are on a stage in front of hundreds, the acoustics, sightlines and microphone all demand specific adjustments to pace, pauses and gesture size. How to speak in front of a large audience covers those mechanics.

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.

For the full playbook — including hostile questions and what to do when the room goes silent — see how to handle questions after a presentation.

How does this change for a work update, a conference talk, or a class presentation?

The spine and the reps do not change. What changes is what the ask is, and how much context the room already has.

A work update or internal proposal. The room knows the background and wants the decision. Lead with the conclusion and the ask in the first thirty seconds, then justify backwards. Assume you will be interrupted and that the Q&A is the real meeting; budget half your slot for it. When the room is senior enough that the interruptions start in the first two minutes, how to present to executives covers the ninety-second open and the recovery move that keeps you from losing your thread.

A conference or external talk. The room has no context and did not have to come. The setup carries far more weight — you have to earn attention before you can spend it. One idea, one story that makes it concrete, and a takeaway they can repeat to a colleague afterwards. The room also has no reason to trust you yet, so the credential you give in your first thirty seconds matters more here than anywhere else; how to introduce yourself in a presentation covers the fifteen-second version and what to say when the host has already read your bio.

A class or student presentation. There is a rubric, and it is usually a better spine than anything you would invent. Map your sections to the marking criteria, keep to the time limit exactly — going over is the most commonly penalised mistake — and rehearse the transition sentences, because that is where nerves show most. If you have never written one, speech transitions has a close-and-open formula and a full worked set for a five-minute talk.

A sales or pitch presentation. The ask is the point and everything else serves it. Say what you want, early, and make the load-bearing points the reasons the buyer should agree, not the features you are proud of.

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.
• Size it to the clock. Roughly 150 words a minute, and build for about 80% of your slot so live delivery has room to breathe.
• Rehearse on a timeline, one job per pass. Spine at T−7, out-loud run at T−5, recorded review at T−3, timed dress run at T−1, reset at T−10 minutes.
• Decide your recovery in advance. Tech failure, overrunning, going blank, and interruptions all have a rehearsed move.
• 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 long should a presentation be?

Long enough for the argument and no longer — and shorter than your slot. Plan for roughly 150 spoken words per minute, so a ten-minute talk is about 1,500 words, and build to fill around 80% of the time you are given. Live delivery always runs slower than rehearsal, and finishing early is read as command; overrunning is read as poor preparation.

How many slides should a presentation have?

Roughly one slide per one to two minutes of speaking, so about five to eight for a ten-minute talk. Guy Kawasaki's 10/20/30 rule — ten slides, twenty minutes, thirty-point minimum font — is a useful ceiling. The count matters far less than the rule behind it: one idea per slide, and nothing on a slide you have not said out loud in rehearsal.

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.

How do you give a presentation without notes?

Not by memorising it. Know your spine — conclusion, setup, two or three points, ask — well enough to recite it in ninety seconds, and let the exact words vary each run. Learn only the opening, the transitions between sections, and the closing verbatim. Those are the seams where people stall, and locking them down is what makes the rest safe to improvise.

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. The exception is the seams: our guide on how to memorize a speech makes the case for learning your opening, closing, and transitions verbatim while leaving the middle loose.

Conclusion

A presentation is not a deck you narrate — it is one clear argument you deliver, sized to the clock, and rehearsed out loud on a real timeline until nerves and questions cannot knock it over. Slides are the visual aid; you are the presentation. Pick the talk you have coming up, write its spine on an index card tonight, and say it out loud once before you touch a slide.