Watch a smart person present a recommendation badly. They walk you through the background, then the analysis, then the options, then, finally, on slide 14, what they think you should do. By then half the room has stopped listening and started guessing. The information was all there; the structure was upside down.

The quick version

  • The Pyramid Principle, created by Barbara Minto at McKinsey, says: lead with your single main point (the answer), then support it with a small number of grouped arguments, each backed by evidence.
  • Readers grasp ideas fastest when they are arranged as a pyramid under one point, top-down, not in the order you happened to think of them.
  • The groups of support must be MECE, mutually exclusive, collectively exhaustive, so they don't overlap and don't leave gaps.
  • To set up the answer, open with SCQA: Situation, Complication, Question, Answer, establish what's agreed, what changed, the question that raises, and your answer to it.

The idea in depth: answer first

The core claim is almost insultingly simple, which is part of why it gets ignored. Minto's rule, in her own words, is that "it's easier for a reader to grasp our ideas if we organize them as a pyramid under a single point." One governing message sits at the top. Beneath it, a handful of supporting arguments. Beneath each of those, the facts and data. You read down the pyramid; the reader meets your conclusion before your reasoning.

Minto developed this at McKinsey in the early 1970s and set it out in The Pyramid Principle: Logic in Writing and Thinking (1985), revised as The Minto Pyramid Principle: Logic in Writing, Thinking and Problem Solving (1996). She was the firm's first female MBA hire, having joined McKinsey in 1963 as one of only eight women in a Harvard Business School class of 600, and she built the method to fix the same problem in consultants' reports that plagues most managers' emails: the point arrives last (see Minto's biography and her own account via barbaraminto.com).

So the move is: before you write the email, finish this sentence, "If you read nothing else, here's what I need you to know:", and put that sentence first. Everything after it is support for that one line. If you can't write the sentence, you're not ready to write the message; you're still thinking, and you should do that before you make the reader do it for you.

Why does answer-first actually work, rather than just feeling tidy? Because of how people read, especially on screens. Nielsen Norman Group's research on the inverted pyramid (Amy Schade, 2018) found that leading with the conclusion lets users "quickly form a mental model and a general understanding" of a page, so a reader who skims and stops early still leaves with your main point. Bury the conclusion at the bottom and, for everyone who doesn't read that far, it may as well not be there. The same logic the military codifies as BLUF, bottom line up front, and journalism has used for a century in the news-story inverted pyramid. Minto's contribution wasn't inventing "get to the point"; it was giving the rest of the message a rigorous shape underneath.

