Pyramid Principle (Minto) for Consulting: Examples (2026)

Updated Nov 9, 2026By Esteban Ronsin · Founder · former Deloitte and Accenture Strategy consultant

The Pyramid Principle is Barbara Minto's method for organizing a message as a pyramid: one governing thought at the top, two to four grouped arguments beneath it, and evidence at the base. Minto developed it at McKinsey, where she worked from 1963 to 1973. In a case interview, it is how you deliver your recommendation. This guide covers the rules, scripts, and email, slide, and AI-prompt versions.

Start a free case interview on the Pyramid Principle

Alex, your interviewer, asking this case's first question

Don't know how to case yet? Learn how to case

What is the Pyramid Principle?

The Pyramid Principle, also called the Minto Pyramid, the Minto method or the Minto framework, is a way to organize ideas under a single point, so a reader or listener can take in your thinking in the order they need it. Consultants use this pyramid framework in client work, and candidates use it in interviews. Minto's own site describes it as presenting ideas as a pyramid under one point, and says it applies to an email, a one-page memo, a long report, or a slide presentation (barbaraminto.com, checked November 2026).

A simple pyramid has three layers (top, middle, base); Minto's own pyramids can run to many levels, and each level summarizes the one below it.

LevelWhat sits thereExample (profit case)
Top: governing thoughtOne sentence that answers the questionRenegotiate the supplier contract and close the weakest stores
Middle: argumentsTwo to four grouped reasons that prove itCosts drive the decline; the supplier is overpriced; the weakest stores lose money
Base: evidenceThe data, math, and facts behind each argumentCost bridge, contract price vs market, store-level margins

Because each level summarizes the next, a listener can stop at any level and still hold a true statement. McKinsey's alumni page quotes Minto describing the pyramid as "a tool to help you find out what you think", which is why it works on your thinking before it works on your delivery (McKinsey Alumni, checked November 2026).

What is a governing thought?

A governing thought is the single point at the top of your pyramid: your answer to the question, written as a claim someone could disagree with. Everything below it exists to support it, and it must be a summary of the arguments beneath it.

A topic is not a governing thought. "Store profitability" is a topic. "Close the 40 weakest stores and renegotiate dairy" (an illustrative example) is a governing thought, because a partner can act on it or push back.

Three checks catch most weak governing thoughts:

  • Can it be wrong? If nobody could disagree, it is a topic.
  • Does it answer the exact question asked? "Should we enter Germany?" needs "Yes, with a two-city launch", not a description of how to enter.
  • The skeptic test. Read your arguments to a skeptic. If they could accept all of them and still reject your top line, the middle layer has a gap.

Start here: EV Charging Hub Profitability is a profitability case where you must find the driver of a profit drop and close with a recommendation. It has 8 questions, 3 with math, 3 exhibits. An AI interviewer runs it out loud, shows each exhibit and scores the debrief, including your communication and synthesis. Your first full case is free when you create an account.

Case (style, industry)Quant difficultyQualitative difficultyThe math you runMedian time
EV Charging Hub Profitability (McKinsey, energy and retail). 8 (3 with math), 3 exhibits.
mediummediumSegment profit bridge, percentage change17 min, 45 voice runs
Pet Care Services Market Entry (Bain, pet care). 8 (4 with math), 3 exhibits.
hardhardTAM, share caps, entry cost27 min, 14 voice runs
Regional Cinema Location Selection (McKinsey, entertainment). 9 (3 with math), 3 exhibits.
hardhardStaffing from throughput, concession revenue33 min, 24 voice runs

More cases are in the case library, 92 in all.

Who created the Pyramid Principle, and when?

Barbara Minto created the Pyramid Principle at McKinsey, where she worked from 1963 to 1973 as the firm's first female MBA professional hire. McKinsey's alumni page says she noticed that, while editing consultants' reports, she kept reorganizing the ideas into a pyramid shape, and that she diagnosed the problem as thinking, not language: people were writing before they had worked out what they thought.

YearWhat happenedSource
1963Graduates from Harvard Business School and joins McKinsey's new Cleveland officeMcKinsey Alumni
1966Moves to the London office. After seeing the same writing problems in other offices she turns the idea into a course taught at McKinsey officesMcKinsey Alumni
1973Leaves after the oil crisis cuts the London office, and starts her own training businessMcKinsey Alumni
1985 or 1987First book, The Pyramid Principle: Logic in Writing and Thinking. McKinsey's profile dates it 1985 and says Pearson mass-produced it from 1987; Minto's own site dates the book 1987 and says it was reissued unchanged in 2002McKinsey Alumni; barbaraminto.com
1996The Minto Pyramid Principle: Logic in Writing, Thinking and Problem Solving, which her site says supersedes the earlier bookbarbaraminto.com

