What makes a good slide deck
How to build a slide deck that carries a clear argument: the answer first, titles that speak, evidence on every slide.
A slide deck often carries your case to a customer: in a meeting, or sent ahead by email. This guide teaches the method the large consulting firms use. The method is not about decoration. It is a way to build an argument that a busy reader can check and accept.
A deck is one way to answer question three of the marketing tutorial: How will we deliver/present it? The other four questions shape the deck too. The last section shows how.
A deck moves a decision
A good deck asks for something. Before you open the slide program, complete this sentence: "After this presentation, we want [who] to [do what]." Choose the smallest honest next step.
The last slide states that ask, plainly. A deck with no ask is a brochure.
Put the answer first
Consultants build a deck like a pyramid. They call this the pyramid principle: the main message at the top, in one sentence. Under it, two to four arguments. Under each argument, the evidence.
State the main message early, on the first content slide. Do not save it for the end. The reader should never wonder where you are going.
Then check the arguments as a group. Together they should cover the whole case, and they should not repeat each other. No gaps, no overlaps.
flowchart TD
A["The main message: one sentence"] --> B["Argument 1"]
A --> C["Argument 2"]
A --> D["Argument 3"]
B --> E["Evidence, with source"]
C --> F["Evidence, with source"]
D --> G["Evidence, with source"]The answer sits at the top. Each layer answers "why?" for the layer above it. Together the arguments cover the case: no gaps, no overlaps.
Open so the reader recognizes themselves
Before the answer, give a short opening. First the situation: what is true today. Then the complication: what changed, or what hurts. Then the question this raises. Then your answer. Four sentences can be enough.
A reader accepts an answer only after they recognize the situation as their own.
Slide titles carry the argument
A slide title is a full claim, not a label.
Weak: "Q3 revenue". Strong: "Service revenue grew 40% in the EU".
The test: read only the titles, in order. They should form the complete argument on their own. If they do not, fix the titles before you touch anything else.
Write the titles before the slides
Write the full list of titles first, on one page. Read it as an argument. Move, merge and cut until the line of thought holds. Only then build the slides.
A weak argument is cheap to fix while it is ten sentences on one page. It is expensive to fix after it has become thirty slides.
The same rule applies to review. When you review a deck, review the titles first. Do not comment on the layout of a slide that should not exist.
flowchart TD
A["Write the titles first"] --> B{"Titles alone carry the argument?"}
B -->|"No"| A
B -->|"Yes"| C["Build the slides"]
C --> D["One message per slide"]
D --> E["Evidence and source on every slide"]
E --> F["Move the rest to the appendix"]Fix the argument while it is a list of ten sentences. Then spend your effort on the slides.
One message per slide
The title states the message. Everything on the slide supports it. Everything else is removed, or moved to the appendix.
Ask of every element on the slide: what does this add to the message? If the answer is nothing, it costs attention and gives nothing back.
Evidence on every slide
Every claim needs its evidence on the same slide: the number, the test report, the named customer, the date. Write the source under every chart and every table.
Evidence changes what you may say. A claim with visible evidence can be direct. A claim without evidence has to stay modest, or it costs trust. Be modest in the ask. Be direct in the evidence.
Charts that say what they mean
A chart title says what the data means, not what the axes are.
Weak: "Sales 2023–2026". Strong: "Sales doubled in three years".
One chart, one message. Choose the chart form from the point you make: shares of a whole, a change over time, a comparison between items. Remove decoration: no 3D, few gridlines, no background images. Use a table when the reader needs to look up values. Use a chart when you make a point.
Keep the main line short
Ten to fifteen slides carry the argument. Everything else goes to the appendix: present in the room, but not presented.
Put a one-slide summary at the front, with the answer first. A busy reader should get the complete argument from that summary and the titles in half a minute. Many decks are only ever read that way.
Decide early which kind of deck you are making. A deck you present live has sparse slides, because you are the voice. A deck you send by email must stand alone, with fuller titles and short notes.
Design quietly
One or two typefaces. The same layout from slide to slide. Generous empty space. Numbers where words would be vague.
The design should not draw attention. A calm, consistent deck signals care, and the reader assumes the analysis received the same care.
A worked example
Five titles that carry a whole argument. The example is an equipment maker addressing buyers in the EU:
- Your buyers ask for safety evidence before they ask for price.
- Most vendors cannot show that evidence when asked.
- We publish it: the test report, the technical file, the EU representative.
- Ask every vendor for the same three documents.
- Compare the answers. Then let us talk about what you find.
Read the titles in order: they form the complete argument, and the last one is the ask.
A deck is the five questions in slide form
- Who is the target audience? This decides what counts as evidence in the room. An engineer wants the test data. A buyer wants the terms and the track record.
- What is the message? The one sentence at the top of the pyramid, and the ask on the final slide.
- How will we deliver/present it? A deck is a channel choice. Presented live or sent ahead: decide, and build accordingly.
- What is the expected result? The named next step you ask for on the last slide.
- How do we know/measure success? Decide before the meeting what a yes looks like, and when you expect it.
A good deck is the five questions, answered in order, in slide form. The method is not about beautiful slides. It is about respect for the reader's time, and evidence for every claim.