The Pyramid Principle for Strategists: Where Storylines Break

The deck with the answer on slide 22

Picture a strategy team presenting a pricing review to the chief financial officer. Twenty-two slides. Market context, customer interviews, competitor prices, elasticity estimates, three options scored on four criteria. On slide 22, the recommendation. The CFO has already flipped to it. “Why didn't you start here?”

So the team rebuilds the deck answer-first. Slide one now says: “We recommend raising list prices 4% on the mid-tier line.” Slide two is headed “Three market dynamics.” Slide three, “Customer perspectives.” Slide four, “Competitive considerations.” The CFO reads slide one, then two, and asks the same question in a different form: “So what?”

The team fixed the top of the pyramid and left the joints broken. The Pyramid Principle, developed by Barbara Minto, says that “your thinking will be easy for a reader to grasp if you present the ideas organized as a pyramid under a single point” ¹. The single point goes first. Every level below it supports the level above. And each point on each level summarizes, as a claim, the ideas grouped beneath it.

That last rule is where nearly every storyline fails. The thesis of this page: answer-first is the easy half of the pyramid. A storyline breaks at its joints, at the first summary point that announces a topic instead of stating what the ideas beneath it mean.

A heading that names a topic is a drawer. A heading that makes a claim is an argument.

What Minto actually said

Minto's own course is based on a similar course she developed and taught for several years at McKinsey & Company ². Her textbook is now The Minto Pyramid Principle: Logic in Writing, Thinking and Problem Solving, which supersedes the earlier The Pyramid Principle, first written in 1987 ³.

Two ideas on her own site are worth more than most summaries of the book. First, the pyramid is how thinking is done, not just how it is presented. People ideally work out their ideas, she writes, by grouping low-level facts they see as similar, drawing an insight from the similarity, then grouping related insights, until the thinking ends in “a single pyramid of ideas, at many levels, obeying logical rules, and held together by a single thought” ⁴. Second, once that is done, presentation is simple: “Communicating the thinking requires only that you guide the reader down the pyramid” ⁴.

So the pyramid is built bottom-up and delivered top-down. Most people who learn the method learn only the delivery. For the rule that keeps groupings clean, see MECE, with real work examples. For how a governing hypothesis drives the analysis before any writing starts, see hypothesis-driven problem solving.

The opening: situation, complication, question

Before the answer, the reader needs the question. Minto's course teaches what she calls the Situation, Complication, Question framework “for identifying the question in your reader's mind” ¹. The situation is something the reader already accepts. The complication is what changed. The question is the one the complication raises, and the top of your pyramid answers it.

The test of an opening: nothing in it should surprise or annoy the reader except the complication, and the question should be the one they would have asked. If the reader disagrees with your situation, you have started an argument before reaching the answer. Strategy teams often shorten the structure to situation, complication, resolution; the executive summary template applies it to a one-page summary.

The joints: summary points that think

Minto's course description includes a line every analyst should tape to the monitor. The course teaches how to look critically at groupings, to make sure that when you say “There are three reasons for making this change,” there are in fact only three, that they are the right three, “and that you have drawn the appropriate insight from having identified them. (‘There are three reasons’ is not an appropriate insight!)” ².

Why do analysts write topic labels instead of claims? Because a label is safe. “Customer perspectives” cannot be wrong. “Customers in the mid-tier rarely compare prices, and none of the 30 we interviewed named price as a reason to switch” can be wrong, and the CFO can check it. The label postpones the thinking to the reader. The claim does the thinking and exposes it. That is exactly why the claim is worth the reader's time.

• The so-what test. Read a summary point aloud and ask “so what?” If the honest answer is the real point, write that instead.
• The derivation test. Cover the summary and read only the points beneath it. Would a smart reader arrive at your summary from those points alone? If not, either the summary overreaches or a point is missing.
• The question test. Each point raises a question in the reader's mind (why? how? how do you know?). The level beneath must answer exactly that question, and nothing else.
• The same-kind test. Ideas in one group should be the same kind of idea: all reasons, all steps, all problems. A group that mixes a reason, a risk and a next step has no summary that can be true of all three.

Read the right-hand column alone and you have the argument. Read the left-hand column alone and you have a table of contents.

A worked storyline

The company below is invented. Here is the pricing storyline as a pyramid, written as the sentences that would become slide titles or memo headings.

Check the arithmetic the way a CFO would. If volume holds, 4% on $150 million is $6 million, all of it margin. If volume falls 3%, revenue is $150 million × 1.04 × 0.97, about $151.3 million, while costs fall 3% from $90 million to $87.3 million; gross margin goes from $60 million to about $64 million, a gain of about $4 million. The cost base of $90 million also explains the complication: a 10% rise in input costs is the $9 million. Notice that Support 3 is the claim most likely to be challenged, so it is the one that needs its model in the appendix. A good pyramid tells you where to put your evidence: under the joint most likely to break.