Sources checked November 2026. The two sources disagree on the first book's date, so we show both rather than pick one. The 1996 book has 12 chapters and three appendices, and McKinsey's profile calls it the authoritative edition. Minto's site describes it as a standard text used by all of the major consulting firms.

What are the three rules of the Pyramid Principle?

The Pyramid Principle comes down to three logical rules, as Minto describes them in McKinsey's alumni profile. In our words:

  1. The point above summarizes the points below it, because it is derived from them.
  2. Ideas in a group are the same kind of idea. You cannot derive a point from a mixed group, such as two reasons and one action.
  3. Ideas in a group are in a logical order.

Rule 1 is the one candidates break without noticing. If your top line says "this is a cost problem" but your three arguments cover costs, revenue, and competitor pricing, the top line does not summarize what sits below it. Either the answer or one argument is wrong.

Her course page adds a warning about the middle layer: saying "there are three reasons" is not an insight. Check that there are really only three, that they are the right three, and say what they add up to.

What is the McKinsey rule of 3?

The McKinsey "rule of 3" is a popular shorthand for supporting your answer with three grouped reasons, and it is not a rule Minto sets. Her course page asks you to test the grouping, not hit a number.

Our working default for a spoken answer, which is a judgment and not a Minto rule:

  • Two reasons can feel thin, but are fine when the question is narrow.
  • Three is the best default: enough to feel complete, few enough to remember.
  • Four starts to leak overlap. Five or more usually means you have not grouped yet.

How do you build a pyramid step by step?

You build a pyramid bottom-up and deliver it top-down. Your analysis moves from data to insight; your delivery moves from insight to data. Minto's site describes the thinking side the same way: group low-level facts you see as similar, draw an insight from the similarity, then group related insights, until one pyramid ends in a single thought.

  1. Write the question. Put the decision your audience faces into one sentence.
  2. List what you found. Every number, observation, and calculation, unedited.
  3. Group the findings. Cluster the ones that are the same kind of idea.
  4. Name the insight of each group. Label it with what it proves, not what it covers. "Data about stores" is a topic. "The 40 weakest stores lose money at current traffic" is an insight.
  5. State the governing thought. The one answer your insights add up to, in decision language.
  6. Test rule 1. Read the top line, then the arguments. Is anything missing, and is anything extra?
  7. Order and deliver. Pick a deliberate order, then say the top line first.

What is the difference between vertical and horizontal logic?

Vertical logic is the question-and-answer dialogue between levels; horizontal logic is how the ideas within one level relate. Vertical logic is why a good pyramid feels inevitable: you state the point, the reader asks "why?" or "how?", and the next level answers exactly that. A layer that answers a question nobody asked does not belong.

Horizontal logic comes in two kinds:

  • Inductive grouping: the arguments are siblings of the same type that together support the answer. "We should enter because the market is large, we can win share, and the economics work." Each stands alone.
  • Deductive grouping: the arguments form a chain. "The market is attractive. We win in attractive markets. So we should enter." One broken link breaks the chain.

Under interview pressure, prefer inductive grouping. If the interviewer attacks one argument, the other two still stand.

How do you order the ideas in a group?

Order the ideas in a group deliberately, by the nature of the ideas and not by the order you happened to analyze them. Three orders cover most cases, and this list is our guidance:

OrderUse it whenExample
By importanceYou want the strongest point to earn the right to keep talkingLargest profit driver first, then the second, then the third
StructuralThe ideas are the parts of one wholeNorth America, Europe, Asia Pacific
TimeThe ideas are steps or events in sequencePilot in two cities, measure for a quarter, then scale

If none of the three fits, that is a signal the group is wrong. Ideas that resist ordering are often not the same kind of idea.

How does SCQA set up the pyramid?

SCQA (Situation, Complication, Question, Answer) is the opening that makes the reader feel the problem before you state the governing thought. The Answer is the top of the pyramid. Minto's own site calls the setup the SCQ Framework (Situation, Complication, Question) and describes the pyramid as held together by a single point on top. For the full template and examples, see our SCQA framework guide.

