The One Question Every Slide Must Answer Before You Design It
A presentation is not a document with an audience. It's a document for a specific audience. The distinction sounds semantic. It isn't.
The first category — a document with an audience — is designed around its own content. The structure follows the logic of the information. Sections appear in the order they make sense to the person who built them. The vocabulary belongs to the subject matter. The visual choices are made on aesthetic grounds. This describes most presentations I've seen.
The second category — a document for a specific audience — is designed around the people in the room. The structure follows the journey those specific people need to take to reach the intended conclusion. The sections appear in the order that serves their understanding. The vocabulary belongs to their world. The visual choices are made to support the emotional arc the presenter needs them to experience.
These are different objects entirely. And the difference begins, not in the design phase, not even in the content phase, but before a single slide is touched.
The pre-design brief
Before I start work on any presentation of meaningful complexity, I do something that surprises a lot of new clients: I spend the first conversation not talking about the deck at all. I ask them to describe the room.
Not abstractly — specifically. Who will be there? What are their roles? What decisions are they authorized to make? What decisions do they want to avoid making? What do they already believe going in, and what do they resist? What have they heard before that sounded like this and disappointed them? What's the best version of how this presentation could go, and what does the room look like in that version?
Most clients have never been asked these questions in the context of a presentation project. They've been asked about deliverables, timelines, formats, and content. The questions about the audience — real, specific, behavioral questions — are treated as common sense background that doesn't need to be made explicit.
But common sense that hasn't been made explicit isn't common sense. It's assumptions.
What I learned designing for Philips
The Philips Healthcare engagement was one of the more technically complex projects I've worked on. The presentations were designed to be used in Philips' flagship experience centers in Best and Cambridge — physical environments where their most advanced medical imaging and workflow technology was installed and operational. The audience would literally be standing in front of the technology during the presentation.
The Sales Enablement Managers — the people delivering these presentations — were dealing with a specific audience challenge: the people walking into those experience centers were not homogeneous. A hospital CEO and a head of radiology would visit the same room and both need to leave with something meaningful, but they were looking for completely different things. The CEO was evaluating strategic fit and total cost. The radiologist was evaluating workflow impact and diagnostic capability. The same slide that served one would alienate the other.
We designed the deck as a modular system — entry points for different audience types, sections that could be re-ordered depending on who was in the room. But the more important work was building the Sales Enablement Managers' understanding of their audience before the meeting started. The deck had a built-in pre-meeting framework: four questions to ask any prospect before the session began, which would determine the entry point and emphasis for that specific conversation.
It sounds obvious in retrospect. It required deliberate design to make possible. And it required the pre-project understanding that "the audience" was not a single entity but a variable that determined everything else.
The four things you need to know about your audience
After working with audiences across health, finance, consumer, technology, entertainment, and education, I've landed on four categories of knowledge that actually change how a presentation is built.
The first is decision authority. Who in the room can say yes? Who can say no? Who can influence without officially deciding? Knowing this tells you where to direct your most critical argument. If the decision-maker is a CFO who won't speak until the third slide, you're designing the first two slides to earn the CFO's attention — not to inform the room.
The second is existing belief. What does the audience already believe about your topic, your company, or the problem you're addressing? If they're skeptical, you need to acknowledge that skepticism explicitly rather than presenting as if it doesn't exist. If they're enthusiastic, you don't need to sell them — you need to organize the enthusiasm into commitment. Different beliefs require completely different structural responses.
The third is vocabulary. Every professional community has its own language. Presenting data architecture to a CMO using engineering vocabulary loses the room. Presenting campaign metrics to a CTO using marketing vocabulary does the same. The vocabulary of the audience is not just a courtesy — it's a trust signal. Using their words correctly tells them you understand their world.
The fourth is what I think of as the unspoken question. Every room has at least one thing people are thinking and nobody is saying. Sometimes it's skepticism ("we've heard this before"). Sometimes it's a political reality ("this threatens another team's budget"). Sometimes it's a personal concern ("if this succeeds, does my role change?"). The unspoken question doesn't disappear because you ignore it. If you don't address it, the audience addresses it internally while you're still speaking.
StarzPlay: designing for a skeptical but eager audience
Special Forces Insights brought me in to design a research and debrief presentation for StarzPlay UK. The context was specific: an American streaming platform trying to understand British consumer behavior, in a market where local insight was a genuine competitive advantage.
The internal client — the StarzPlay leadership team — was eager for insight but also quietly nervous about whether an American platform could really understand the British market well enough to compete. That was the unspoken question in the room.
We addressed it at the top of the deck, not by reassuring the audience that we understood, but by demonstrating it. The opening section walked through three pieces of British cultural intelligence — around TV viewing habits, the relationship between public broadcasting and subscription services, and the specific way British consumers talk about entertainment choices — that immediately established that the research team had done genuine, locally-grounded work.
The audience's guard came down within the first ten minutes. Not because we told them to trust us. Because we showed them evidence of something true that only real engagement with the market could have produced.
That's what knowing your audience makes possible. Not better slides about your content — a different relationship with the room from the moment the presentation begins.
The brief I give every client before design begins
There are six questions I ask every client at the start of a presentation project. I'd encourage anyone building a significant presentation to answer them before touching a slide.
Who, specifically, is in the room? Name them if you can. Describe their role and what they're accountable for.
What do they already believe about this topic? What are they hoping to hear? What are they wary of?
What would success look like — not for the presentation, but for the relationship that follows it?
What's the one thing you cannot afford to have them leave believing?
What's the unspoken question that everyone is thinking but nobody will ask directly?
If you could only get one thing across in this entire presentation, what would it be?
The answers to these six questions will tell you more about how to design the deck than any content brief you could receive. Because the content is in service of the audience. Not the other way around.