Executive Brief

Lead with the answer, back it with three points, make the ask specific and have the reader's questions answered before they raise them.

Practice, not research: answer-first writing is consulting craft from Minto's Pyramid Principle (Minto, 1981), widely taught and used, but no peer-reviewed test shows that briefs built this way are understood or approved more often. The page trains a habit, not a proven effect.

Use it when:

• You write an email or memo to a senior manager, a client or a board, and you need a decision, approval or help.
• You need a summary on top of a longer analysis, such as 2.10 Insight & Implications Sheet or 2.11 Options & Recommendations.
• You get one short chance to speak, such as a two-minute update in a leadership meeting.

Skip it when:

• You do not have an answer yet: structure the question first with 2.21 Issue Tree and MECE Check.
• The decision goes to a board with formal papers: use 8.16 Board Decision Prep Sheet.

The claim behind this page is a craft claim. A busy reader should meet the conclusion first and the reasoning second, because they read to decide, not to follow your process. Minto (1981) built a method on that idea. A message is a pyramid: one governing thought at the top, a few points that support it, and evidence under each point. The opening that leads into the answer follows a fixed path in the same tradition: the situation the reader already accepts, the complication that changed it, and the question that complication raises. Once the reader has the answer in the first lines, every later line becomes support they can check, not suspense they must sit through.

The limits are as clear. No controlled test of the pyramid exists (see the Minto research card), so treat it as discipline, not as a persuasion technique. Answer-first assumes you have an answer; if you do not, the honest brief says so. And a tidy page can carry a weak finding very confidently, which is why Step 3 asks for the evidence behind each point.

Write who reads it, where they stand today, and the exact action you need, from whom and by when.

Strong answer: "Reader: the head of customer service, who believes Monday queues are a staffing problem. Ask: approve a rewrite of the weekend billing message by Friday, so it can be live before the next billing cycle." Not: "Ask: some support with the queue issue."

Who reads this, and what they already know and believe about it:

Exactly what I am asking for (action, from whom, by when):

Why then:

What happens if we do nothing:

Illustrative example: the organization, the roles and all numbers are made up.

A customer support specialist at a regional energy company in Sweden has spent two weeks looking at why phone queues spike every Monday. She is not a manager, and the head of customer service has ten minutes a week for requests like hers.

Step 1: The reader believes the queues are a staffing problem. The ask: approval by Friday to have the communications team rewrite the weekend billing message, and to track Monday queue time for four weeks.

Step 2: Situation: Mondays carry the longest queues and already get extra staff. Complication: the extra staff have not helped, and most callers in her sample ask about the same weekend billing message.

Step 3: Answer: rewrite the message and test it for four Mondays, medium confidence. Points: the calls cluster on one topic; three colleagues read the message three different ways; a rewrite costs a few hours once, while extra staffing recurs every week.

Step 4: "What if the queue does not drop?" Then the topic was a symptom, and four weeks of data narrow the next search.

The head of customer service approved it in a two-line reply. The brief worked because the answer and the ask were in the first five lines.