Back to Blog
Design Insights

How to Structure a McKinsey Slides Deck

How to structure a McKinsey slides deck end to end: the storyline, executive summary, section flow, and appendix, with a worked example.

6 min readBy Kevin F.
Reviewed by AutoPresent's presentation experts — former MBB consultants
How to Structure a McKinsey Slides Deck

A single polished slide is not the hard part. This is how a full McKinsey slides deck is structured end to end — the storyline, the executive summary, the section flow, and the appendix — so forty pages read as one argument instead of a pile of exhibits.

If you have ever built a slide you were proud of and then watched it drown inside a deck that went nowhere, you already know the problem. Individual slides can be clean and the deck can still fail, because a deck is not a collection of good pages. It is one argument delivered across many pages, and the structure is what holds that argument together.

This is the level MBB teams obsess over. Below is how a consulting deck is put together as a whole, with a worked example you can adapt.

Start with the storyline, not the slides

Before anyone opens PowerPoint, the team writes the storyline — the sequence of claims that, in order, make the case. In practice this is a "ghost deck": one line per page stating the action title, with a rough note on the exhibit that will support it. No formatting, no charts, just the logic.

The reason is economic. It costs almost nothing to reorder an argument when each page is a single sentence. It costs an evening when each page is a finished chart. So you settle the story first, get a partner to sign off on the logic at the title level, and only then build.

A good storyline test: read the titles alone, top to bottom. If they tell a complete, persuasive story with no charts attached, the deck will work. If they read as a list of topics, no amount of design will save it.

The pyramid: answer first, support beneath

A McKinsey slides deck follows the Pyramid Principle — Barbara Minto's framework, and the backbone of consulting communication. You lead with the answer, then group the supporting arguments beneath it, and each argument is itself supported by evidence one level down.

This inverts the way most people naturally write, which is to walk through the analysis and arrive at a conclusion at the end. In a board or investment committee, that order fails: the senior reader wants the recommendation on page one and the proof on request. The pyramid gives them exactly that, and it lets the deck be read at three depths — executive summary only, plus section leads, or in full.

The standard shape of a McKinsey slides deck

Most consulting decks share the same skeleton:

  1. Executive summary / synthesis. One page, up front, stating the recommendation, why it matters now, three supporting reasons, and the ask. If the reader stops here, they should still know what you think and what you want them to do.
  2. Context and question. A short framing of the situation and the specific question the deck answers. Kept tight — the reader lived this problem; do not re-teach it to them.
  3. Body sections, one per supporting argument. Each section opens with its own claim and then proves it across a handful of slides. The section leads, read in order, should mirror the three supporting points from the executive summary.
  4. Implications and recommendation. What follows from the analysis, the specific decision requested, and the immediate next steps or timeline.
  5. Appendix. The methodology, sensitivity tables, detailed models, and backup exhibits. This is where the homework lives so the body can stay clean.

The discipline is that every body slide ladders up to a section claim, and every section claim ladders up to the executive summary. Nothing floats. If you cannot say which higher-level point a slide supports, it belongs in the appendix or in the bin.

A worked example

Say the engagement is whether a regional bank should exit its wealth-management arm. The numbers are illustrative; the structure is the point.

Executive summary (1 page): "Divest wealth management within 12 months and redeploy capital into commercial lending, where returns are structurally higher." So what: the unit consumes a fifth of capital for a tenth of profit and is losing share. Three reasons, plus the ask: approve a sale process this quarter.

Section 1 — "Wealth management is structurally disadvantaged." Three or four slides: subscale assets under management, cost-to-serve above peers, no realistic path to the scale required.

Section 2 — "Commercial lending is the stronger use of the same capital." Three or four slides: higher risk-adjusted return, existing relationships to cross-sell, capacity to absorb redeployed capital.

Section 3 — "A sale is achievable on acceptable terms." Two or three slides: comparable transactions, likely buyer pool, indicative range.

Recommendation and next steps: the decision, the timeline, and what needs approving now.

Appendix: the valuation model, the AUM cohort analysis, the peer benchmarking detail.

Notice the horizontal logic. The three section claims are exactly the three supporting points named on the executive summary. A partner can read five pages — the summary and three section leads — and follow the entire case.

Where decks go wrong

  • No governing thought. The deck reports findings but never says what to do. A deck without a recommendation is a research document, not a consulting product.
  • Sections that don't ladder up. Interesting analysis that supports no stated claim. It reads as "here is everything we looked at," which erodes trust in the parts that matter.
  • The summary is a table of contents. "This deck covers market, competition, and options" tells the reader nothing. State the answer.
  • The body carries the appendix's weight. Every methodological detail on the main path. Move it back; let the argument breathe.
  • Building before the storyline is signed off. The most expensive mistake — polishing pages that get cut when the logic finally gets scrutinized.

How AutoPresent helps

The storyline is yours to write; a tool cannot decide your argument. But once the logic is set, producing a consistent, board-appropriate deck across forty pages is exactly the grind worth automating. AutoPresent turns a prompt or an uploaded document into a full, editable PowerPoint deck — feed it your outline or a source memo and it drafts the sections, action-title placeholders, and exhibits in one coherent template rather than a set of mismatched pages.

Because the output is native PowerPoint, you keep full control: reorder sections, rewrite a title, rebrand to the client's palette in one step, and drop your real charts into the layouts. It handles the connective tissue and the formatting consistency that usually eats the last night before an IC meeting. For teams shipping decks weekly, the pricing is designed to make that time trade an easy call.

The takeaway

A McKinsey slides deck is one pyramid, not many good slides. Settle the storyline first, lead with the answer, make every section ladder up to the executive summary, and push the homework to the appendix. Do that and the deck will read as a single argument — which is the whole point of building one.


Related reading

Turn your next presentation into a board-ready deck.

Use AutoPresent to convert documents, notes, data, and rough ideas into polished, editable slides in minutes.

Try AutoPresent now