A strange thing happens after a good meeting: the presentation disappears.

People may have watched every slide, nodded at the important numbers, asked questions, and even agreed with the recommendation. A week later, the same deck sits untouched in an email attachment or shared folder. When someone finally opens it again, they often have to ask the original presenter what half the slides were supposed to mean.

The often-repeated claim that “70% of presentations are never read again” is not something I would treat as a verified industry statistic without a named study behind it. But the underlying problem is very real: a deck can succeed as a live performance and fail completely as a reusable document.

The presentation was built for the meeting, not for the person who opens it later

This is the first distinction most teams miss.

During a meeting, the presenter supplies context that never appears on the slide. They explain why a chart matters, define an acronym, point at a particular number, and answer the obvious question before anyone has to ask it.

Remove the presenter, and the slide may suddenly become almost meaningless.

A title such as “Q3 Performance” tells a future reader almost nothing. Was performance good? Bad? Better than expected? Which metric matters? What decision followed from it?

Compare that with a headline such as “Q3 revenue grew 18%, but enterprise churn offset half the gain.” The second slide has already done part of the explanatory work before anyone reads the chart.

This is one reason ImagineLayout recommends headlines that state the conclusion rather than simply naming the topic. A presentation designed for skimming has to communicate its point without relying entirely on the speaker. How to Build a Presentation People Watch to the End

People do not reread slides the way they reread documents

A report invites reading. A presentation usually invites scanning.

That difference becomes important after the meeting. Nobody wants to reconstruct a 30-slide presentation by reading every sentence from beginning to end just to find one decision or number.

The useful question is therefore not “Can someone read this slide?” It is “Can someone find the important information on this slide without the presenter standing next to it?”

That changes how you build the deck.

  • Use the headline to communicate the takeaway.
  • Make charts answer a specific question rather than merely display data.
  • Keep supporting detail close to the claim it explains.
  • Make important numbers visually discoverable.

This does not mean turning every slide into a minimalist poster. Data-heavy presentations sometimes need detail. The mistake is forcing the reader to determine the hierarchy for themselves.

The most expensive slide is often the one nobody understands without you

Imagine a manager receives a presentation three weeks after the meeting. They remember that there was something important about customer retention, but they do not remember which slide contained it.

They open the deck.

Slide 7 says “Customer Retention.” Slide 8 says “Retention by Segment.” Slide 9 says “Customer Metrics.” Slide 10 contains a chart with six colored lines.

The information may all be there. The usability is not.

One thing people overlook is that retrievability is part of presentation design. A deck that will be reused should help someone locate the answer without remembering the original conversation.

This is where a clear slide sequence becomes more valuable than decorative consistency. ImagineLayout's discussion of presentation structure makes a similar point: the three-part structure is not enough by itself; proportion, sequencing, and the relationship between sections determine whether the audience can follow the argument. How to Structure a Presentation Using the Rule of Three Parts

There is a second problem: some decks contain too much evidence and too little meaning

Teams often respond to the fear of being misunderstood by adding more information.

Another chart. Another footnote. Another paragraph explaining the previous paragraph.

It feels safer because everything is documented. In practice, the important point can become harder to find.

I often see this when a presentation is built from a spreadsheet or report. The author wants the slide to preserve every useful piece of evidence. But a reference deck does not need every piece of evidence on every slide. It needs enough context for the reader to understand the claim and enough structure to find deeper information when necessary.

ImagineLayout's slide-design guidance puts the same principle into practical terms: when a slide contains too much content, splitting the slide is generally preferable to shrinking the typography until the audience has to work to read it. 10 Rules for Designing Slides That Don't Bore Your Audience

A meeting deck and a reference deck are not always the same thing

This is where the usual “keep every slide simple” advice stops being useful.

A live presentation may deliberately reveal information one step at a time. A reference version cannot depend on that sequence. A presenter can say, “Look at the highlighted bar on the right.” A person reading the PDF later needs the slide itself to make that bar obviously important.

Sometimes the best solution is not to force one deck to perform both jobs.

You can have a concise presentation for the meeting and a slightly more detailed appendix or reference version for people who need to revisit the material afterward.

The trade-off is straightforward: a presentation optimized only for live delivery may be more engaging in the room, while a presentation optimized only for documentation can become painfully slow to present. The right choice depends on whether the file is expected to survive beyond the meeting.

Build the deck backward from the question someone will ask later

If you know the presentation will be emailed after the meeting, test it without speaking.

Open the file as if you have never seen it before. Give yourself a simple task: find the decision, find the key number, identify the recommendation, or explain why the proposal was approved.

If you cannot do that quickly, the problem probably isn't the template.

It may be the structure.

One useful approach is to write the slide headlines first and read them in sequence. If the headlines tell a coherent story by themselves, the deck has a much stronger backbone. If they read like a collection of topics—“Market,” “Competition,” “Financials,” “Next Steps”—you probably have a set of sections rather than an argument.

That logic is also central to the way consulting-style decks are structured: the argument is worked out before the visual polish, rather than expecting design to rescue unclear reasoning. How McKinsey Designs Their Presentation Slides

The real test is what survives after the presenter leaves

A presentation should not necessarily be judged only by what happens while it is on the screen.

Ask what remains when the meeting is over.

Can a colleague understand the main decision without calling you? Can a manager find the relevant number two weeks later? Can someone forward three slides to another department without having to write a separate explanation?

If the answer is yes, the presentation has become more than a meeting aid. It has become a working document.

That is a much better target than chasing an unsupported percentage about how many presentations supposedly get reread. The goal is not to make people reopen every deck. The goal is to make the deck valuable enough that, when they do reopen it, they immediately understand why it mattered.