The Minto Pyramid Principle is Barbara Minto's 1987 framework for structuring communication so that the most important point arrives first, not last. Most people think bottom-up — assemble evidence, reason from it, arrive at a conclusion — and then present in the same order. The Pyramid inverts that: state the governing thought first, then the supporting arguments (MECE — mutually exclusive, collectively exhaustive), then the data underneath each. The SCQA form (Situation–Complication–Question–Answer) is Minto's narrative wrapper for the governing thought, useful when the audience needs context before they can absorb the conclusion.

When to use Minto Pyramid · SCQA

Use the Minto Pyramid for executive communication, written documents, and any high-stakes presentation where the audience is time-constrained and already informed about the general domain.

Board decks and executive summaries
Written recommendations and decision documents
Status updates to senior leadership
Consulting deliverables and client presentations
Any email where the ask is buried in the third paragraph

How to use it

Find your governing thought first. What is the single most important thing you want the reader to walk away believing or doing? Write that sentence. Everything else is in service of it.
Build the SCQA wrapper. Situation (context they already know) → Complication (what changed or is at risk) → Question (what this naturally raises) → Answer (your governing thought). SCQA orients the audience before you make the argument.
Support the governing thought with 2–4 MECE arguments. MECE means each argument covers distinct ground (mutually exclusive) and together they cover all the ground (collectively exhaustive). If two arguments overlap, merge them.
Put data under each argument, not the other way around. The governing thought and arguments should be comprehensible without the data; the data is there for the skeptic.
Apply to slide headlines. Every slide headline should state the conclusion, not the topic. "Revenue grew 12% QoQ, driven by enterprise" is a Minto headline. "Revenue" is a topic label.

Example

Them

Can you send me a quick summary of where we are on the infrastructure migration?

On your HUD

We should accelerate the migration to Q2 rather than waiting for Q3.
Three reasons: the vendor sunsets support in June, the engineering team has capacity now that will be absorbed by the May product launch, and the new quote came in 20% lower than the approved estimate.
The decision we need from you is whether to reallocate two engineers from the roadmap to make Q2 work.

What Kennan would surface in this moment, in the same first-person bullet format as the in-app HUD.

Common pitfalls

Building bottom-up and presenting bottom-up. Presenting your reasoning process ("first we looked at X, then we found Y, so we concluded Z") is the opposite of top-down. Lead with Z.
Governing thoughts that are topics, not conclusions. "The state of the migration" is a topic. "The migration is on track to miss the June deadline without a scope change" is a governing thought.
Too many supporting arguments. More than four means the structure has not been made MECE. Collapse the weakest into the strongest, or find the one dimension along which all of them fit.

Where it comes from

Minto, The Minto Pyramid Principle (1987)

In your next meeting

Kennan watches for the conversational pattern this framework addresses and surfaces a first-person line you can read off your HUD, in the same shape as the example above. Frameworks are receipts; the user-facing output is a sentence, not a citation.