A McKinsey style presentation reads fast and feels inevitable — a partner can flip through it and follow the argument without stopping. That is engineered, not accidental. This is how the whole deck is built, from storyline to section flow, so your presentation carries its case the way theirs do.
Most advice on "McKinsey style" fixes on the individual slide — the action title, the clean chart. That matters, and it is covered well elsewhere. But the thing that makes a McKinsey deck feel like a McKinsey deck is one level up: the whole presentation is a single argument, and every slide is a sentence in it. Get the deck-level logic right and the pages almost design themselves.
The short version: a McKinsey style presentation leads with the answer, groups its reasons beneath, and orders the slides so the sequence of titles alone tells the story. Everything below builds toward that.
What "McKinsey style" means at the deck level
At the page level, "McKinsey style" means one claim per slide. At the deck level, it means the deck is a pyramid: a single governing recommendation at the top, a handful of supporting arguments beneath it, and the evidence beneath those. The reader can stop at any depth — the executive summary, the section headers, or the full analysis — and the story still holds.
That is the opposite of the default deck, which is organised by workstream: "here is the market, here is the competition, here is finance, here are some recommendations." A workstream deck is a report. A McKinsey style presentation is an argument that happens to draw on those workstreams.
Start with the storyline, not the slides
Experienced consultants do not open PowerPoint and start designing. They write the storyline first, usually as a ghost deck or dot-dash outline — each page reduced to an action title and a one-line sketch of the exhibit that will support it. No formatting, no charts, just the logic as a sequence of assertions.
The reason is economics. It is far cheaper to move an argument when it is one line of text than when it is a formatted chart with a tuned layout. You pressure-test the whole story at the title level, get someone senior to sign off on the logic, and only then build. Skipping this step is how teams end up rebuilding a beautiful deck at 2am because the argument never worked.
Write your titles as a list first. Read them top to bottom. If that list of sentences tells a coherent story on its own, you have a deck. If it reads as a set of topics, you have a table of contents, and no amount of design will fix it.
The Pyramid Principle runs the whole deck
Barbara Minto's Pyramid Principle is the backbone here. State the answer first, group the reasons beneath it, and make each level support the one above. Applied to a full presentation, it produces a predictable, powerful shape:
- The governing thought — your single recommendation — leads the deck, on the executive summary.
- Three or four supporting arguments each become a section of the deck.
- Within each section, the slides prove that section's argument and nothing else.
MECE — mutually exclusive, collectively exhaustive — is what keeps the structure honest. Your supporting sections should not overlap and should not leave an obvious gap. If your three sections are "cost pressure," "supplier concentration," and "raw materials," a partner will spot in seconds that two overlap and something (labour, logistics) is missing. Holes in the logic are more visible than flaws in the data.
The executive summary carries the deck
In a McKinsey style presentation, the executive summary is not a warm-up. It is the whole argument in miniature: the recommendation, why it matters now, the three reasons it holds, and the decision you want. A senior reader should be able to read only that page and know what you think and what you are asking for.
Everything after it is defence. The market section exists to support a claim the summary already made; the finance section quantifies it; the risk section pre-empts the objection. If a slide does not advance the summary's argument, it belongs in the appendix, not the main line.
Section flow: governing thoughts, not labels
Between sections, use dividers that state the section's claim, not its topic. "Competitive dynamics" is a label. "The market is consolidating faster than the plan assumes" is a governing thought — it tells the reader what the coming slides will prove. When every divider makes an assertion, the deck reads as a chain of arguments rather than a filing system.
The test for the whole presentation is the same as for a single slide, scaled up: read only the executive summary and the section dividers. If that skeleton is a complete, persuasive argument, the deck is built correctly. If it is a list of subjects, the story is still hiding in the analysis.
The look is the easy part
Once the logic is right, the visual grammar is mostly restraint, applied consistently across every slide:
- One chart, one message, matched to the claim — a line for trend, a waterfall for contribution, a simple bar for comparison.
- A muted palette with one accent, used only to highlight the number that matters. Colour is a pointer, not decoration.
- Data ink over chartjunk — no 3D, no heavy gridlines, no drop shadows.
- A source line on every exhibit, and a short takeaway callout that restates the "so what."
The reason real McKinsey decks look calm is that someone removed everything that was not load-bearing. Consistency across the deck — same type sizes, same margins, same chart conventions — does more for the "premium" feel than any single beautiful slide.
Building one without an MBB team
The logic is yours to do; no tool decides your storyline. But turning a signed-off outline into clean, consistent, editable pages is exactly the production work that should not eat your evening. AutoPresent generates a fully editable PowerPoint deck from a prompt or an uploaded document — a memo, a model, a Word draft — and lays it out with action-title placeholders, a restrained palette, and chart types matched to the point.
The output is native PowerPoint, so you rework a title, swap a chart, or rebrand to the client's colours in one step, exactly as you would any deck. It clears the blank page and the fiddly formatting so your hours go to the argument, which is the only part a partner actually grades. For teams producing this every week, the pricing is built to make that trade obvious.
The takeaway
A McKinsey style presentation is not a template or a colour scheme. It is a pyramid: one governing recommendation, a few MECE arguments as sections, evidence beneath each, and an executive summary that states the whole case on one page. Build the storyline first, keep the logic honest, and the polish follows — because a well-argued deck has nothing on it that does not belong.