Build the storyline before the analysis is done

The method is most useful early, not at the end. Writing the pyramid on day two, with your best current answer at the top, tells you which analyses matter: the ones that test the joints. It also tells you when you are finished: when every joint holds.

1. Write the questionDraft the situation and complication in two sentences each, then the question they raise. Check it with the decision maker before you do anything else.
2. Write a one-sentence answerYour best current answer, specific enough to be wrong. A placeholder answer is still better than none, because it shapes the support beneath it.
3. Write the supporting claimsThree to five sentences, each a claim, each answering the question the answer raises. Apply the so-what and same-kind tests.
4. List the evidence each claim needsUnder each claim, note the facts or analyses that would prove it. That list is your work plan.
5. Find the weakest jointMark the claim you are least sure of and do that analysis first. If it fails, rewrite the answer.
6. Turn sentences into titlesOnly when the pyramid holds, turn each claim into a slide title or memo heading. The headings, read in order, should be the whole argument.

When answer-first backfires, and what the pyramid hides

The strongest objection is that answer-first fails with some audiences. A board hostile to the recommendation hears the answer and spends the meeting building a rebuttal. A team receiving bad news needs the reasons before the verdict. Some cultures and some executives expect context first, and read an opening recommendation as presumption.

Part of this is right. The objection is really about the opening, and the SCQ structure already handles most of it: a situation the audience accepts and a complication they recognize put them in the frame of mind to want an answer before you give one. For a hostile room, state the question first and secure agreement that it is the right question; then give the answer. What rarely works is hiding the answer on slide 22. The skeptical reader finds it early anyway, and now distrusts the 21 slides that delayed it.

The deeper risk is the reverse. A clean pyramid looks more certain than the analysis is. Every claim stated crisply, every group tidy: the structure can hide that Support 3 rests on one model with a wide range. At senior level, the honest pyramid shows its weakest joint on purpose (“the volume estimate is the uncertain part; here is what happens if it is twice as bad”). Executives who have been burned by tidy storylines trust the one that points at its own soft spot. See managing up for how to raise that risk with a skeptical executive before the meeting.

One more problem at scale: in a large team, the storyline becomes the control point. Whoever owns the pyramid owns the conclusion, and analysts produce charts to fit. A good engagement lead treats the pyramid as a hypothesis to be broken, not a script to be filled, and rewards the analyst who finds the joint that does not hold.

Before you send it

• The question is one the decision maker agrees is the question.
• The top point is one sentence a reader could act on.
• Every summary point is a claim that could be wrong, not a topic.
• Each group answers the single question its parent raises, and holds one kind of idea.
• The headings, read alone and in order, make the whole argument.
• The weakest joint is named, with its evidence nearby.

Monday morning: take the last deck you sent and copy out only its slide titles. Circle every title that names a topic instead of making a claim. Rewrite those as sentences. That list of rewritten titles is your storyline, and it is probably a different argument from the one the deck made.

Minto's pyramid is often taught as a rule about order: answer first. It is really a rule about honesty. Every joint is a place where you say what your evidence means and invite the reader to check. Labels avoid that. Claims make it unavoidable, which is why they persuade.

Questions

What is the Pyramid Principle?

The Pyramid Principle is Barbara Minto's method for structuring business writing and thinking. Ideas are organized as a pyramid under a single governing point: the point comes first, and each level below summarizes and supports the level above. Her writing course grew out of one she developed and taught at McKinsey, and her textbook sets out the full method.

What is the SCQ framework?

SCQ stands for situation, complication, question. Minto uses it to open a document: the situation is what the reader already accepts, the complication is what changed, and the question is the one that change raises in the reader's mind. The rest of the document answers that question, starting with the single point at the top of the pyramid.

What is the difference between SCQ and SCR?

SCQ, Minto's term, ends the opening with the question the complication raises; the document then answers it. SCR, situation, complication, resolution, is a common consulting shorthand that writes the answer straight into the opening. They describe the same logic. SCQ makes you check that you are answering the reader's question, which is the step most often skipped.

Why do pyramid storylines fail?

Most fail at the joints, not the top. Writers put the answer first but then use topic labels such as “Market dynamics” as supporting points, so the reader gets drawers instead of reasons. Each summary point should be a claim the points beneath it prove. Minto's own course warns that “There are three reasons” is not an insight.

Where to go next

• Executive Summary Template (situation, complication, resolution)
• MECE, With Real Work Examples
• How Strategists Think: Hypothesis-Driven Problem Solving
• Board Deck
• Root-Cause Tree (5 Whys)