The Consulting Deck, Deconstructed: How McKinsey-Style Presentations Actually Work

By the Kinsy team · Published 27 July 2026

A consulting deck looks effortless from the outside and is anything but. Behind the plain charts sits a strict grammar — answer first, titles that argue, slides that prove — codified at McKinsey decades ago and barely changed since. None of it requires a consultant. Here is how the machine works, piece by piece, and how to build one yourself.

What makes a deck a consulting deck?

A consulting deck is a presentation built on the pyramid principle: it states its answer first, supports it with a small set of non-overlapping arguments, and gives every slide an action title — a full sentence that the body of the slide then proves. The approach was codified by Barbara Minto, who developed it at McKinsey and later published it as The Pyramid Principle, and it has been the firm's — and the industry's — house style ever since.

The logic is audience-shaped. Executives read conclusions first and evidence second, if at all; they will not sit through a methodology tour to find out what you recommend. So the McKinsey-style presentation inverts the way analysis actually happened. You spent months moving from data to insight; the deck runs the other way — recommendation on page one, reasoning beneath it, raw workings in the appendix. Consultants call the alternative the mystery novel: clues accumulating for forty slides towards a reveal. It reads as suspense to the author and as evasion to the client.

Action titles: the horizontal spine

The pyramid's slide-level expression is the action title. Every slide gets a headline that is a complete assertion — "Retail margins fund the expansion" — never a filing label like "Market overview". The standard test, applied in every consulting review, is to flip through the deck reading only the titles: in sequence they should read as a connected, self-sufficient argument, from situation to recommendation. That property is called horizontal logic, and teams check it before anything else, because a deck whose titles don't hold together cannot be rescued by its charts. We've unpacked the craft — with rewrites of common label titles — in our guide to writing action titles that carry the storyline.

Vertical logic: the title asserts, the slide proves

Horizontal logic runs across the deck; vertical logic runs down each slide. The title makes one claim, and everything below it exists to prove that claim — the exhibit, the annotations, the source line. A reader should be able to glance from headline to chart and verify the assertion without help. The discipline cuts both ways: if the chart doesn't support the title, the title is wrong; if something on the slide doesn't serve the title, it comes off — to the appendix, or to nowhere. One claim, one exhibit, one slide is the default, and every element on it has to survive the reviewer's standing question: so what?

The ghost deck: storyboard before you design

The least visible convention is the one that saves the most time. Before any real slide is built — often before the analysis is finished — consulting teams draft a ghost deck (also called a storyboard or dummy deck): the full set of action titles, each with a rough sketch of the exhibit that would prove it. "Chart showing costs rising faster than revenue" is enough; nobody draws real axes. The point is that a storyline is cheap to rearrange on paper and expensive to rearrange in a formatted deck, so the argument gets reviewed — and torn apart, and reordered — while it is still boxes and pencil. When a partner finally sees polished pages, the structure has already survived scrutiny; the polish is the last step, not the first.

The standard grammar: summary, SCR, MECE, appendix

Around the pyramid sits a small set of house conventions you will find in nearly every McKinsey-style presentation:

• The executive summary. One slide, the whole pyramid in miniature: answer, key arguments, ask. It is written so that a reader who stops there — and many are expected to — leaves with the complete case.
• Situation–complication–resolution. Minto's opening structure: what the reader already agrees is true, the thing that changed or broke, and therefore the question this deck answers. Three slides at most, and the only set-up the deck allows itself.
• MECE groupings. The supporting arguments are mutually exclusive and collectively exhaustive — no two overlap, and together they cover the ground. It is the test that stops a storyline being a heap: if two sections keep borrowing each other's evidence, the structure is wrong.
• Appendix discipline. The main flow carries only what the argument needs; every analysis that might answer a question waits in a numbered appendix, jumped to on demand. Consulting decks can run long in total pages precisely because the storyline stays short — the arithmetic is in our guide to how many slides a presentation really needs.

Partner-ready or analyst draft?

Inside a firm, the gap between a draft and a deck that goes to the client is not design flair — it is whether the grammar above has actually been applied. The same checklist works for anyone:

Storyboard in a doc, then let the doc become the deck

Notice what the ghost-deck convention implies: the hard part of a consulting deck is a writing exercise, not a design one. The storyboard is really a structured document — an answer, a key line, a stack of asserted titles with evidence beneath them. Which means the modern workflow is to do that thinking where thinking is cheap, in a doc, and hand the production step off:

1. Write the answer as one sentence. If you cannot state the governing thought in a line, you are not ready to make slides — that is the pyramid's first filter, and it is brutal on purpose.
2. List the key line. Three or so arguments that together carry the answer. Run the MECE check: no overlaps, no gaps, no argument that is really two.
3. Draft the action titles. Under each argument, write the titles of its slides as full assertions. Read the titles aloud, top to bottom — the horizontal test. Fix the storyline here, where reordering costs nothing.
4. Sketch the evidence. Under each title, note what would prove it — a comparison, a trend, a quote, a table. One line each. This is your ghost deck, in prose.
5. Turn the doc into the deck. Upload the storyboard with a one-line brief and let a doc-to-deck tool build the pages: structured slides with speaker notes on every one, exported as a native, fully editable .pptx in which every text element opens as a real object — so tightening a title in PowerPoint is an edit, not a redraw. The mechanics are in our walkthrough of turning a Word document into a presentation.
6. Edit like a partner. Reread the titles in sequence, cut what the argument doesn't need, demote the rest to the appendix. The storyline is yours to defend in the room — which is exactly why steps one to four stay yours.

The division of labour matters. A tool can group, phrase and lay out; it cannot know your answer, and it shouldn't be trusted to. Do the pyramid yourself, then judge production tools on the one thing that wrecks this workflow at the last step — whether the exported file is genuinely editable. Our round-up of AI presentation makers that export truly editable .pptx files tests exactly that.

Keep reading

• The board deck, structured: what directors actually want
• The best AI deck maker in 2026: the full field test
• Kinsy pricing — plans and credits