# The Pyramid Principle, Explained

> What the Pyramid Principle is, where it came from, and when not to use it. With a worked example and a version you can play.

Source: https://www.wavetable.net/frameworks/pyramid-principle

[Frameworks](https://www.wavetable.net/frameworks)

CommunicationAlso called Minto Pyramid

# Pyramid Principle

Put your answer first, then group the reasons that support it underneath.

## In one look

1.  1Answer first.
2.  2Reasons grouped beneath it.
3.  3Detail on demand.

Barbara Minto, one of McKinsey's first women consultants, developed it after the firm sent her to London in 1966 to fix its European reports. They were written in the order the analysis happened, with the point at the end. She reversed it, and her book is still handed to new consultants.

The problem it solves

## The recommendation is on slide 34.

Forty minutes of context, then the exec looks up and asks the question slide 34 was about to answer. Most decks run in the order the work happened, so the point comes last. Now that a polished document takes seconds to make, getting the order right is the part that still takes thought.

## Try it yourself

No sign-up, a few minutes. The shareholder letter goes out in an hour, and you pick its opening line.

## The same update, answer first

A Q3 update on a new checkout flow, to an exec who has five minutes.

-   Built up toWe looked at the Q3 numbers, and a few things are going on.becomes We should roll back the new checkout flow.
-   Built up toTraffic is up 12% but conversion dipped, so the data is noisy.becomes Conversion fell 8% from the day it launched.
-   Built up toSupport tickets also rose...becomes Payment tickets doubled, and the holdout group converted at the old rate throughout.

## Good times to run it

-   Recommendation decks and board papers
-   The client email that needs a decision
-   The "so, what do you think?" moment in a pitch
-   Updates where the news matters more than how you got there

## When to skip it

-   When you don't know the answer yet. Putting a guess first only makes it sound certain.
-   Discovery conversations, where concluding early closes doors.
-   A hostile audience that needs to walk the reasoning with you first.

Teams we've run sessions with:

-   ![Publicis Groupe](https://www.wavetable.net/logos/publicis-groupe.svg)
-   ![SoundCloud](https://www.wavetable.net/logos/soundcloud.svg)
-   ![WeTransfer](https://www.wavetable.net/logos/wetransfer.svg)
-   ![The New York Times](https://www.wavetable.net/logos/nyt.svg)
-   ![Columbia Business School](https://www.wavetable.net/logos/columbia.svg)
-   ![EY](https://www.wavetable.net/logos/ey.svg)
-   ![Havas](https://www.wavetable.net/logos/havas.svg)
-   ![NYC](https://www.wavetable.net/logos/nyc.svg)
-   ![MCI Group](https://www.wavetable.net/logos/mci-group.svg)
-   
-   
-   
-   
-   
-   
-   
-   
-   

## Run it with your team

That was Netflix's letter. On your own recommendation, with the exec already interrupting, it's harder. We run it as a live session on a recommendation like yours, in small groups with a host.

[Consulting firms](https://www.wavetable.net/for/consulting-firms)[Storytelling for leaders](https://www.wavetable.net/for/storytelling-for-leaders)

## More frameworks

-   [Communication**SCQA**A four-part opening for any memo, deck or email: what they already accept, what changed, the question that raises, and your answer.](https://www.wavetable.net/frameworks/scqa)
-   [Structuring thinking**MECE**A test for any list: no item overlaps another, and nothing important is missing.](https://www.wavetable.net/frameworks/mece)
-   [Structuring thinking**First Principles Thinking**Break a problem down to the facts you can check, then reason up from those instead of from what's usually done.](https://www.wavetable.net/frameworks/first-principles)
