Apply Pyramid Principle

---
name: apply-pyramid-principle
description: Use when writing a business document, memo, email, or presentation where the reader needs to understand a recommendation or conclusion quickly.
source: 'Barbara Minto, "The Minto Pyramid Principle: Logic in Writing, Thinking and Problem Solving", 1987 (Minto International)'
tags: [communication, executive-writing, structured-thinking, writer, comprehension-speed, persuasion]
verified: true
---

# Apply Pyramid Principle

Lead with the answer, then support it with grouped, ordered reasoning — never make the reader wait for the conclusion.

## Why This Is Best Practice

**Adopted by:** McKinsey & Company (where Minto developed it — required training for
all associates and consultants), BCG, Bain, Goldman Sachs, Morgan Stanley, Deloitte.
Harvard Business School includes it in core curriculum. Standard for all client-facing
deliverables in top-tier consulting and investment banking globally for 50+ years.
**Impact:** Top-down structure cuts time-to-comprehension because readers get the
conclusion before processing supporting detail — the brain can file each argument
under a known conclusion rather than holding uncertainty in working memory.
Bottom-up writing (conclusion last) forces readers to re-read once the conclusion
arrives. McKinsey measures communication quality on this framework in internal reviews.
**Why best:** Most writers default to bottom-up (chronological story → conclusion)
because that's how thinking unfolds. But readers are not interested in the writer's
thinking process — they want the answer. Pyramid Principle forces the discipline of
separating thinking order from communication order.

Sources: Barbara Minto, "The Minto Pyramid Principle" (1987); McKinsey & Company
internal writing standards; Harvard Business School MBA core curriculum

## Structure

```
          [Governing Thought — the single answer]
               /           |           \
        [Key Point 1]  [Key Point 2]  [Key Point 3]
         /      \         |           /       \
      [Data]  [Data]   [Data]     [Data]    [Data]
```

Every level answers the question raised by the level above it.
The governing thought answers: "So what should I do/know/think?"
Key points answer: "Why?" or "How?"
Supporting data answers: "How do you know?"

## Steps

### 1. Define the governing thought

Write the single sentence that is your entire message.
If forced to telegram the document, this is the telegram.

```
Bad:  "There are several factors affecting our Q3 performance..."
Good: "We should exit the German market by Q4 to stop the cash drain."
```

This goes at the top — title, subject line, or opening sentence. Never at the end.

### 2. Use SCQA to open (for resistant or uninformed audiences)

When the reader doesn't yet accept the problem framing, use SCQA before the governing thought:

- **Situation:** Shared context the reader already knows (1–2 sentences)
- **Complication:** What changed or what problem emerged
- **Question:** The question the complication raises (implicit or explicit)
- **Answer:** The governing thought — your recommendation

```
Situation:   Our German operations have grown to €12M revenue over 5 years.
Complication: The market requires 3× our current investment to reach profitability,
              and two local competitors have locked up the top three accounts.
Question:    Should we continue investing or redirect resources?
Answer:      We should exit Germany by Q4 and redeploy capital to the UK expansion.
```

Skip SCQA when the reader already accepts the problem — go straight to the answer.

### 3. Group key points (MECE)

Supporting points must be:
- **Mutually Exclusive** — no overlap between points
- **Collectively Exhaustive** — together they fully support the governing thought

```
Bad grouping (overlapping):
  - Cost is too high
  - Margins are too low        ← same problem, two framings
  - Revenue doesn't cover costs ← same again

Good grouping (MECE):
  - Unit economics are structurally negative (cost > price ceiling)
  - Market share is unwinnable (top accounts locked by incumbents)
  - Capital requirement exceeds strategic value (3× invest for 15% share)
```

Aim for 3–5 key points. Fewer than 3 feels thin; more than 5 overloads working memory.

### 4. Order points logically

Choose one ordering principle and apply it consistently within each level:

| Order type | When to use | Example |
|------------|-------------|---------|
| **Deductive** | One argument flows from the previous | Major premise → minor premise → conclusion |
| **Chronological** | Steps or phases | Step 1 → Step 2 → Step 3 |
| **Structural** | Physical or org components | North region, South region, West region |
| **Importance** | Independent parallel points | Most critical → least critical |

Don't mix ordering types within the same group.

### 5. Check the "So what?" test

Read each level and ask: "So what does this mean for the level above?"
If the answer isn't already in the document, the logic is incomplete.

```
Data:     "Customer churn increased 8% in Q3."
So what?  "Our retention problem is accelerating." ← this must appear as a key point
So what?  "We must fix retention before expanding." ← this must appear at governing thought
```

### 6. Apply to format

| Format | Pyramid location |
|--------|-----------------|
| Email | Subject line = governing thought; first paragraph = key points |
| Memo | Title + opening paragraph = governing thought + SCQA; sections = key points |
| Slide deck | Title slide = governing thought; each slide title = key point (not topic) |
| Verbal briefing | First sentence = governing thought; then key points with evidence |

Slide titles must be assertions, not topics:

```
Bad title:  "Market Analysis"
Good title: "German market cannot reach profitability within our investment horizon"
```

## Rules

- **Answer first, always.** Never write "After reviewing all options, we recommend…" — the recommendation comes before the review.
- **One governing thought per document.** Two governing thoughts = two documents.
- **Key points must be the same kind of thing.** Mixing reasons with actions with risks in the same group violates MECE and confuses readers.
- **Data never appears at the key point level.** Raw facts belong at the bottom. Key points are interpretations, not observations.
- **SCQA is optional.** Use it only when context-setting is genuinely needed. Overusing it buries the answer.

## Common Mistakes

**Bottom-up structure.** "We analyzed X, then Y, then Z, and therefore we recommend…"
The reader waited through the entire analysis to get the answer. Invert it.

**Topic slide titles.** "Revenue Trends" tells the reader nothing. "Revenue growth is
decelerating and will miss target by 15%" tells them everything before they read the chart.

**Non-MECE groupings.** Two key points that overlap confuse readers and signal fuzzy thinking.
If points overlap, merge them or find the higher-level point they both support.

**Governing thought too vague.** "We need to improve our go-to-market approach" is not
a governing thought — it's a topic. "We should hire three enterprise sales reps in H1
to capture the mid-market segment before the competitor launches" is a governing thought.

## When NOT to Use

- **Exploratory documents** where the conclusion is genuinely unknown — use a structured problem-solving framework instead, then apply Pyramid when writing up findings
- **Chronological narratives** (postmortems, case studies) where the story structure is the point
- **Emotional or sensitive communications** (feedback, difficult news) where leading with the conclusion feels abrupt — use SCQA to build context first, or consider a different format entirely
- **Creative writing** — narrative tension depends on withholding the conclusion