flowchart TD
  A(["The answer
one governing point"]) --> B(["Argument 1"])
  A --> C(["Argument 2"])
  A --> D(["Argument 3"])
  B --> B1(["facts & data"])
  C --> C1(["facts & data"])
  D --> D1(["facts & data"])
The pyramid: one point at the top, a small set of supporting arguments, evidence beneath each. You read top-down. Leaders Loop

Making the support hold together: MECE and SCQA

Leading with the answer is half the method. The other half is making the layer beneath it sound, because "answer first" with mushy support is just a confident person being wrong quickly. Minto's test for the supporting groups is MECE, her own coinage: mutually exclusive (the groups don't overlap) and collectively exhaustive (together they cover the whole question, with no gap). If your three reasons for entering a market are "it's growing," "it's growing fast," and "our competitor is weak," you don't have three reasons, you have one reason said twice and a gap where the others should be. MECE forces you to notice that.

So the move is: after drafting your supporting points, ask two questions of the set. Do any two of these overlap? Is there an obvious objection none of them addresses? Fixing overlap sharpens the argument; fixing gaps is what stops the meeting derailing on the question you didn't see coming.

Then there's the opening. A bare "do X" can land as abrupt or context-free, so Minto's device for the introduction is SCQA, Situation, Complication, Question, Answer. State the situation everyone already agrees on; name the complication that changed and creates tension; let that surface the question in the reader's mind; then give your answer. As Minto frames it, this "permits you to make sure you and the reader are standing in the same place before you take him by the hand and lead him through your thinking" (her site presents this as the SCQ Framework; the SCQA shorthand is the widely taught form, summarised well by Think Insights).

flowchart LR
  S(["Situation
what we agree is true"]) --> C(["Complication
what changed / the tension"])
  C --> Q(["Question
what that forces us to ask"])
  Q --> A(["Answer
your recommendation"])
SCQA: the opening that earns the right to lead with your answer by first establishing common ground. Leaders Loop

If you can't write the one-sentence answer first, you're not ready to write the message, you're still thinking.

An honest limitation. The Pyramid Principle is a method, not a peer-reviewed finding, and it isn't free of cost. Two cautions worth holding. First, answer-first assumes the reader will accept a conclusion before the reasoning, which works for an internal recommendation but can backfire with a hostile or skeptical audience who needs to be walked toward the conclusion, or in cultures and contexts where leading with the bottom line reads as presumptuous. Second, MECE is a discipline, not a guarantee of truth: a structure can be beautifully mutually-exclusive and collectively-exhaustive and still rest on the wrong question. Use the pyramid to organise good thinking; it won't substitute for it. The structure makes a clear argument legible, it does not make a weak argument right.

A worked example

Take a real-shaped situation. (Illustrative throughout, this is a teaching example, not a real company.) You manage a support team and you want sign-off to hire two more agents. The version most people send reads like a diary: "Hi, wanted to flag that ticket volume has been climbing since we launched the new plan, the team's been doing a lot of overtime, our response times have slipped from 4 hours to about 11, I've looked at a few options including outsourcing and a chatbot, and I think we probably need to hire, can we chat?"

The recommendation is in there, buried in the second-to-last clause, hedged with "probably," and arriving after three paragraphs of context the reader has to hold in their head. Now restructure it as a pyramid with an SCQA opening:

flowchart TD
  A(["ANSWER: approve two
support hires this quarter"]) --> B(["Service is breaking
response time 4h → 11h"])
  A --> C(["The cause is structural
+40% tickets since new plan"])
  A --> D(["Cheaper fixes won't close it
chatbot/outsourcing assessed"])
  B --> B1(["SLA breaches, churn risk"])
  C --> C1(["volume data by week"])
  D --> D1(["cost + lead-time comparison"])
The same facts, restructured: the ask on top, three non-overlapping reasons beneath, evidence under each. Leaders Loop

Written out, the opening does the SCQA work in a few lines. Situation: "We've held a 4-hour support response time for two years." Complication: "Since the new plan launched, ticket volume is up roughly 40% and response time has slipped to 11 hours." Question (implied): how do we get back to target? Answer, stated plainly: "I'm asking to approve two support hires this quarter. Here's why, in three points." Then the three MECE reasons, each with its evidence.

Notice what changed. The facts are identical, nothing was added or removed. But the reader now meets the decision first and can approve it in thirty seconds, or interrogate exactly one of the three pillars if they disagree. The three reasons are mutually exclusive (service quality, cause, alternatives-ruled-out don't overlap) and collectively exhaustive enough to pre-empt the obvious "have you considered a chatbot?" The hedge is gone, because pyramid structure forces you to commit to the point at the top. That is the whole method in one email.

Frequently asked questions

Isn't "get to the point" just common sense, why need a framework?

"Get to the point" is the easy half, and most people still don't do it under pressure. The framework earns its keep in the harder half: what comes after the point. MECE stops your support from overlapping or leaving gaps; SCQA gives the opening a repeatable shape; the pyramid keeps a long document from sprawling. It's the difference between "be clear" as advice and a checklist you can actually run on a draft.

Doesn't leading with the answer feel blunt or arrogant?

It can, if you drop the conclusion cold. That's exactly what the SCQA opening prevents, you establish the agreed situation and the shared complication first, so by the time your answer lands it reads as the obvious response to a question the reader is already asking, not a verdict imposed on them. Answer-first done well feels considerate, because it respects the reader's time.

When should I not use answer-first?

When the reader will reject the conclusion unless walked through the reasoning, a genuinely contentious recommendation, breaking bad news, or persuading a hostile audience. There, you may need to build the case before the verdict. The structure still helps; you simply lead with the question and the stakes rather than the answer. Treat answer-first as the default, not a law.

What's the difference between this and just using bullet points?

Bullets give you a list; the pyramid gives you a logic. Random bullets can still be a pile of overlapping, gappy points with no governing idea. The pyramid demands a single point at the top that every bullet beneath must support, and that the bullets be MECE. Formatting is cosmetic; structure is the argument.

How do I practise this without overthinking every email?

Reserve it for messages that ask someone to decide, fund, or act, not "running 5 minutes late." For those, build one habit: write your one-sentence answer first, then list three non-overlapping reasons, then check for the gap. After a few weeks it stops being a method you apply and becomes the way you think before you type, which was Minto's point, the structure of the writing and the structure of the thinking are the same thing.

Related in the Toolkit

Structured communication is the backbone the rest of this cluster hangs on: it's how you turn a clear structure into a story rather than a checklist, and it's the discipline that makes a one-page memo work (executive writing & memos).

Where to go next