CaseClimbThis guide shows you how to write emails, memos and slides that a senior reader can act on in the first thirty seconds. You will get the method in plain terms, a full rewrite of a status email, the same logic applied to a deck, and the mistakes that most often undo it.
The pyramid principle in plain terms
The pyramid principle is a way of ordering a message. You lead with the answer, group the supporting points beneath it, and order those points so the reader can follow the logic. Barbara Minto developed it at McKinsey, and her book, The Pyramid Principle, sets it out in full.
The name comes from the shape. One idea sits at the top. Under it sit a small number of ideas that support it, and under each of those sit the facts that prove them. A reader can stop at any level and still leave with the main point.
Most people write in the opposite order. They start with background, walk through what they did, and reach the conclusion in the final paragraph, the order in which they did the thinking. The pyramid asks you to do the thinking in that order and then present it upside down.
Senior readers want the answer first
Think about the reader's day. A director reads dozens of emails between meetings, often on a phone, and opens each one wanting to know what you need from them. If that is in the first two lines, they can act, delegate or file it. If it sits in paragraph four, they read on with growing impatience or put it aside until next week.
From the manager's side of the desk, junior team members tend to write in time order so the effort is seen, while senior readers care about the effort only as far as it supports a decision. You also show confidence when you lead with the answer: you have done the analysis and you are prepared to commit to a view. If the view is wrong, the reader can challenge it in one reply.
The structure: one governing thought, a few supporting points
A pyramid has four working parts.
- Governing thought: the one sentence you want the reader to remember. It is a conclusion or recommendation that someone could disagree with. "Project update" is a topic. "The launch will slip two weeks unless we approve extra testing budget by Friday" is a governing thought.
- Supporting points: two to four reasons, actions or findings that together justify the governing thought. Each one is a full sentence that makes a claim.
- Evidence: the data, examples and facts under each supporting point. The reader goes down to it only if they doubt the point above.
- MECE grouping: the supporting points are mutually exclusive and collectively exhaustive. They do not overlap, and taken together they leave no gap in the argument.
MECE is the part people skip. If two of your points overlap, the reader counts the same reason twice and starts to distrust the rest. If there is a gap, the reader will find it with their first question. The same discipline sits behind a good case structure, covered in how to structure a case interview.
Keep to two to four supporting points: five or more means you have not grouped them yet, and most readers lose track after the fourth. Pick one ordering logic for each level and keep to it: time order, structural order (by region, product or process step), or order of importance. If you mix orders within one level, the reader loses the thread without knowing why.
A status email, before and after
Take a typical project update from a team lead to a director.
"Hi Sarah, a quick update on the supplier migration. Over the last two weeks the team has worked through the data cleansing for the new platform, and we have now finished about 80 percent of the vendor records. We ran into some issues with the legacy codes from the Lyon site, which took longer than planned, and Tom has been working with their finance team to resolve them. We also had the user acceptance testing workshop on Tuesday, which went well overall, although procurement raised a few concerns about the approval workflow that we are now looking into. On the timeline, we are still aiming for go-live on 3 November, but this depends on getting the remaining records cleaned and on the workflow fix. It would help to have one more analyst for two weeks if possible. Let me know if you have any questions. Thanks, James"
The same content, rewritten answer-first.
"Hi Sarah, I need your approval by Thursday to borrow one analyst for two weeks. Without one, go-live moves from 3 November to 17 November. (1) Data cleansing is 80 percent done. The remaining records are legacy codes from the Lyon site, and Tom is resolving them with their finance team. (2) Testing went well, with one open issue: procurement flagged the approval workflow, and we have scoped a three-day fix. (3) An extra analyst lets us run both pieces of work in parallel and hold 3 November. Happy to talk it through for five minutes after your 2pm. James"
The change, in one line: the ask and its consequence moved to the top, the three supporting points are grouped and numbered, and the story of the fortnight is gone because Sarah did not need it. Sarah can reply "yes" from her phone, and if she wants to push back, she knows which point to push on.
The same logic in a slide deck
A deck is a pyramid laid out across pages. The title of each slide carries one supporting point, and the body of the slide holds the evidence for it. Consultants call these action titles: full sentences that state the point of the slide. Topic titles such as "Market overview" or "Q3 results" name the subject and leave the reader to find the point.
The test is the storyline read. Copy the slide titles into one document and read them top to bottom. If they make a coherent argument on their own, the deck works. If you need the charts to follow the argument, rewrite the titles until you do not. A short deck for a leadership team on a pricing decision might carry these five titles.
- We should raise list prices 4 percent in January and protect our top 50 accounts with a one-year price lock.
- Our input costs have risen faster than our prices for three years, and margin has fallen in each of them.
- Competitors raised prices this year and our win rate held, so we expect customers to accept a moderate increase.
- The top 50 accounts produce most of our profit and are the most likely to switch, so a price lock for them limits the risk.
- We can roll out the change in eight weeks if sales and finance agree the account list by the end of this month.
Read those five lines and you have the meeting. Slide one is the governing thought, slides two to four are the supporting points, and slide five turns the recommendation into a plan.
Opening with situation, complication, question
Answer-first works best if the reader already knows why you are writing. Sometimes they do not: a new stakeholder, a board paper, a memo on a problem the reader has not heard about. For those cases the pyramid has a standard opener in three short moves, known as SCQ (situation, complication, question).
- Situation: a fact the reader already accepts. "We moved customer support to the new ticketing system in June."
- Complication: the change that creates a problem. "Since then, average response time has doubled and complaints to account managers have tripled."
- Question: the question this raises in the reader's mind, often left implied. "What should we do before the renewal season?"
Then you give the answer, and the pyramid continues as normal. Keep each part to a sentence or two. The SCQ is a run-up to the answer, and if the run-up stretches to a page, you are back to the meandering email.
Common mistakes
- Burying the ask. The request sits in the last paragraph, after the reader has stopped reading. If you need a decision, a budget or a reply by a date, put it in the first line and repeat it at the end.
- Topic titles instead of point titles. With slides headed "Customer feedback" or "Next steps", you leave the reader to work out the point. Write the conclusion of the slide as its title, in a sentence.
- Too many supporting points. To you, seven reasons feel thorough. To the reader they look like an unsorted list. Group them into three or four, and if one fits no group, ask whether it belongs in the message at all.
- A governing thought that is a topic. "Update on Q3" offers the reader nothing to agree with. "Q3 will land 5 percent under budget, and we have a plan to recover half of it in Q4" does.
Most of these come from writing in the order you worked. Write the governing thought as a single sentence before you draft anything else. If you cannot write that sentence, the problem sits in the thinking, and formatting will not fix it.
Case practice trains the same habit
Case interviews test this skill under time pressure. At the end of a case, the interviewer asks for a recommendation, often framed as the client's chief executive walking in with two minutes to spare. Candidates who score well open with the answer, give two or three reasons, name the main risk and propose next steps. Candidates who struggle replay the case in the order they solved it.
That closing is a spoken pyramid, and you can work through it step by step in the guide to the case recommendation. People who have practised dozens of cases tend to write better emails afterwards, having rehearsed the move from analysis to answer against the clock. In the case trainer, you end each case with a recommendation.
Common questions
Can answer-first feel rude to some readers? In some cultures and organisations a direct opening can feel abrupt. Keep the answer first and adjust the tone around it. A line of courtesy before the answer costs nothing, while a paragraph of preamble costs the reader's attention.
What if I do not have the answer yet? Then your governing thought is your current best view, or the decision you need in order to reach one. "We do not yet know why churn rose; we will have the answer by Friday once the cohort data is in" is a valid top line. The reader learns where things stand and when to expect more.
Does the pyramid work for long reports? Yes. A report has the same shape at greater depth: an executive summary with the governing thought and supporting points, then one section per point, each opening with its own conclusion.
How do I get my team to write this way? Ask for the one-sentence answer before you read any draft. If they cannot give it, the draft is not ready. Within a few weeks, most people write that sentence first.
If your team writes for senior readers and you want to build this habit through structured practice, see how CaseClimb works for companies.
