The Pyramid Principle: Think Bottom-Up, Write Top-Down

The structure

Barbara Minto’s The Pyramid Principle (1987, still assigned at McKinsey, Bain, and BCG) comes down to one idea: state your answer first, then support it with groups of logically ordered evidence. Every level answers the question raised by the level above.

Why most reports fail

Minto opens the book with a scheduling memo. The original:

The Conference Room is booked tomorrow, but free Thursday. Thursday at 11:00 looks to be a good time. Is that OK for you?

The reader wades through logistics before finding the point. The rewrite:

Could we reschedule today’s meeting to Thursday at 11:00? This would be more convenient for Collins and Johnson, and would also permit Clifford to be present.

Same information. The second version leads with the request and gives reasons below it.

Most writers use the writing process itself to figure out what they think. That works for the writer, but forces the reader to reverse-engineer the conclusion from a trail of observations.

George Miller’s magic number seven (plus or minus two) means the reader’s working memory fills up after four or five items. If you haven’t given them a frame by then, they’ll invent one, and it probably won’t match yours.

Minto’s fix: separate thinking from writing. Think bottom-up (gather, group, conclude). Write top-down (conclusion first, support below).

Technique 1: SCQA introductions

Every document opens with a story the reader already knows, told in four beats:

1. Situation: a stable state the reader will accept as true without argument.
2. Complication: something changed, went wrong, or is about to.
3. Question: the question that naturally arises from the complication.
4. Answer: your main point, which the rest of the document supports.

Minto shows that varying the order of these four elements changes tone without changing content:

• Considered (S-C-Q-A): “We bill clients for diversification work. No one has demonstrated a result. How do we fix this? Here’s a project plan.”
• Direct (A-S-C): “Our first priority should be improving diversification outcomes. We’ve grown 40% in five years. Yet we can’t point to a single result.”
• Concerned (C-S-A): “No diversification study has yielded demonstrable results. This is startling given 40% practice growth. We must fix this.”

Your Situation must be something the reader already agrees with. Your Complication raises the stakes. If the Complication doesn’t produce your stated Question, one of them is wrong.

SCQA maps well onto scientific reports for non-technical stakeholders. The Situation is the biology they’ve already bought into. The Complication is the gap between what the data shows and what they expected. Most analysis reports bury this across ten slides and a “Background” section nobody reads.

Technique 2: the vertical question-answer dialogue

Once you state your answer at the top, it raises a new question in the reader’s mind (“Why?” or “How?”). Your key line points answer that question. Each key line point raises its own question, answered one level below.

Minto illustrates why order matters with a story from a pub. She tells a friend:

I was in Zurich last week, and within 15 minutes I saw 15 people with beards or moustaches.

The friend guesses she’s comparing cities, or disapproves of facial hair. Wrong. She then adds observations about New York offices and London. The friend guesses again: London is ahead of the trend? Still wrong. Her actual point:

It’s incredible to me the degree to which facial hair has become an accepted part of business life.

Had she stated that first, every detail would have clicked into place. Without the frame, the listener invents a wrong one. The pyramid terminates when the reader has no more logical questions.

Minto is strict about this: never raise a question before you’re ready to answer it, and never answer a question before you’ve raised it. A section labeled “Our Assumptions” before the main argument answers questions the reader couldn’t have had yet. That information will have to be restated later.

Try this on your next draft: read just the headings. If a heading says “Background” or “Methodology” instead of stating an idea, it’s not pulling its weight. Headings should state conclusions, not categories.

Technique 3: MECE groupings

Every group of ideas at any level must be:

• Mutually Exclusive: no overlaps. If two ideas partially cover the same territory, you haven’t separated them.
• Collectively Exhaustive: no gaps. Together, the group accounts for everything relevant at that level.

Minto’s diagnostic: can you label every group with a single plural noun? “Reasons,” “steps,” “problems,” “changes.” If you can’t find the noun, the ideas aren’t the same kind of thing.

If you can name the noun but one idea doesn’t fit it, you have a misfit. Move it or split it.

Minto catches a common error with a real memo from a junior consultant at a printing company. The original lists eight problems: low productivity, same steps for every job, uncompetitive prices, behind schedule, low wages, staff shortage, high overtime, below PAR standards. Minto sorts them and finds two causal chains hiding in the list:

• Low wages → can’t hire → behind schedule → high overtime → high costs
• Same steps for every job → below PAR → low productivity → high costs

What looked like eight separate problems is actually two causes with one shared effect. The “inductive list” was a deductive argument in disguise. One piece of evidence for anything forces deductive treatment.

Technique 4: logical ordering

Ideas within each MECE group must follow one of exactly three orders:

Minto argues these are the only three because they correspond to the only three analytical activities the mind performs: determining causation, dividing wholes, and classifying likes.

The ordering test is Minto’s sharpest diagnostic tool. She takes a messy list of eleven objections to entering the plastic bottle business and sorts them onto an ROI tree (a structural order).

Once sorted, the argument becomes two claims: entry would dilute profitability short-term through lower EPS and long-term through lower ROI. The actual concern, a possible nonreturnable bottle ban, was buried at point #2 in the original list.

If you can’t find the order, your grouping is wrong.

Technique 5: induction over deduction (at the Key Line)

At the Key Line level, Minto says: prefer induction over deduction.

A deductive Key Line walks through “what’s going wrong, what’s causing it, therefore what you should do.” The reader holds the problem in memory, matches each cause to each symptom, and drags the whole chain to the recommendation. By the time they arrive, they’ve forgotten the beginning.

An inductive Key Line says: “Do these three things” and then explains each. The reader gets the answer up front, with clear fences between topics and all evidence for each recommendation in one place.

Minto’s rule of thumb: present actions before arguments. The reader cares about what to do Monday morning. Two exceptions: the reader will strongly disagree with your conclusion (so you need to prepare them), or the action makes no sense without the reasoning behind it.

Push deductive reasoning as low in the pyramid as possible. At the paragraph level, deduction flows naturally. At the section level, it becomes a mystery story.

Applying this to scientific and technical writing

Minto wrote for consultants writing memos. I came to the book looking for something different: how to write analysis reports that translate scientific results into decisions for a client’s stakeholders. The transfer turns out to be direct.

A typical bioinformatics deliverable buries the answer. It opens with “Methods,” walks through the pipeline, shows 15 figures, and arrives at a conclusion on page 22. The client’s VP skips to the last page, reads one paragraph with no context, and asks the project lead what it means. Everyone’s time wasted.

The pyramid fixes this. A report on differential expression analysis might look like:

• Situation: You asked us to identify gene signatures distinguishing responders from non-responders in your Phase II cohort.
• Complication: Standard bulk RNA-seq DE found 2,400 significant genes, too many to act on.
• Question: Which genes are worth validating?
• Answer: Three genes (X, Y, Z) survive all filters and have prior drug-target evidence.

The Key Line then gives three inductive reasons: each gene passes significance, replicates in an external cohort, and maps to a druggable target. Methods, QC, and sensitivity analyses go below the relevant Key Line point, not in a separate section at the top.

Two practical translations:

• Slide decks for client steering committees are natural pyramids. The title of each slide should be the conclusion (“Gene X replicates across cohorts”), not the category (“Replication analysis”). Minto calls these “headings that state ideas, not subjects.”
• MECE works well for structuring analysis results by question rather than by method. Don’t organize around “what we ran” (DE, enrichment, survival). Organize around “what we found” (response signature, pathway mechanism, clinical implication). Each finding gets its own branch, with methods as support underneath.

Where the pyramid breaks down

I’m less sure the framework fits exploratory scientific writing. A paper that says “we don’t know yet, but here are three promising directions” works as a pyramid. A paper that says “we found something unexpected and we’re not sure what it means” fights the “answer first” rule. Minto addresses this briefly in her “structureless situations” appendix, but it’s thin.

MECE also gets tricky in biology. Gene ontology terms are famously non-exclusive. Pathway databases assign the same protein to multiple pathways. Forcing MECE on inherently overlapping biology might produce clean slides but misleading science. The framework is a communication tool, not a classification system.

For any document where the goal is “the reader should understand my thinking in 30 seconds,” I haven’t found anything better.

The full map

I distilled the book into an interactive mindmap covering why the pyramid works (cognitive science), how to build one (SCQA, vertical/horizontal logic), the three rules every grouping must obey, and the problem-solving toolkit (MECE, logic trees, abduction). Hover for Minto’s original wording.

If MECE forces clean boundaries on your communication, what happens to the insights that live in the overlaps?