Case Interview HQ
Frameworks

The Minto Pyramid Principle: Start With the Answer

Short answer

The Minto Pyramid Principle is a method for structuring communication top-down: state your conclusion first, then group the supporting arguments beneath it, with each group MECE and each point summarizing the ones below. Barbara Minto developed it at McKinsey after 1963. Consultants use it in reports, emails and case interview recommendations because listeners grasp the answer immediately.

Key takeaways

  • Lead with the conclusion, then support it with three or so grouped arguments.
  • Barbara Minto, McKinsey's first female MBA hire, developed the principle while editing consultants' reports; her book appeared in 1985.
  • Bottom-up storytelling lets listeners build their own conclusion, which may differ from yours.
  • The key line under the conclusion should be actionable, and every group in the pyramid should be MECE.
  • In a case interview, the final recommendation is a 60-second pyramid.

What is the Minto Pyramid Principle?

The Minto Pyramid Principle is a way of structuring any message so the conclusion comes first. You state the main point at the top, support it with a small set of grouped arguments, and support each argument with facts below it. The listener understands your answer from the first sentence and can follow the reasoning in whatever depth they need.

Consultants use it for slide decks, emails, reports and spoken updates. In a case interview, it is the structure of a strong final recommendation.

Who is Barbara Minto?

Barbara Minto joined McKinsey in 1963 as the firm's first female MBA hire, after graduating from Harvard Business School in a class with only a handful of women. She started in the Cleveland office and moved to London in 1966, where the firm was building its European practice.

Minto became known for improving the writing of consultants. Editing their reports, she saw the same problem again and again: the language was fine, but the thinking behind it was disorganized. She kept rearranging ideas into a pyramid in which each point summarizes the group of points beneath it. She also coined MECE, the grouping rule that keeps each layer clean.

After leaving McKinsey in 1973 she set up her own training business and published The Pyramid Principle in 1985, with an expanded edition in 1996. For the firm's wider background, see McKinsey history.

Why top-down beats bottom-up

Bottom-up communication walks through facts first and reveals the conclusion at the end. The risk: while you talk, the listener builds their own framework and reaches their own conclusion, which may differ from yours. By the time you state your answer, you are arguing against an idea they already hold.

Top-down communication removes that risk. The listener hears the conclusion first and then reads every following fact as support for it.

Example 1: Linda's move

Here is the bottom-up version:

"Linda has worked in New York for six years and finds the commute exhausting. She spends most weekends hiking and wishes she had trails closer to home. She speaks English and some French, has a permanent residence card for Canada through her mother, and enjoys long winters. Her employer has an office in Toronto. So Linda should move to a suburb of Toronto."

By the third sentence, a listener might have decided she belongs in Vancouver, Montreal or a mountain town in Colorado. Now the pyramid version:

Linda should leave New York for a suburb of Toronto.

  1. Canada fits her legal and work situation. She already holds Canadian residence, and her employer has a Toronto office she can transfer to.
  2. A suburb gives her the outdoor life she wants. Hiking trails and long winters are within easy reach, without a two-hour commute.
  3. She can work in English from day one. Toronto runs mainly in English, while her French is only partial, which makes Montreal a harder fit.

The same facts, the same conclusion, but the listener never has to guess where the argument is going.

How to build a pyramid step by step

  1. Write the conclusion in one sentence. It should answer the question the audience has.
  2. List every supporting idea you have. Facts, analyses, observations.
  3. Group the ideas. Each group should share one logic (reasons, steps or segments) and the groups together should be MECE.
  4. Write the key line. Summarize each group in one sentence. Together these form the second layer and should be actionable.
  5. Order the groups. By importance, by time or by structure, and keep one ordering principle per layer.
  6. Test it. Read only the top two layers aloud. If a listener could act on that alone, the pyramid works.

Example 2: a business recommendation

Bottom-up: sales of a kitchen appliance maker fell 12% over two years, a low-cost competitor entered with prices 15% lower, the company opened a second factory that runs at half capacity, and unit costs rose because fixed costs are spread over fewer units.

The pyramid:

Restore profitability by lowering prices 10% to win back volume and fill the new factory.

  1. The volume loss comes from price. Customers switched to a competitor that undercuts us by 15%; quality scores stayed level.
  2. Higher volume cuts our unit costs. Filling the second factory to 85% capacity spreads fixed costs over 40% more units.
  3. The numbers work. At 10% lower prices, the volume gain and unit-cost savings together raise operating profit within 18 months.

Each line in the key line is a claim the CEO can test, and the conclusion at the top tells her what to do.

The Pyramid Principle in case interviews

The final recommendation in a case interview is a 60-second pyramid: answer, three supporting reasons, the main risk and next steps. Interviewers score synthesis explicitly, and candidates who end by recapping their process lose points. I describe that pattern in case interview mistakes.

You can also use the pyramid at transition points. After a block of analysis, say "So far, the data says the problem sits in Region C, for two reasons" before moving on. It keeps the interviewer oriented and shows you are driving the case.

Stephan's note: I still write every client email this way: the first line is the answer or the request, the rest is support. Once you train the habit for case interviews, it pays off for the rest of your career.

Where to learn more

Minto's own book remains the reference for the full method, including the SCQA introduction. For the case interview context, read the complete case interview guide and practice the close at the end of every practice case. My book Cracking the Case shows the pyramid applied in three fully worked candidate cases, from opening structure to final recommendation.

Frequently asked questions

Who invented the Pyramid Principle?

Barbara Minto developed it at McKinsey, which she joined in 1963. She published The Pyramid Principle in 1985 and an expanded edition in 1996.

What is the difference between top-down and bottom-up communication?

Top-down states the conclusion first and then the reasons. Bottom-up walks through facts and reasoning and reveals the conclusion at the end. Busy executives prefer top-down because they get the answer in the first sentence.

How many supporting points should a pyramid have?

Two to five per group, with three as the most common choice. More than five usually means the points need to be regrouped under a higher-level idea.

Is the Pyramid Principle the same as SCQA?

SCQA (situation, complication, question, answer) is Minto's technique for writing the introduction that leads into the pyramid. It is part of the same method.

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

Use it for the final recommendation: answer first, three supporting reasons from your analysis, then risks and next steps. You can also use it whenever you summarize midway through the case.

Sources

  1. McKinsey Alumni: Barbara Minto on MECE
  2. Wikipedia: Barbara Minto

Stephan Spijkers

Stephan Spijkers founded Case Interview HQ in 2011 after working through the strategy consulting selection process himself: written test, case rounds and partner interviews. He has interviewed candidates from the other side of the table, coached students one-on-one and in group sessions, and wrote Cracking the Case and the two Key to the PST practice books. Today he runs PIMvendors.com, a product information management consultancy.