The Pyramid PrincipleWriting & Expression

When a reader opens a memo, an email, or a report, the first question in their mind is so what? Put that answer up front. Then unfold the reasoning. Don't write a memo like a detective novel where the killer is named on the last page.

Working memory is small (Miller's 7±2). When details come first, the reader has to hold them all in mind while guessing what they add up to — the cognitive load compounds. Answer-first writing hands the reader a map at the door, and every detail that follows hangs onto it. This is the same logic behind Amazon's six-page memo, McKinsey's SCR (Situation–Complication–Resolution), and the military's BLUF (Bottom Line Up Front).

• Use in: decision memos, leadership updates, the summary section of a technical RFC, the body of an email.
• Use whenever the reader is busier than the writer.
• Do not apply to: suspense narratives, fiction, literary essays that need to build emotion slowly.
• Soften when: the conclusion will trigger a strong emotional reaction — empathize first, then answer.

• Opening with paragraphs of background, with the recommendation buried on page three.
• Wasting the first sentence on "After careful analysis…" — that sentence is your most valuable real estate.
• Hiding the ask in a closing "next steps" line.
• Putting evidence first and treating the conclusion as an afterthought, so it lands weakly.
• Padding before the conclusion because it feels "abrupt." Trust the reader to handle directness.

Barbara Minto, The Pyramid Principle: Logic in Writing and Thinking (1978); Amazon S-Team Memo template (recommendation in Section 1).

The sub-points supporting an argument (the next level of the pyramid) must do two things: not overlap with each other, and together cover the problem. Otherwise the reader feels either "something is missing" or "aren't those the same thing?" — and trust drops.

MECE is not about looking tidy. It is a trust signal. When a reader sees "we'll look at this through three lenses — cost, benefit, risk," they can verify the coverage at a glance. But if you write "through finance, technology, and cost" — cost is a subset of finance — a quiet alarm goes off: maybe this writer hasn't thought it through. MECE is the visible trace of disciplined thinking.

• Use in: strategic analysis, root-cause diagnosis, options comparisons, user segmentation.
• Use whenever the argument requires exhausting the possibility space.
• Do not apply to: emotional narrative, personal essay (forced MECE feels mechanical).
• Skip in: fast-moving conversations where chasing perfect MECE would slow the decision.

• Mixing dimensions of cut (half by team, half by geography).
• Listing five reasons, two of which are the same thing in different words.
• Forgetting the "other / default" bucket — the categories don't actually cover everything.
• Splitting too finely, so the sub-items blur together.
• Closing with "and so on" — a tell that the writer didn't finish the thinking.

Barbara Minto, The Pyramid Principle, ch. 6 ("Imposing Logical Order"); Ethan Rasiel, The McKinsey Way (MECE in consulting practice).

You can build a pyramid in two directions. Top-down: fix the conclusion first, then find supporting points. Bottom-up: gather material, then induce a conclusion. The first is faster but risks premature closure. The second is slower but easier to get lost in. Mature writers use both: bottom-up to think, top-down to tell.

Bottom-up (group, then summarize) suits the exploration stage, when you don't yet know the answer and the data needs to speak. Top-down (hypothesis, then test) suits the expression stage, when you do know and you need it to land. The most common failure is using bottom-up to express — dumping the research process on the reader and asking them to assemble it themselves.

• Top-down: whenever you already know the conclusion and need it to land (about 90% of work communication).
• Bottom-up: exploratory research, user-interview synthesis, surveys of unfamiliar territory.
• Do not: hand the reader your bottom-up draft (unless they have explicitly asked for the process).
• Beware: closing top-down too early misses the counterintuitive finding hiding in the data.

• Submitting the research narrative as the deliverable ("first I did A, then B, then I noticed C…").
• Doing top-down with a foregone conclusion — bias dressed as analysis.
• Skipping bottom-up entirely; writing top-down on evidence you don't actually have.
• Mixing both structures inside one document, losing the reader.
• Showing the process to prove the workload. The reader cares only about the result.

Barbara Minto, The Pyramid Principle, ch. 4 ("Building a Pyramid Structure"); Paul Graham, "The Age of the Essay" (on the difference between the act of thinking and its presentation).

Minto proposed that the opening of any serious document should read like a miniature story: Situation (where we are), Complication (what changed), Question (what the change forces us to ask), Answer (your recommendation). The reader walks into a shared world, sees the disruption, feels the question rise naturally, and meets your answer ready to hear it.

A pure-conclusion opening can land too hard, with no setup. A pure-background opening drags. SCQA is the bridge between them. The situation is shared ground; the complication is the tension; the question is the hook the tension creates; the answer is the resolution you offer. This is the same load-bearing shape that runs through Aristotle's rhetoric, Hollywood three-act structure, and the opening of an Amazon six-page memo. Humans have been listening to that pattern since before writing existed.

• Use in: decision memos, proposals, the opening of a PRD, the opening of a quarterly review.
• Use whenever the reader needs to feel why now before they hear the answer.
• Do not apply to: pure status updates (weekly metrics don't need a story).
• Skip when: the message is short enough that SCQA would slow it down (Slack-length).

• Writing the situation as grand-context throat-clearing ("In this era of rapid AI advancement…") — empty.
• Manufacturing a complication where none truly exists.
• Posing a question that interests the writer but not the reader.
• Letting the SCQA sprawl across three paragraphs and lose its momentum.
• Treating SCQA as a fill-in-the-blank template instead of a shape — the language goes flat.

Barbara Minto, The Pyramid Principle, ch. 3 ("Why a Storylike Introduction?"); Amazon Working Backwards / PR-FAQ (the same storyshaped opening, applied to launches).