The keynote had forty-five slides. Each slide was justified. I could tell you precisely why each one was there, what argument it was making, what it was contributing to the overall narrative. The content was solid. The research behind it was real. The case I was building was coherent.
It was also, when I stepped back and watched a run-through on recording, genuinely exhausting to watch.
Not because of the content. Because of the density. Forty-five slides in forty-five minutes means a new slide every sixty seconds. A new slide every sixty seconds means the audience never settles into anything. Every time they’ve begun to process one piece of information, a new piece arrives. Every time they’ve started to feel the weight of an idea, the visual field changes and another idea demands attention.
The audience was theoretically getting everything I’d prepared. What they were actually experiencing was information at a rate that exceeded their processing capacity, delivered in a format that prevented any individual idea from landing with full force.
The content was fine. The architecture was wrong.
What Architecture Means
I want to be precise about the distinction, because it’s not intuitive.
Content is what you’re saying: the arguments, the evidence, the stories, the concepts. In my case, the content was well-developed and accurate. I’d done real work to understand the topic, and the presentation of that understanding was genuinely sound.
Architecture is how the content is organized, sequenced, and housed. It’s the structure that the content moves through. Two presentations with identical content but different architecture produce completely different audience experiences.
Most people who prepare presentations — and I was one of them for years — think primarily about content. Get the ideas right. Make sure the arguments are sound. Ensure the research is accurate. These are all necessary and not sufficient.
The architecture determines whether the content arrives.
The Reduction Process
When I decided to reduce the keynote, I started with a principle I’d developed from studying retention research: what is the one thing I want someone to remember a week from now? Everything else in the presentation is scaffolding — necessary for building the central idea during the talk, but not meant to be retained independently.
With that principle, I looked at the forty-five slides and asked, for each one: is this the central thing, or is this scaffolding?
Most of them were scaffolding. Contextual material that helped the central ideas make sense but that didn’t need to exist as a standalone slide. Supporting evidence that could be verbalized rather than visualized — a single sentence while a more compelling image held the visual field. Transition slides that existed because I didn’t know how to move from one idea to another without announcing the transition explicitly.
The reductions fell into categories:
Slides that were explaining the same idea twice — once in text, once in image form, but adding no new information in either layer. These became one slide where the image did the work and the text disappeared.
Slides that were providing context I could provide verbally, while the visual stayed with something more meaningful. These became zero slides — the context went into the spoken layer, and the audience’s visual attention stayed on whatever was already there.
Slides that existed because I was anxious about moving past an idea too quickly. These were the most revealing category: pure security blanket material, providing comfort to the presenter without providing anything to the audience.
After the audit, I had a deck of eighteen slides — each doing specific, irreplaceable work that no other slide was doing.
The Counterintuitive Effect
Here’s what I expected when I ran the reduced version: that the talk would feel sparse, that important material would feel missing, that the audience would be getting less.
Here’s what actually happened: the talk felt more substantial, not less. The ideas that previously rushed past the audience now had room to exist. The silence around an idea — the moment of “here is this thing, let it be what it is before the next thing arrives” — was possible with eighteen slides and impossible with forty-five.
The audience wasn’t getting less. They were getting the same content at a rate they could actually absorb. They were getting the architecture that let the content do what the content was capable of doing.
The most common feedback after that restructured version: “It was surprisingly simple” — which, translated from audience-speak, means the ideas were clear. And “I’m still thinking about the point you made about X” — which means something survived past the end of the event.
Neither of those responses had appeared with the forty-five-slide version.
What Made the Cut and Why
The eighteen slides that survived the reduction share a quality: each one does something that the spoken content can’t do alone.
A visual that makes a spatial or relational point that would be confusing to describe verbally. An image that carries emotional weight the words would flatten into information. A data visualization that makes a comparison viscerally legible in seconds rather than taking a minute to describe numerically.
What disappeared: slides that were primarily text repeating what I was saying. Slides that were bullets summarizing a point that was better experienced as a story. Slides that were transitional — “now we’re going to look at…” type content that a gesture and a pause could communicate more elegantly.
The slide count turned out to be a proxy for a more important question: is each visual element earning its interruption of the audience’s focus? Every time a new slide appears, the audience’s attention briefly redirects. That redirection is a cost. The slide has to be worth the cost.
With forty-five slides in forty-five minutes, I was asking for a redirection every sixty seconds regardless of whether any given slide justified it. With eighteen slides, I was only asking for the redirections that had clear value.
The Lesson That Transfers
This experience reshaped how I think about density in any performance context — not just keynotes. Magic sets included.
Effects and presentations have a natural density that serves the audience and a density that exceeds what the audience can process. The comfortable feeling of “I have enough material” often masks the architectural problem of “I have more material than I have structure for.”
Reduction — done with a clear principle about what you’re optimizing for — doesn’t diminish content. It clarifies it. What remains is what was always the substance; what’s removed was the accumulation around the substance.
Same content. Half the slides. Twice the impact.
The architecture, not the content, was the variable.