Overview

The Pyramid Principle was developed by Barbara Minto, who joined McKinsey & Company in 1963 as the firm's first female hire from Harvard Business School. Minto developed the framework to address a persistent problem she observed in McKinsey's written outputs: analysts who had done excellent analysis couldn't communicate it clearly. They would build their argument from the bottom up — laying out all the evidence and reasoning before arriving at the conclusion — which was intellectually thorough but practically unusable for the busy executives they were advising.

Minto's insight: the structure that produces a good analysis is the opposite of the structure that communicates it well. Analysis proceeds bottom-up (gather data, identify patterns, draw conclusions). Communication should proceed top-down (state the conclusion, then provide the supporting logic). She published the approach in The Pyramid Principle: Logic in Writing and Thinking (1987, Pitman; revised editions Pearson/FT Press), and it has been a cornerstone of consulting communication training ever since.

The core rule: every written or verbal communication should lead with the answer — the governing thought, the main message, the "so what." Supporting points follow, organized to explain and justify that governing thought. The structure is literally pyramidal: the top contains the single most important idea; the level below contains the grouped and summarized supporting arguments; the level below that contains the evidence for each supporting argument.

Two structural principles run through the framework:

Two types of argument structure:

The SCQA framework provides a standard opening structure for any communication:

When to Use It

For any consequential written or verbal communication: a recommendation presentation, an executive summary, an email to a senior stakeholder, a client update, a decision memo. The Pyramid Principle is most valuable when the audience is time-constrained, information-dense situations where the listener might not make it to the end, and any context where the credibility of the recommendation depends on its structure being clear.

How It Works

  1. Identify the governing thought — what is the single most important thing you need the audience to take away? Write it in one sentence. This is the top of the pyramid.
  2. Build the SCQA opening — set up the governing thought with a Situation and Complication that makes the answer feel necessary and inevitable, not arbitrary.
  3. Group supporting arguments — identify the 2–5 key arguments that justify or explain the governing thought. Apply the MECE test: do they overlap? Do they together fully support the top?
  4. Write summary sentences — for each group of supporting arguments, write a governing thought: not a topic label ("Market Analysis") but a conclusion ("The market is structurally attractive but competitively crowded").
  5. Add evidence — at the base of the pyramid, the facts, data, and analysis that support each argument above.
  6. Read top-down — the governing thought plus the summary sentences of each supporting argument should read as a complete, coherent argument on their own. If someone only reads the top two levels, they should understand the full recommendation.

Running It in a Session

Apply the Pyramid Principle explicitly to the recommendation presentation. The Lead Consultant should open with the answer — the governing thought — in the first sentence. Not "we looked at three areas: X, Y, and Z" but "you should do A, because B and C, and here's how."

Use SCQA to open the presentation: "You're growing revenue but your margin is compressing [Situation]. The pricing renegotiations from your two largest customers have permanently reset your revenue mix [Complication]. The question is whether this is structural or recoverable [Question]. We believe it's recoverable — but it requires a specific set of moves on the cost side [Answer]." That structure earns the next ten minutes of attention.

In the debrief, the "Would I hire?" round often hinges on whether the recommendation was structured. A team that builds beautifully to a conclusion that arrives at minute 8 of a 10-minute presentation has failed the Pyramid test.

Common Pitfalls

References & Further Reading

  • Minto, Barbara. The Pyramid Principle: Logic in Writing and Thinking (1987, Pitman; revised editions Pearson/FT Press)
  • Rasiel, Ethan M. The McKinsey Way (1999, McGraw-Hill) — includes an accessible chapter on Minto's framework in practice

Recommended Books