Walk into any office on any given week and you will find someone, somewhere, building a slide deck that nobody will ever present. They will email it. The recipients will open it on their laptops, scroll through it in silence, and form an impression — usually a confused one — before moving on.
This is the central muddle of modern presentation work. We use the same tool, the same template, and the same word — “deck” — for two completely different jobs. One job is to support a person speaking to an audience. The other is to communicate information to a reader on their own. The two jobs need almost opposite designs. The most common presentation mistake is not ugly slides. It is slides built for one job and used for the other.
Two completely different audiences in the same file
A slide that supports a speaker is meant to be glanced at while you listen. The voice in the room is doing most of the work; the slide is reinforcing it, giving the eye somewhere to land, providing the diagram or photograph or chart that the words alone could not carry. The slide is a prop. The speaker is the act.
A slide that is read alone is doing all the work itself. There is no voice. There is no live explanation, no opportunity to ask a question, no one to point at the chart and say “but look at this column.” Everything the reader needs has to be on the slide, in a form that makes sense without help.
These are two very different products. A good speaker-support slide has very few words. A good read-alone slide has whatever words it needs to be understood. A speaker-support slide can be visually bold and emotionally striking. A read-alone slide needs to be navigable, linear, and self-explanatory.
If you imagine the two on opposite ends of a spectrum — pure visual prop on one side, pure self-contained document on the other — most slide decks made for business sit awkwardly in the middle. Too wordy to be effective behind a speaker. Too thin to stand on their own. The result is a deck that does neither job well.
Why reading and listening are not the same
The deeper reason these two jobs cannot share a design is that reading and listening work differently in the brain. When someone is listening to a speaker and looking at a slide at the same time, both channels compete for attention. If the slide has more than a few words, the audience reads. Reading wins over listening, every time. The speaker becomes background noise behind their own slide.
This is why dense slides during a live presentation fail so consistently. It is not that the audience is rude or distracted. It is that the architecture of the situation does not allow them to do both. Either they read the slide and ignore the speaker, or they listen to the speaker and ignore the slide. The slide content is not actually being absorbed twice.
A slide built to be read alone, in contrast, is fine if it takes a minute or two to work through. The reader is not racing against a voice. They can pause, scroll back, sit with a chart. The deck behaves like a document, which is what it has become.
What “speaker support” actually looks like
A slide built to support a speaker tends to be sparse. One idea, sometimes one word. A photograph that anchors the point. A chart with the one number that matters made large. A diagram that you would draw on a whiteboard if you had one.
The speaker provides the context. They explain why the photograph matters. They walk through the diagram. They give the chart its caveats. The slide does not need to do those things, because a human being is doing them in real time. The slide is there to give the audience somewhere to look while it happens.
Decks built this way feel uncomfortable to people who have not used them before. They look thin. There is a temptation, especially before a high-stakes meeting, to “add a bit more” — a second bullet, a clarifying line, a footnote. Resist this. Every word added to a speaker-support slide is a word the audience will read instead of listening to the speaker.
What a read-alone document actually looks like
A slide built to be read alone, by contrast, has the structure of a short report. It has headings, body text, and the supporting visuals you would expect in a document. It uses full sentences, not bullet fragments. Charts have axis labels and captions. Diagrams have legends. There is enough text on the page to carry the meaning without a speaker to interpret it.
This is, in honest moments, a document with slide dimensions. And that is fine, as long as the maker knows that is what they are making.
The mistake comes when people try to keep the “presentation” look — minimal text, big visuals, dramatic slides — while expecting the deck to also be sent and understood on its own. The reader opens a deck of fifteen slides that say things like “Vision: First in Class,” “Strategy: Disrupt,” and “Outcome: Growth,” and is left to invent the explanation themselves. They invariably invent the wrong one.
A simple rule of thumb
Before building a deck, ask one question: how will this be consumed? Spoken to a live audience, with the maker in the room? Read alone, on a laptop, with the maker absent? Both — first presented, then sent around afterward?
The answer changes what you build.
If it is purely spoken, go sparse. Trust yourself. The audience will hear what you say.
If it is purely read, design for a reader. Use full sentences. Give context. Caption your charts. You are writing a document; the fact that it lives in PowerPoint is incidental.
If it is both, the cleanest answer is to build two versions, not one. A spoken deck for the meeting, and a brief written summary — even one page — to send around afterward. This is slightly more work and considerably more effective than the universal compromise, which is a deck that fails twice.
The handout problem
The “send the deck afterward” tradition is so ingrained that it usually overrules everything else. People design their slides knowing they will need to be read alone, and they pack them accordingly, then deliver a live presentation that the audience cannot follow because the slides are too dense.
There are better ways to handle the handout. A two-page summary written for reading, separate from the deck, almost always communicates more than the deck itself. A short follow-up email with the key points and an offer to discuss is even simpler. The notes field in the slide tool is underused — adding the speaker’s narrative there lets a sparse deck travel afterward as something close to a transcript.
None of these are exotic. They are just slightly more deliberate than the default, which is to use the same fifteen slides for two opposite purposes.
The short version
A slide deck is not one thing. It is a tool that gets used for two completely different jobs — speaker support and standalone reading — and the design rules for those jobs are not the same. The most reliable improvement any presenter can make is to decide, before they open the template, which job they are doing. Designing for one job at a time is harder than designing for both at once, because it forces a choice. But the choice is the point. A deck that knows what it is for will always communicate better than a deck that is trying to be everything.
