Is this deck for the room or for the inbox?
Slides built to be presented and slides built to be read are different documents. Deciding which one you're making ends the wall-of-text problem.
Built from a decade of presenters, consultants, engineers, and the people in their audiences arguing about slides — including the camp whose industries genuinely require dense decks, carried here as correct in their context rather than argued away.
You have sat through it: the lights dim, the first slide is a wall of sentences, and the presenter turns and reads it to you — a human audiobook — the word that recurs in these arguments, with real frustration behind the joke. The mechanism of the boredom is simple and worth knowing: you read faster than a speaker talks, so you finish the slide, wait, and stop listening — and a listener who is reading isn’t listening even before the waiting starts. Presenters keep building that slide anyway, and one account traces the habit to school, where the deck gets graded instead of the talk, so cramming text on slides was literally what the points rewarded.
The usual repair is a rule — fewer words, fewer bullets. The advice here starts with that rule and then does something more useful: it argues, at length and from real workplaces, about where the rule fails. What survives the collision is a question instead:
Decide the deck’s job before you design a single slide. A deck you present live stays sparse — you are the information, and the details go in your notes. A deck that travels without you is a document and needs a document’s detail. Walls of text come from forcing one deck to do both jobs at once.
For the deck that stays in the room, the craft notes here are consistent. Keep the visible text to key phrases — people cite conventions like the 6x6 rule (six bullets, six words each) less as law than as a leash. Prefer a chart, a diagram, a picture: more than one account notes visuals outlast text in the audience’s memory, and one person’s test for a strong deck is that someone who can’t read the language could still follow the shapes of it. Put every full sentence you’re tempted to show into the speaker notes instead — the deck stays clean, and the notes become your script and a readable version for whoever opens the file later. Guide attention by duplicating a slide and adding one element per copy rather than reaching for animation effects. One person adds a time test: if a slide needs more than about fifteen seconds of explanation, it should be a visual, not text. More than one conversation lands under ten slides for a fifteen-to-twenty-minute talk. For executive rooms, one account recommends stating the conclusion on slide one — one account warns that decision-makers interrupt, so don’t build to a climax you may never reach. And two small stagecraft moves, one person each: put your strongest, most curiosity-provoking material early, because the hook has to land before the boredom does; and drop an occasional blank slide between sections, so eyes return to you.
Delivery has its own split, worth respecting: some people here script and rehearse until the talk is word-perfect, and others learn their subject deeply but refuse a script, because reciting makes them trip over their own sentences. Both report it working. The shared ground under both camps is that the speaker, not the deck, is the presentation — storytelling and engagement are the learnable skill, and a good talk survives bad slides far better than good slides survive a bad talk.
And for the deck that travels — the consulting deliverable, the finance read-ahead, the engineering trip report, the deck leadership will read with nobody presenting it — density is not a sin. One person draws the line cleanly: a deck that stands on its own is a written report wearing slide clothes, and the mistake is pretending it’s also a live visual aid. If your week demands one file that does both, people here offer working bridges: write the whole argument out as a report before touching a slide, then distill the deck from it, so the report ships as the depth; keep the live section sparse and park detail slides in an appendix behind the ending; use the hide-slide function so density ships in the file but never hits the screen; or simply make two decks and stop negotiating.
Who this page isn’t for: if your deck is never going to be presented aloud, you aren’t preparing a presentation — you’re writing a report, and the report conventions win. And if the deck is fine but the standing-up part is the wall, that’s stage fright, not slide design; the conversations behind this page reach for that question and don’t answer it, so treat the caveat below as the honest boundary it is.
The next time the file is open and empty, ask it the question in this page’s title before you type. Room or inbox. Everything else — the word counts, the appendix, the notes pane, even the argument with your boss about density — sorts itself under whichever answer is true.
The community disagrees on this one
Run the slide argument long enough and it lands on the same fork: how much should the deck itself carry?
Sparse slides, spoken depth
This camp treats the deck as scenery for a talk: a handful of visuals and key phrases, everything else spoken or tucked into the notes. Their reasoning is mechanical — a screen full of sentences competes with the person saying them, and the screen wins. If detail must exist, it belongs in a handout, an appendix, or a report.
4 independent accounts
Dense slides, because the deck travels
This camp lives where the deck is emailed, filed, and read by people who never heard the talk: clients, executives, auditors, absent decision-makers. A sparse deck arriving without its speaker is a riddle. In their rooms, detailed slides aren't lazy design — they're the document of record doing its job.
4 independent accounts
The deciding question, named on both sides: how will this deck mainly be consumed — live, with you talking, or later, without you? The camps stop arguing the moment that's answered. Where one file must do both jobs, the bridges are in the first FAQ.
Common questions
My company expects dense, detailed slides. Is everyone here just wrong?
No — and the people giving the minimal-slides advice concede it themselves once the argument runs long enough. One account from consulting describes clients who want every timeline and framework on the page. Finance and executive audiences, another says, treat the deck as their own notes. In engineering and supply-chain work, one account explains, decks double as trip reports and test results in place of documents — and a separate account observes that a deck gets read where a long report doesn't. In defense and similarly audited fields, one person explains, substantiating detail stays in the deck for the future reader, because the deck itself is the document of record. And one account describes organizations that deliberately pack everything onto the slides so leadership reads ahead — the live meeting is just key points and questions. None of that is bad presenting — it's a different document with a different job. The failure isn't density; it's denying the split. If your workplace's deck is really a report, build it as a report and don't torture it into minimalism — and if you still have to present it live, use the bridges people here use: a sparse front section with the density in an appendix, hidden slides that ship in the file but stay off the screen, or two versions of the same deck, one for the room and one for the inbox.
What do I do about the technology failing?
Treat the venue as a stranger. A few practiced presenters here describe their kits, and the kits rhyme: the file in more than one format and more than one place, every video or audio clip saved locally on the machine that will play it — links die on venue networks and firewalls, one person warns — plus their own adapters and cables, and their own laptop where allowed. One person keeps a separate, clean computer account just for presenting, so no pop-up, personal file, or browser history can walk on stage. Several accounts insist on a full dry run on the actual equipment — days before if you can, again that day — because rehearsal catches broken fonts, missing hardware, and content errors, and because live demos fail in ways a local test didn't predict. Two cautions ride along. First, a camp in these conversations pushes back on the 'assume everything will break' framing itself: testing is an action, dread is a mental state, and if the preparation is feeding anxiety instead of confidence, dial it back to what the stakes actually require. Second, the deepest backup isn't in the bag — one person puts it flatly: if you can't deliver your material without the slides at all, you aren't ready yet. Know it well enough to keep talking to a blank wall, and a technical failure becomes an anecdote instead of an ending.
Should slides show numbers, like 'slide 8 of 30'?
The running total is the version people here argue against with the most experience behind them. A few defend it — knowing how far along things are can feel like control, and some listeners genuinely hate not knowing. But the better-evidenced side, including people who present professionally, reports that a visible countdown pulls attention off the content and onto the clock, gets removed on client request, and tends to get noticed just when a talk is already losing the room — one person's blunter version: if the audience is watching the slide counter, the counter isn't the problem. A practical middle appears in the same conversations: keep small slide numbers for navigation — they're genuinely useful when someone in Q&A says 'go back to slide 12' or when the deck circulates afterward — and skip the 'of 30' total. And if you feel the urge to reassure people about how much is left, one account suggests reading that urge as data about the talk, not the numbering.
Full tip: https://findangel.org/tips/is-this-deck-for-the-room-or-for-the-inbox · FindAngel.org — free, always.