McKinsey slides look simple and read fast, but that simplicity is engineered. This is how the individual page is built — the action title, the single idea, the MECE support — so your own slides carry an argument the way theirs do.
Most people who ask how to make "McKinsey slides" are really asking two different things. Some want the look: the clean charts, the muted palette, the confident typography. Others want the logic: why a partner can flip through a deck at speed and still follow the reasoning. The look is easy to copy and the logic is the part that actually matters, so this article is mostly about the logic — with enough on the visual grammar to make your pages resemble the real thing.
The short version: a McKinsey-style slide makes one claim, states it in the title, and spends the body proving that claim and nothing else. Everything below follows from that.
The action title carries the slide
The single most important habit is writing the title as a sentence that makes a claim, not a label that names a topic. "Revenue by segment" is a label. "Enterprise now drives 60% of revenue but less than half of new logos" is an action title — it takes a position the reader can agree or disagree with.
The test is simple. Read only the titles, top to bottom, and skip every chart. If the story still holds together, your titles are doing their job. If you get a list of nouns — "Market overview," "Competitive landscape," "Financials" — you have a table of contents pretending to be an argument.
Action titles also force you to know what each slide is for. A page you cannot summarize in one assertion is a page that has not earned its place in the deck. Cut it or split it.
One idea per slide
A McKinsey slide answers one question. When a page tries to carry three ideas, the reader has to do the work of separating them, and in a board or IC meeting they will not bother — they will lose the thread and start reading email.
Practically, this means the body of the slide exists only to support the title's claim. If the title says enterprise drives revenue but not new logos, the chart shows exactly that split, and any data that does not bear on it comes off the page. The instinct to include everything you found is the enemy here. The appendix is where your homework goes; the slide is where your conclusion goes.
MECE support beneath the claim
MECE — mutually exclusive, collectively exhaustive — is the discipline that keeps the support honest. When you break a claim into reasons, the categories should not overlap (mutually exclusive) and should not leave an obvious gap (collectively exhaustive).
Say your title is "Three structural forces are compressing margin." If your three supporting points are "rising input costs," "supplier concentration," and "raw materials," you have failed MECE twice: supplier concentration and raw materials overlap, and you have probably missed labor or logistics entirely. A partner will spot the gap in seconds, because a hole in the logic is more visible than a flaw in the data.
Three supporting points is the working number. Two feels thin; five means you have stopped synthesizing and started listing. If you genuinely have seven items, they usually collapse into three groups — find the groups.
Horizontal and vertical logic
Good decks read two ways. Vertical logic is within a slide: the title makes a claim, the body proves it. Horizontal logic is across slides: each title advances the argument so the sequence of titles is itself a coherent storyline.
This is where the Pyramid Principle, Barbara Minto's framework and the backbone of MBB communication, comes in. Lead with the answer, group the reasons beneath it, and make sure each level supports the one above. A deck built this way can be read at three depths — titles only, titles plus key exhibits, or in full — and makes sense at every depth. That is why partners can review at speed.
The visual grammar of McKinsey slides
Once the logic is right, the look is mostly restraint:
- One chart, one message. Match the chart to the claim. Trend over time is a line; contribution to a total is a stacked bar or waterfall; comparison across categories is a simple bar. Do not use a pie chart for six slices.
- Muted palette, one accent. A neutral base (greys, a single brand blue) with one accent color used only to highlight the number that matters. Color is a pointer, not decoration.
- Data ink over chartjunk. No 3D, no heavy gridlines, no drop shadows. Label the point you want read; delete the rest.
- A source line and a takeaway. Every exhibit cites its source at the bottom and, ideally, restates the "so what" in a short callout so the reader cannot miss it.
None of this is hard. It is just disciplined. The reason real McKinsey slides look calm is that someone removed everything that was not load-bearing.
The ghost deck comes first
Experienced consultants do not open PowerPoint and start designing. They write the storyline first — often as a "ghost deck" or dot-dash outline, where each page is just an action title and a rough sketch of the exhibit that will support it. You pressure-test the argument at the title level, get a partner to sign off on the logic, and only then build the actual slides.
This ordering saves enormous rework. It is far cheaper to move an argument around when it is one line of text than when it is a fully formatted chart with a hand-tuned layout.
How AutoPresent helps
Structure is thinking, and no tool does your thinking for you. But once you have the storyline, turning it into clean, editable pages is exactly the kind of work that should not eat your evening. AutoPresent generates a fully editable PowerPoint deck from a prompt or an uploaded document — a diligence memo, a model, a Word draft — and lays it out with action-title placeholders, a restrained palette, and chart types that match the point you are making.
The output is native PowerPoint, so you edit it the way you edit any deck: rework a title, swap a chart, rebrand to the client's colors in one step. It gets you past the blank page and the fiddly formatting so your time goes to the argument, which is the only part a partner is actually grading. For teams doing this every week, the pricing is built to make that trade obvious. You keep the judgment; the tool absorbs the production.
The takeaway
A McKinsey slide is not a design trick. It is one claim, stated in the title, proven by MECE support, set inside a storyline that holds together read top to bottom. Get the action titles right and the horizontal logic clean, and the visual polish is almost automatic — because there is nothing left on the page that does not belong there.