Executive-Summary Discipline

Overview

The executive summary — the one-page or one-slide distillation of a recommendation — is not attributed to a single originator. It is a communication discipline embedded in consulting firm training, military briefing standards, and executive communication best practices. What distinguishes a great executive summary from a mediocre one is not the template used but the quality of synthesis it represents.

Two principles from different traditions converge here. Barbara Minto's Pyramid Principle (see that page) establishes the structural logic: lead with the governing thought, support it with grouped arguments, provide evidence at the base. Jeff Bezos's Amazon writing culture, formalized through the company's "six-pager" memo format and the insistence on complete sentences and full reasoning, represents a different application of the same underlying discipline: clear writing is clear thinking made visible. Bezos famously banned PowerPoint bullet points at Amazon leadership meetings, replacing them with narrative memos that demonstrate genuine understanding rather than the appearance of it.

The military's BLUF (Bottom Line Up Front) standard — used in intelligence reporting, situation updates, and operational briefings — reflects the same principle: the most important information leads. The reader's most valuable resource is attention, not time, and that attention should be spent on the recommendation and its implications, not on working through a buildup to eventually get there.

What belongs in an executive summary:

• The recommendation: stated plainly and specifically in the first sentence. Not "we analyzed the situation and present our findings" — "you should do X."
• The situation and complication: the minimum context required to understand why the recommendation is the right one now. One to two sentences.
• The supporting logic: 2–4 key arguments that justify the recommendation. Each should be a complete thought, not a topic label. Together, they should be sufficient to accept the recommendation without needing to read the full deck.
• The ask or next step: what decision or action is required from the reader? Be explicit.

What does not belong:

• Background the audience already knows
• A summary of the analytical process ("we looked at three frameworks...")
• Hedged language that avoids committing to a recommendation
• Supporting detail that belongs in the appendix

When to Use It

Any time a recommendation is being delivered to a senior audience with limited time and high stakes. The executive summary disciplines are most important when the recommendation is complex (many inputs, competing considerations), when the audience is skeptical, or when the decision the recommendation enables is irreversible or costly. In a Consulting Club session, the 10-minute recommendation presentation is, in effect, an executive summary delivered verbally — the same rules apply.

How It Works

1. Write the governing thought first — before the context, before the supporting arguments, write the recommendation in one sentence. This is the hardest step: it forces clarity about what you actually think. If you can't write it in one sentence, you don't yet know what you think.
2. Add the minimum necessary context — what does the reader need to know to understand why this recommendation is the right one now? No more than that.
3. Build the supporting argument — identify the 2–4 key reasons the recommendation is correct. Write each as a complete sentence that stands on its own. These are the logical scaffolding. Ask: "If I were a skeptic, which of these would I push back on hardest?" — that's the one that needs the most support.
4. State the ask — what do you need from the reader? Approval to proceed? A decision between two options? Resources? Name it explicitly.
5. Cut ruthlessly — remove anything the audience could have assumed, anything that doesn't directly support the recommendation, and anything that hedges instead of committing. The executive summary is done when you can't remove anything without weakening the recommendation.
6. Read it as a skeptic — does the recommendation follow logically from the context? Does the supporting logic actually support the recommendation, or does it just describe a situation? Would a reasonable person who only read this page be able to act on it?

Common Pitfalls

• The context-heavy opening — spending so long on background that the audience's attention is exhausted before the recommendation arrives; assume the audience knows more than you think they do
• The non-recommendation — "based on our analysis, the company should consider exploring potential options in this space" is not a recommendation; it's a hedge; commit to something specific
• The list of findings — presenting what you found is not the same as recommending what to do; every finding should connect explicitly to the recommendation it supports
• The appendix in the summary — including supporting detail that belongs in the backup; the executive summary earns the right to skip ahead; don't take it back by padding
• False balance — presenting pros and cons of multiple options without recommending one; a decision-maker who asked for a recommendation did not ask for a menu

Recommended Books

• The Pyramid Principle — Barbara Minto
• The McKinsey Mind — Rasiel & Friga
• On Writing Well — William Zinsser