In a live case, compress SCQA into two sentences before the recommendation:

  • Situation: "The client is a regional coffee chain with healthy margins at home."
  • Complication: "Growth has stalled because the home market is saturated."
  • Question: "Should it enter Germany?"
  • Answer: "Yes, with a phased two-city launch."

How do the Pyramid Principle and MECE work together in management consulting problem solving?

In management consulting problem solving, MECE checks the groups inside the pyramid, and the pyramid decides what you say first. MECE means mutually exclusive and collectively exhaustive: no overlap and no gaps. McKinsey's alumni page says Minto credits the underlying idea to Aristotle and was the first to abbreviate it and apply it to analyzing groups of ideas. Our MECE framework guide has the two-question test.

ConceptWhat it isWhen you use it
Pyramid PrincipleCommunication structure: answer first, grouped support, data at the baseDelivering any recommendation
MECEA test for overlap and gapsBuilding the middle layer, and any issue tree
SCQAA setup: Situation, Complication, Question, AnswerThe intro that frames why your answer matters
Hypothesis-drivenLead with a best guess, then test itSolving the case; see hypothesis-driven case interviews

Pyramid Principle MECE grouping diagram with buckets feeding an inductive conclusion

The clean mental model: hypothesis-driven thinking shapes how you solve the case, an issue tree is the pyramid built before you know the answer, and once the analysis is done you invert it into a pyramid with the answer on top. The market entry framework and profitability framework show the middle layer in the two most common case types, and the complete frameworks guide shows how these fit with the rest of your toolkit, and structured thinking in a case interview covers the habit behind it.

How do you use the Pyramid Principle in a case interview?

In a case interview, use the Pyramid Principle at every moment you speak for more than a few seconds, and above all in your final recommendation. This is our guidance, not a published firm rule. It applies in McKinsey, BCG, and Bain cases alike, and our case interview communication tips cover the rest of the delivery. For what McKinsey and Bain publish about the closing recommendation, see our guide to case interview synthesis.

Four moments call for it:

  • Your structure: state the number of buckets and their names before explaining any of them.
  • Your chart reads: give the insight first, then the numbers that produce it.
  • Your math results: say what the number means before you say what the number is (see case interview math tips).
  • Your final answer: recommendation, reasons, risk, next step, in that order.

Pyramid Principle synthesis structure showing answer, reasons, and risk

The Pyramid Synthesis Delivery Pattern

  1. 01

    1. Lead with the answer. One sentence. The recommendation, stated as a decision, not a maybe. 'My recommendation is to enter the German market.'

  2. 02

    2. Group the reasons. Two to three MECE buckets, signposted. 'Three reasons: demand, our right to win, and the unit economics.'

  3. 03

    3. Support each with one number. One headline figure per argument. Do not dump every calculation; give the proof point that carries the bucket.

  4. 04

    4. Name the main risk. State the single biggest threat to your recommendation. Showing you see it makes you more credible, not less.

  5. 05

    5. De-risk and give the next step. Say how you would manage the risk and what you would do first. This turns analysis into an executable plan.

Bottom-up vs top-down: the same content, two ways

The content below is identical. Only the order changes.

Bottom-up (rambling): "So I looked at the market, and it is around 8 million customers, growing maybe 6 percent. I also checked the competitors, there are two big ones but their pricing is high. Our margin would be about 35 percent I think, and the fixed cost to enter is around 12 million. There is some risk with retaliation. So, putting that together, I guess we should probably consider entering?"

Top-down (pyramid): "My recommendation is to enter the German market with a phased two-city launch. Three reasons: the market is large and growing, we have a clear price-based right to win, and the unit economics break even within 18 months. The main risk is price retaliation, which I would manage with a staged rollout."

Same facts, same analysis. You can hear the pattern in worked profitability and market entry examples, and across our case interview examples. The first sounds like someone thinking out loud. The second sounds like a consultant briefing a client.

The full pyramid behind the script

LevelContent
Governing thought (apex)Enter the German market with a phased two-city launch.
Argument 1The market is large and growing.
Argument 2We have a right to win.
Argument 3The unit economics work.
Evidence for 18M target customers, 6% annual growth, about 2B euros addressable spend.
Evidence for 220% price advantage over the incumbent; a product feature they lack.
Evidence for 335% contribution margin (about 88 euros per customer on about 250 euros of spend); 12M euro fixed entry cost; break-even at about 137K customers (at about 88 euros of annual margin each) in about 18 months.

