Minto Pyramid

Minto Pyramid Principle

Barbara Minto's Pyramid Principle is the structuring discipline behind McKinsey-style communication. Its core idea: readers can only hold a few ideas at once, and they understand ideas most easily when the conclusion comes first and every supporting idea is grouped, ordered and summarised above the ideas beneath it. The result is a pyramid: one governing thought at the top, a small MECE set of key lines underneath, and supporting detail below each key line.

This skill turns a topic, a draft, a pile of notes or a vague question into that pyramid, and then into a storyline the user can put on slides or into a document.

What the user gets

Produce, in this order, unless the user asks for a subset:

1. Governing thought — the single answer, in one sentence, that the whole communication exists to deliver.
2. SCQA introduction — Situation, Complication, Question, Answer. The Answer is the governing thought.
3. Key line — 2 to 5 MECE arguments (ideally 3) that together justify the governing thought, each stated as a full-sentence claim, not a topic label.
4. Support — under each key line, the facts, analyses or examples that carry it, again as claims.
5. Storyline / slide flow — action titles in order, ready to be turned into slides or headings.
6. Open gaps — what evidence or decision is still missing to make the pyramid stand.

Default output is plain text with the pyramid rendered as an indented outline, because most users paste it into a deck or a doc. Offer a table or a mermaid diagram only if they ask for a visual.

How to build the pyramid

Step 1 — Find the question before the answer

A pyramid answers exactly one question the reader has. Before writing anything, establish:

• Who is the reader and what decision or action do they need to take?
• What is the one question they have in mind (or should have) when they open this?

If the request does not make this clear, ask one focused question rather than guessing. A pyramid built on the wrong question is worthless no matter how clean it is. If the user is clearly in a hurry, state the assumed reader and question at the top of your output and proceed.

Step 1b — Decide: answer first, or answer after the lead-in?

The pyramid itself is always built answer-first. Where the answer appears in the delivered document is a separate choice, and Minto herself makes it depend on the reader. Check before structuring, and state the choice with a one-line reason:

• Reader likely to resist the answer (it costs them budget, status or a decision they already made): lead them through Situation and Complication first and let the answer arrive as the conclusion of a tension they have accepted. Putting a contested answer in the first sentence closes the reader before the arguments are heard.
• Reader lacks the background to place the answer (new topic, training, first contact): give more Situation than usual; an answer nobody can locate is noise.
• Communication is about people, not logic (change, conflict, a team that has to be taken along): the pyramid carries the argument, but it does not carry the relationship. Say so and suggest what the pyramid needs next to it — a story, an acknowledgement, a conversation rather than a document.
• Analytical audiences who expect derivation before conclusion (engineers, scientists, some legal and finance cultures): "recommendation first" can read as premature. Keep the pyramid, soften the opening.

Default for executives and boards remains answer first. The point of this step is that the default is a choice, not a reflex.

Step 2 — Write the introduction as SCQA

The introduction leads the reader from what they already know and agree with to the question the document answers. Keep it short and uncontroversial.

• Situation: a stable, agreed starting point. Nothing the reader would dispute.
• Complication: what changed, went wrong, or now demands attention. This creates the tension.
• Question: the question that tension naturally raises in the reader's mind.
• Answer: the governing thought.

Variants of order are legitimate and depend on the reader's mood: lead with the Answer for impatient executives, lead with the Complication to convey urgency, lead with the Question when the reader is already anxious about it. See references/scqa-patterns.md for worked patterns and typical mistakes.

Step 3 — State the governing thought as a claim

The governing thought is a complete sentence that could stand alone as the "so what". Test it:

• Does it answer the question from Step 1 directly?
• Does it contain a verb and a position ("we should", "X is", "the cause is") rather than a topic ("overview of options")?
• Would the reader be able to act on it if they read nothing else?

"Our marketing channel mix" is a topic. "We should shift 30 % of paid budget from display to search, because search is the only channel where incremental spend still pays back" is a governing thought.

Step 4 — Build the key line (MECE)

The key line answers the question the governing thought raises in the reader's mind — usually "Why?", "How?", or "What exactly?". Every key line point must be:

• a claim in a full sentence, not a heading;
• mutually exclusive of the other points (no overlap in what they cover);
• collectively exhaustive with them (together they fully justify the parent — nothing important is left out);
• of the same kind (all reasons, or all steps, or all parts — never a mix).

