A McKinsey deck is not a set of good-looking slides. It is a single argument spread across pages, built so a reader can follow the logic from the headlines alone. This is how the structure works and how to build one on your own material.
Ask what makes a McKinsey deck a McKinsey deck and most people point to the aesthetic — the white space, the blue accent, the clean charts. That is the surface. What actually distinguishes the firm's work is that the deck is engineered as a top-down argument. Every page has a job, every headline is a claim, and the claims connect into one line of reasoning that leads to a decision.
Get the structure right and a plain deck will read as consulting-grade. Get it wrong and the most beautiful slides in the world will still feel like a pile of exhibits. This piece is about the structure.
Start with the storyline, not the slides
The single biggest difference between a McKinsey deck and an ordinary one is that the argument is designed before any slide is built. Consultants call this the storyline: the ordered sequence of one-sentence takeaways that, read together, make the case.
A common way to draft it is a "ghost deck" — a full skeleton where each page is just its action title and a rough sketch of the exhibit that will prove it, before any real analysis is formatted. You write the headlines, arrange them until the logic flows, and only then build the pages. If the story does not hold as a list of sentences, no amount of formatting will fix it later.
This is worth doing on paper or in a plain outline first. Building slides before the storyline is settled is how decks balloon to eighty pages and still fail to make a point.
Lead with the answer (the Pyramid Principle)
McKinsey decks are top-down. They open with the recommendation and then support it, rather than walking the reader through the analysis toward a reveal at the end. This is Barbara Minto's Pyramid Principle: state the governing thought first, group the supporting arguments beneath it, and support each of those in turn.
In practice, that means an executive summary near the front states the answer, the "so what," three supporting points, and the ask. Everything after it is evidence for one of those points. A reader can stop after the summary and know your conclusion; they read on only for proof. The methodology and the detailed tables go to the appendix, where they are available but not in the way.
Make every headline an action title
Inside the deck, each content slide carries a full-sentence headline that states the takeaway of that page — an action title, not a topic label. "Revenue grew 12%, entirely on price" rather than "Revenue Overview."
The action titles are load-bearing. Read in sequence, top to top, they should tell the complete story without the reader opening a single exhibit. Consultants call this the horizontal logic, and it is the real test of a McKinsey deck: flip through reading only the headlines, and check that they form a coherent argument that arrives at the recommendation. If the sequence jumps or repeats, the deck's logic is broken no matter how good the individual slides look.
Each slide then has its own vertical logic: the exhibit below the headline proves that specific claim, and nothing on the page competes with it. One idea per slide. If a page makes two points, it is two pages.
Structure the flow
A typical McKinsey-style engagement deck moves in a predictable arc:
- Cover — neutral engagement title, client name, date, confidentiality line. Restrained.
- Executive summary / synthesis — the whole argument in miniature: answer, so-what, three points, ask.
- Context and framing — the question, the scope, often a MECE framework that organizes what follows.
- The body — one section per supporting point, each section a short run of action-title slides that build that point.
- Recommendation and next steps — restate the ask, specific and time-bound, with owners and a rough sequence.
- Appendix — methodology, detailed models, sensitivity tables. Everything the body pointed to but did not need to show.
The body sections map one-to-one onto the supporting points in the summary. That correspondence is what makes the deck feel inevitable rather than assembled.
Hold the house style
Once the logic is right, the visual discipline finishes the job. The McKinsey look is mostly restraint:
- One accent color, used sparingly, on a neutral base.
- One typeface, two or three sizes. Consistent, quiet.
- Real white space. Margins signal confidence; crammed slides read as anxious.
- Source lines in a small footer on every exhibit.
- Clean, single exhibits. One chart per slide, labeled directly, no chartjunk.
None of this is expensive to do; all of it is easy to skip under deadline. The polish is in what you leave off.
Common mistakes
- Building slides before the storyline. The deck grows without an argument. Draft the headlines first.
- Topic titles instead of claims. "Market Context" tells the reader nothing. Make every headline arguable.
- Broken horizontal logic. Headlines that do not connect when read in sequence. Read them top-to-top and fix the jumps.
- Burying the recommendation. Saving the answer for slide 40 is the opposite of the pyramid. Lead with it.
- Appendix material in the body. If a reader does not need it to follow the argument, move it back.
How AutoPresent helps
The storyline and the action titles are yours — no tool decides the argument. Building the deck around them, cleanly and consistently across forty pages, is where the hours go, and where a tool helps.
AutoPresent produces fully editable PowerPoint, so you can turn an outline or a source document into a first-draft deck — a cover, an executive summary, and body slides with headline slots in place — and then rewrite the action titles and reorder the flow until the horizontal logic holds. It applies a restrained, board-appropriate style by default, and the theme switcher rebrands to a client's colors in one step. Because it is native PowerPoint, a partner can redline it in Track Changes like any other file. There is a free tier and paid plans from $25 a month to try it on a live engagement.
The tool assembles and formats the pages. It does not write your storyline or decide your recommendation — the argument stays yours, which is the only part that was ever the real work.
The takeaway
A McKinsey deck is an argument first and a set of slides second. Draft the storyline before you build anything, lead with the answer, make every headline a claim that connects to the next, and hold the visual restraint that lets the logic show. Do that and the deck will read like the firm's work — not because it looks like it, but because it is built like it.