Looking at McKinsey slide examples is more useful than admiring them. This walks through the recurring slide types that define the style — the action-title exhibit, the synthesis page, the MECE framework, the driver decomposition — and explains what each one is doing, so you can build your own.
People search for McKinsey slide examples hoping to copy a look. The look is the easy part: a lot of white space, one accent color, thin rules, restrained type. What actually makes a slide read like McKinsey is structural, and it does not photograph. It is the way each page states a conclusion and then earns it.
Below are the McKinsey slide examples worth studying, described by what they contain and why they work. Read them as blueprints, not screenshots. The value is in the pattern you can reuse, not the pixels.
Example 1: The action-title exhibit
This is the workhorse — the slide type that appears twenty times in a McKinsey deck. At the top, a full-sentence headline states the takeaway: "Volume growth stalled in 2026 as the two largest accounts cut order frequency." Below it, a single exhibit — one chart or one table — that proves exactly that claim. A thin source line sits in the footer.
Why it works: the headline is the message, and the chart is evidence for it, not the other way around. A reader who reads only the top line already knows the point. The exhibit is there for the skeptic who wants to check. Notice the discipline — one claim, one chart, nothing else competing for attention.
To build your own: write the headline as an arguable sentence first, then choose the single exhibit that demonstrates it. If you find yourself adding a second chart, you probably have a second slide.
Example 2: The synthesis (executive summary) page
Near the front sits the synthesis: the whole argument in miniature. A governing thought at the top states the recommendation. Beneath it, three grouped supporting points, each a full sentence carrying one piece of evidence. Often a one-line "so what" and a clear ask.
Why it works: it front-loads the answer. Following the Pyramid Principle, it leads with the conclusion and groups the reasons under it, so the reader can stop after one page and know what you think, why it matters, and what you want them to decide. The restraint — three points, not seven — is what signals the team has actually synthesized rather than dumped.
To build your own: draft the governing thought and three supporting points in plain text before you open PowerPoint. If they do not hold together as an argument on their own, the slide will not either.
Example 3: The MECE framework slide
This slide breaks a problem into parts that are mutually exclusive and collectively exhaustive — an issue tree, or a three- or four-box framework laid across the page. "Cost reduction has three levers: procurement, footprint, and productivity," with each lever opened up beneath.
Why it works: it demonstrates completeness. A skeptical executive scans for the option you skipped, and a genuine MECE structure leaves no gap to find. The framework also organizes everything that follows — the next several slides map one-to-one to the boxes.
To build your own: test every framework against the two MECE questions. Do any boxes overlap? Is anything important missing? If either fails, the structure is not yet right, and no formatting will hide it.
Example 4: The driver decomposition
Here a top-line number is broken into the levers beneath it, often as a tree or a waterfall. Revenue splits into customers times average revenue per customer; average revenue splits into price and volume. Or a bridge shows what moved EBITDA from last year to this one, bar by bar.
Why it works: it makes the arithmetic visible and locates where value sits. The recommendation usually falls straight out of it — the one lever that, moved realistically, changes the outcome most. The action title names that finding: "Price, not volume, drove the entire margin gain."
To build your own: make the math legible so a reader can trace the boxes to the total, then add the "so what" in the headline. A decomposition with no conclusion is a calculation, not a slide.
Example 5: The recommendation and next-steps page
The deck usually closes on a page that restates the recommendation and lays out what happens next — the decision required, the immediate actions, and who owns them. Sometimes a short roadmap; sometimes a clean list.
Why it works: it hands the meeting a direction instead of ending on analysis. A McKinsey deck is built to produce a decision, and this page makes the ask unmissable. It mirrors the synthesis page, closing the loop the summary opened.
To build your own: make the ask specific and time-bound. "Approve the pilot budget this quarter" beats "Consider next steps."
What the examples share
Across every one of these McKinsey slide examples, the same rules hold:
- Every headline is a full-sentence claim, never a topic label. Read top-to-top, the headlines tell the whole story.
- One idea per slide. Density is not the same as rigor.
- Exhibits serve the claim. The chart proves the headline; it is not there for decoration.
- Source lines on every exhibit. Small, in the footer — the number can be traced.
- Restraint. One accent color, consistent type, real white space. The polish is in what is left off.
Copy those patterns and your slides will read like the examples. Copy only the color palette and they will not.
How AutoPresent helps
The structure — the action title, the MECE split, the "so what" — is judgment you bring. The formatting that makes it look like the examples is repeatable, and that is where a tool earns its keep.
AutoPresent generates fully editable PowerPoint in a restrained, board-appropriate style, so you can draft a slide or a full deck from a prompt or a source document with headline slots already in place, then rewrite each into the exact claim your analysis supports. Because it is native PowerPoint, you edit exhibits, alignment, and titles like any other file, and the theme switcher rebrands to client colors in one step. There is a free tier and paid plans from $25 a month if you want to build a real slide with it.
The tool will lay out the exhibit cleanly. It will not decide your action title or check your framework for gaps — that judgment stays with you, which is exactly where it belongs.
The takeaway
The best way to use McKinsey slide examples is to reverse-engineer the pattern, not the palette. Each recurring type — the action-title exhibit, the synthesis page, the MECE framework, the driver decomposition, the recommendation page — does a specific job, and each earns its conclusion instead of asserting it. Learn what each one is doing and you can build slides that read like the examples, on your own content, under your own deadline.