Aim for three; never exceed five. If you have seven arguments, some of them belong under others. See references/mece-grouping.md for the standard grouping frames (process, structure, class, time, and the "same kind" test) and for how to find the summary sentence above a group.

Step 5 — Choose the horizontal logic and make it explicit

Ideas at any level relate to each other either deductively (premise → premise → therefore conclusion) or inductively (several parallel ideas of the same kind, summarised by their common point). Inductive groupings are easier for readers of business documents and should be the default for key lines; deductive chains work for short, tight arguments where the reader must follow each step.

Never mix the two in one group. If the user's draft mixes them, that is usually why it feels unconvincing — say so.

Step 6 — Check the vertical logic (question / answer dialogue)

Walk the pyramid top-down. At each node, the reader asks a question of the statement above ("Why?" / "How?" / "Which ones?"), and the level below must answer exactly that question and nothing else. Anything that does not answer the question raised above it is either misplaced or padding.

Step 7 — Order the support and write the storyline

Within a group, order by the logic of the group: time order for steps, structural order for parts, degree order (most important first) for reasons. Then write one action title per slide or section: a full sentence stating the point, so that reading only the titles in sequence tells the whole story (the "dot-dash" or "ghost deck" test).

Working from an existing draft

When the user hands over a deck, memo or notes:

1. Extract every claim and fact into a flat list.
2. Identify the question the document is trying to answer; check whether the draft ever states an answer.
3. Rebuild the pyramid bottom-up: group facts, write the summary point above each group, repeat until one governing thought remains.
4. Show the user what moved, what was merged, and what got cut, as an explicit change list with a one-line reason per change (template 4 in references/output-templates.md) — not as scattered annotations. When the user gave only headings and no content, say clearly that the new key lines are hypotheses the content must confirm; do not present a grouping invented from headings as if it were derived from evidence. Be candid about the diagnosis — "the deck has no governing thought, it's a tour of the analysis" is more useful than a polite rewrite.

Common failure modes to catch

• Topic headings instead of claims ("Market overview", "Next steps") — replace with sentences.
• Answer buried at the end — the classic analyst deck that narrates the journey. Move the answer up front.
• Intellectually blank summaries ("There are three issues") — the summary above a group must state what the group adds up to, not count its members.
• Overlapping key lines — usually a sign that two points are the same argument at different levels of abstraction.
• Lists longer than five — regroup.
• Situation that is already contentious — the reader stops agreeing before the tension is set up; move disputable content into the Complication or the body.
• Slides whose title does not match their content — retitle or rebuild.

Think bottom-up, present top-down

The order of building is the reverse of the order of reading. Start from the facts and ideas the user actually has, group them, write the summary above each group, and climb until one governing thought remains. Only then write top-down. A pyramid written top-down from the start tends to have a confident governing thought with nothing real underneath it.

Transfer into the target format

• Deck: one key line or support claim per slide as the action title; the agenda slide is the key line in final order; the ghost-deck test (titles alone tell the story) is the acceptance criterion.
• Memo / e-mail: SCQA as the first paragraph, answer at its end (or first sentence, per Step 1b); key lines as bold lead sentences or sub-headings; support in the paragraphs under them.
• Verbal briefing / talking points: governing thought as the first sentence, then the key line as three short bullets the user can read off.

Where the method stops

The Pyramid Principle is a tool for logical exposition. It does not build suspense, tell a story, or create emotional agreement, and it should not be forced onto formats that need those (a keynote, a change announcement, a training). It also cannot repair thin content: if the support under a key line is weak, the pyramid makes that visible rather than hiding it — which is the point, but the user should hear it. Where facts or market data are missing and would settle a key line, say which fact would do it; research it if tools are available and mark sourced facts as such, otherwise mark the gap.

Tone and fit

Use the user's own terminology, company names and numbers. Do not invent data; where a key line needs a number the user has not given, mark it as a gap rather than filling it. Keep the pyramid lean — fewer, sharper claims beat exhaustive coverage. If the user writes in German (or any other language), answer in that language and keep the Minto terms (SCQA, key line, MECE, governing thought) in English, as is customary in consulting practice.

References

• references/scqa-patterns.md — SCQA variants by reader mood, examples, and what a good Situation looks like.
• references/mece-grouping.md — grouping frames, the "same kind" test, how to write summary points, deductive vs. inductive with examples.
• references/output-templates.md — templates for the pyramid outline, a one-page executive summary, and a slide storyline; use them so outputs look consistent.