The three arguments are MECE: demand, competition, and economics do not overlap, and together they cover the entry decision. The figures are illustrative numbers built for this example, not a claim about any real company.

How do you use the Pyramid Principle in emails, slides, and meetings?

Use the same pyramid in every medium; only the format changes. Minto's site says the technique applies to email, memos, reports, and formal slide presentations, for internal or external audiences.

  • Email: put the recommendation or ask in the subject line and first sentence. Bottom-up: "Following our call, I reviewed the three vendor proposals..." Top-down: "Recommendation: renew with the current vendor for one year. Three reasons: switching costs, service levels, and price."
  • Slides: the slide title is the governing thought of that slide, written as a sentence. "Store profitability by volume decile" is a topic; "The 40 weakest stores lose money at current traffic" is an argument. Read only the titles and the story should hold. The executive summary carries the top-level thought plus one line per argument, in the order of the deck.
  • Memos and reports: the first paragraph is the answer, and each section opens with one argument. A reader can skim the first line of every section and rebuild your logic.
  • Meetings: open with the main point, give two or three reasons, and keep detail for questions. When someone asks for your view, answer first.

For the written-case and presentation side of consulting interviews, see our written case and presentation playbook.

What is a Minto prompt for ChatGPT or Claude?

A Minto pyramid prompt (a Minto prompt) tells an AI assistant to write your draft answer-first: governing thought, grouped arguments, then evidence. It is useful for restructuring a messy draft. It is not a substitute for deciding your own answer, because an assistant can group points that do not obey rule 1.

Paste your draft and the question it answers, then use something like this (our wording, not Minto's):

Restructure my draft using the Minto Pyramid Principle.
1. Write one governing thought: a claim that answers this question: [question].
2. Give two to four supporting arguments. Each must be the same kind of idea, and together they must have no overlap and no gaps.
3. Put the evidence from my draft under the argument it supports. Do not add facts I did not give you.
4. List anything in my draft that supports no argument.
Draft: [paste]

Then check the output yourself: does the top line summarize the arguments, and are the arguments the same kind of idea? For a case-prep workflow with an assistant, see how to use Claude for case interview prep.

When should you not use the Pyramid Principle?

Do not use the Pyramid Principle for fit or behavioral stories; use a story structure like STAR instead. A behavioral story persuades through an arc: a challenge, a struggle, a turning point, a result. If you open "tell me about a time you led a team" with the outcome, you delete the suspense that makes the listener care. Our behavioral interview guide covers how to structure personal stories.

The same caution applies when you have no answer yet. Answer-first with no answer makes a thin argument fail faster, so do the analysis, then structure it.

What are the most common Pyramid Principle mistakes?

The most common Pyramid Principle mistakes are burying the answer, listing facts instead of grouping them, drifting off the question, and giving too many arguments.

  1. Burying the answer. If your synthesis opens with "So, looking at everything we covered," you have lost the first and best ten seconds. Open with the decision.
  2. Listing facts instead of grouping them. Reciting findings in the order you found them is not a pyramid. Every fact must sit under an argument, and every argument under the answer.
  3. Drifting off the core question. If the prompt asked "should we enter," do not deliver "how to enter."
  4. A topic as the top line. If your top line could appear on a table of contents, it belongs at the base.
  5. Too many arguments. Five reasons signal that you have not prioritized.
  6. Mixing idea types in one group. Two reasons and an action step is two pyramids stacked awkwardly.

How do you practice the Pyramid Principle?

Practice the Pyramid Principle by making the first sentence of everything you say the conclusion, then getting feedback on spoken answers. You can drill the habit in the gaps of your day.

  • Subject-line-first emails. Write the subject line as the conclusion ("Approve the Q3 budget by Friday"), then make the body the support. If you cannot state the ask in the subject, you do not yet know your governing thought.
  • 30-second summaries. After an article, meeting, or video, summarize it out loud as one answer plus three reasons.
  • Build the pyramid before you speak. In a practice case, take five seconds to fix the top line and the buckets before your synthesis. Speaking before the pyramid exists is what produces rambling.

Spoken pyramids under time pressure are the actual skill, and the way to build them is repetition with feedback. In Road to Offer's cases, an AI interviewer scores your communication and synthesis, among seven debrief categories, after you deliver the recommendation out loud.

Practice your synthesis out loud before the real interview

Run an AI-guided case and deliver the recommendation top-down. Your first full case is free when you create an account.

Sources (checked November 2026)

Frequently asked questions