Presentation vs. Report: Why Your Deck Can’t Be Both

You can’t run a race in swim fins.

Swim fins are excellent equipment. In the water, they make you faster. On a running track, they make you fall.

Many presentation problems are equipment problems.

A team presents a report: full sentences, dense tables, charts in 10-point type. The data is solid. But the presenter ends up reading the slides aloud while the audience reads ahead, and soon nobody is listening to anyone. That’s fins on the track.

Then it happens the other way. A presentation that worked well in the room gets forwarded to a director who wasn’t there. She opens slide 4: a photo of an empty chair and three words. No context. No presenter. She closes the file. That’s running shoes in the pool.

In both cases the content was fine. It was built for a different event.

Presentations and reports look alike: both are files, and both often have slides. But they do different jobs.

What is a presentation?

A presentation is a story told by a person. The slides are only part of it.

The presenter brings what a file can’t: voice, timing, the pause before the important number, the answer to the question someone was about to ask. The slides do what a person can’t: show the picture, make the idea visible, give the room something to remember.

That’s why good presentation slide have way less copy. One idea at a time. Fewer words. An image that makes people feel something. Memory research is consistent on this point: emotional material is remembered more deeply than neutral material. In a presentation, what the audience feels is what they keep.

A presentation needs a presenter. Without one, it’s a set of clues.

What is a report?

A report is information designed to work when nobody is there to explain it.

It has to answer every question by itself. That means complete sentences, clear structure, and data with enough context to be understood on its own. A good report lets someone scan it in five minutes and understand it in ten, at their desk, at their own pace.

Reports are usually leave-behinds. They’re sent before a meeting so people arrive prepared, or after it so the decision has something to stand on.

A report is built to be read, not performed.

Presentation vs. report at a glance

The deck that tries to be both

Nancy Duarte, author of Resonate, gave slide-based documents meant for reading a name: slidedocs. They’re a valid format. The problem is the file that tries to be a slidedoc and a stage presentation at the same time.

It’s too crowded to present, so the presenter ends up reading the slides aloud while the audience reads ahead. It’s too fragmented to read, so the person who opens it later finds bullet points that only made sense with someone talking over them.

It’s fins and running shoes at the same time. You won’t swim well, and you won’t run at all.

How to choose: one question

Before the first slide, ask: will someone be standing next to this?

• Yes. Design a presentation. Tell a story. Leave space for the person.

• No. Design a report. Let the page do the talking.

• Both. Make two files: a presentation for the room and a report for the inbox. It’s more work. It’s also the only version that works twice.

Triathletes don’t swim in running shoes. They change gear between legs. Your story deserves the same.

Why we design both

At Lupa, we design presentations and reports as separate pieces, because they do separate jobs. Clients usually ask us for one deck. Often, what they need is two: one built to be felt in the room, and one built to be understood long after the meeting ends.

Before your next meeting, look down. Fins or running shoes?