# Pyramid Principle > Structure writing and thinking using Barbara Minto's Pyramid Principle — lead with the answer, group supporting ideas, and open with a Situation-Complication-Question-Answer story. Use this skill whenever the user is writing or restructuring a memo, report, email, executive summary, recommendation, proposal, board update, slide deck, or any document where the order of ideas matters; whenever they ask how to organize, structure, or sequence their thinking; or whenever they say things like "make this clearer," "bottom line up front," "BLUF," "this is rambling," "tighten this up," "what's my main point," or "how should I lay this out." Also trigger for consulting-style deliverables, problem analysis, and any time a wall of points needs to become a clear argument. - Skill: `jordangaston/pyramid-principle` (Agent Skill, multi-file: 6 files) - Install (CLI): `npx skillmds@latest add jordangaston/pyramid-principle` - Raw SKILL.md: https://api.skillmd.com/api/skills/jordangaston/pyramid-principle/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: jordangaston (https://skillmd.com/u/jordangaston) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/jordangaston/pyramid-principle --- # The Pyramid Principle ## Overview Barbara Minto's *Pyramid Principle* is the standard method (developed at McKinsey) for ordering ideas so a reader grasps them fast. The core claim: readers absorb ideas most easily when they arrive **top-down** — the single main point first, then the groups of ideas that support it, then the detail beneath those. Writers, however, usually think **bottom-up**. The skill is converting bottom-up thinking into top-down delivery. A document is well-structured when its ideas form a **pyramid**: one governing thought at the top, supported by a small number of grouped ideas, each in turn supported by ideas below them. ## When to Use This Skill Use it for any writing where the sequence of ideas affects whether the reader "gets it": memos, reports, emails, executive summaries, recommendations, proposals, board/investor updates, strategy docs, slide decks, and consulting deliverables. Also use it when restructuring rambling prose, when someone asks "what's my main point," or when a pile of observations needs to become an argument. **If the task is to make thinking land clearly with a reader, use this skill.** ## The Core Workflow When helping someone structure a piece of writing, work in this order: 1. **Find the answer first.** What is the single main point — the one sentence the reader must remember? This goes at the top of the pyramid (and near the top of the document). If the answer isn't clear yet, you're not ready to write; build bottom-up (see `references/building-pyramids.md`). 2. **Write the introduction as a story, not a preamble.** Use **Situation–Complication–Question–Answer (SCQA)**. This is the single highest-leverage move; details and variations in `references/introduction-scqa.md`: - **Situation** — context the reader already accepts as true (uncontroversial). - **Complication** — what changed or went wrong, which raises a question. - **Question** — the question now live in the reader's head. - **Answer** — your governing thought, which answers that exact question. 3. **Support the answer with one grouping of ideas** that answers the question "why / how / which?" raised by the answer. Keep groupings small (ideally 3–5 items). 4. **Enforce the three rules** on every grouping (see below). 5. **Order each grouping logically** — by time, structure, or degree (see `references/ordering-and-grouping.md`). 6. **Run the "So what?" test** on every summary line. A summary must state the *insight*, not just label its contents (see below). 7. **Reflect the pyramid in the prose** — headings that mirror groupings, transitions that carry the Q&A logic, the answer stated up front in each section (see `references/reflecting-in-writing.md`). ## The Three Rules of a Pyramid Every grouping in the pyramid must obey all three. When a structure feels off, one of these is almost always being broken: 1. **Ideas at any level summarize the ideas grouped below them.** A parent box is the distilled point of its children — not a category label, but the conclusion they add up to. 2. **Ideas in each grouping are the same kind of idea.** All reasons, or all steps, or all problems, or all components — never a mix. If you can't give the group a single plural noun ("three *reasons*," "four *steps*"), it isn't a clean grouping. 3. **Ideas in each grouping are logically ordered.** There must be a deliberate reason for the sequence (chronological, structural, or by importance). If you can't name the ordering principle, the grouping isn't fully thought through. ## Vertical and Horizontal Logic Two relationships hold a pyramid together: - **Vertical (Question/Answer):** Each box raises a question in the reader's mind that the boxes directly below it answer. This dialogue is what keeps a reader engaged and guarantees every point is relevant — if a point doesn't answer the question its parent raises, it doesn't belong. - **Horizontal (deduction OR induction):** The ideas in a single grouping relate to each other in one of two ways. **Induction** (group similar ideas, then state what they imply) is clearer for most business writing and should be the default. **Deduction** (premise → premise → therefore) is sometimes unavoidable but is harder to read past the top level. Don't mix the two within one grouping. Full treatment in `references/ordering-and-grouping.md`. ## The "So What?" Test (the most common failure) The most frequent weakness is an **intellectually blank summary** — a heading or top line that names a category instead of delivering a point. Always push past it: - Weak: "The company has three problems." (So what? What do they add up to?) - Strong: "The company is losing its three most profitable accounts because service has collapsed since the reorg." For a grouping of **actions/steps**, the summary states the *result* of taking them. For a grouping of **situations/findings**, the summary states the *implication* they share. If a summary line could sit above almost any list, it's blank — rewrite it to say something only this list could support. ## Top-Down vs Bottom-Up - **Top-down** (use when you already know the answer): start the SCQA, state the answer, then lay out the supporting grouping. Faster and cleaner. - **Bottom-up** (use when the answer isn't clear yet): list every point, sort them into same-kind groups, order each group, then write the summary line each group forces — that line, raised one more level, is your answer. Step-by-step procedures and a full worked example are in `references/building-pyramids.md`. ## Reference Files Read the relevant file when the task calls for depth — don't load them all by default: - **`references/introduction-scqa.md`** — The SCQA introduction in depth: the four standard orderings (standard, direct, concerned, aggressive), how long it should be, what to include and exclude, and worked openings for an email, a memo, and an exec summary. - **`references/ordering-and-grouping.md`** — Logical ordering (time / structure / degree), MECE, and deduction vs. induction with examples and the rules for choosing between them. - **`references/building-pyramids.md`** — The detailed top-down and bottom-up procedures, plus a complete before/after worked example turning a rambling memo into a pyramid. - **`references/problem-solving.md`** — The analytical half of the book: defining a problem (Starting Point → Disturbing Event → R1 → R2), diagnostic frameworks, and MECE logic/issue trees. Use this when the task is *analysis* (figuring out the answer), not just writing it up. - **`references/reflecting-in-writing.md`** — Turning a finished pyramid into prose or slides: headings, transition sentences, section-level mini-introductions, visual hierarchy, and common pitfalls. ## Quick Self-Check Before calling a structure done, verify: - [ ] The main point (answer) is stated up front, not buried in a conclusion. - [ ] The introduction tells an SCQA story the reader will nod along to. - [ ] Every grouping is same-kind ideas with a clear ordering principle. - [ ] Every summary line passes the "So what?" test. - [ ] Every supporting point actually answers the question its parent raises.