Writing for Decision Makers: Getting to Yes in 500 Words or Less
Jeff Bezos banned PowerPoint presentations at Amazon in the early 2000s. In their place, he required six-page narrative memos read silently at the beginning of every meeting. The reasoning was simple: slides encourage hand-waving and bullet-point-level thinking. Structured prose forces the author to think clearly and the reader to engage deeply.
But here is the part most people miss about the Amazon memo format: the most important element is the first page. Senior leaders at Amazon often read only the first page of a six-page memo -- the executive summary and recommendation. If the first page does not compel them, the remaining five pages go unread.
This is the fundamental reality of writing for decision makers: you have one page, often one paragraph, to communicate your point. Everything else is supporting evidence that decision makers may or may not consult.
What Decision Makers Actually Need
Decision makers -- executives, senior leaders, board members, investors, clients with authority -- operate under extreme time constraints. A typical senior executive at a Fortune 500 company processes 200-300 emails per day and attends 20-30 meetings per week, according to a 2018 Harvard Business School study by Michael Porter and Nitin Nohria that tracked 27 CEOs' daily schedules.
What they need from written communication:
- What decision you are asking them to make -- explicitly stated
- What you recommend -- your conclusion, not just options
- Why it matters -- the business impact of acting and the cost of not acting
- What resources it requires -- time, money, people
- What the risks are -- honestly assessed
- What you need from them -- specific next step
What they do not need:
- Your analysis methodology
- Background they already have
- Comprehensive review of every alternative
- Your journey to the recommendation
- Detailed implementation plans (unless they ask)
Example: Andy Grove, legendary CEO of Intel, reportedly returned a five-page memo from an engineer requesting $5 million for a new fabrication process with a single note: "Tell me what you want me to do and why, in the first paragraph. I'll read the rest if I need to."
The BLUF Principle: Bottom Line Up Front
The single most important technique for writing to decision makers is BLUF -- a concept from U.S. military communication doctrine, codified in Army Regulation 25-50. State your conclusion first. Then provide the reasoning.
Why Most Professionals Write Backwards
Academic training teaches a build-up structure: introduce the topic, review the literature, present the methodology, show the results, and conclude. This structure is logical for building an argument from scratch. It is terrible for people who need to make decisions quickly.
The build-up structure forces the reader to consume everything before discovering your point. Decision makers will not do this. They will skim, guess at your conclusion, or ignore the document entirely.
The BLUF Structure in Practice
Opening paragraph (the only paragraph some readers will see):
I recommend we migrate our production infrastructure to AWS by September 30. This will reduce hosting costs by 30% ($150K annually) and eliminate the capacity constraints that caused two revenue-impacting outages in Q1. The migration requires 8 weeks of engineering effort, a $20K budget, and your approval by March 15.
Supporting section 1 -- Why this matters:
Current infrastructure cannot handle projected Q4 traffic. Two Q1 outages cost $80K in lost revenue and damaged client relationships with three enterprise accounts.
Supporting section 2 -- Options evaluated:
We assessed three approaches: expand on-premise (higher long-term cost), hybrid cloud (moderate savings but full complexity of both), and full migration (best cost-risk-simplicity balance).
Supporting section 3 -- Risks and mitigation:
Primary risk: performance regression during migration. Mitigated by parallel testing over 3 weeks before cutover.
Final line -- The specific ask:
Please approve the $20K budget allocation by March 15 so we can begin April 1 and complete by September 30.
Example: Barbara Minto, a former McKinsey consultant, developed the Pyramid Principle in 1987 -- the framework that has been standard at McKinsey and other top strategy firms for decades. The core idea: answer first, group supporting arguments logically beneath, provide evidence only for what requires proof. Her book remains required reading for new consultants at most major firms.
Structuring Executive Summaries That Get Read
An executive summary must stand alone as a complete communication. If the reader never opens the full document, they should still be able to make an informed decision from the summary alone.
The Anatomy of an Effective Summary
Sentence 1: State the recommendation or decision needed.
Sentences 2-3: The primary supporting reasons, quantified.
Bullet points (4-6): Essential context -- options considered, resources required, timeline, key risks, impact of inaction.
Final sentence: The specific action you need and by when.
Total length: Half a page to one full page. Never more.
The Test
Read only your executive summary. Can someone who has no other context about this project understand what you are recommending, why, and what they need to do? If they need to read the full document to grasp the basics, the summary has failed.
Common Summary Failures
Starting with background: "Our company has been using on-premise servers since 2015..." -- the reader already knows this. Start with the recommendation.
Vague language: "We propose a significant improvement to our infrastructure" -- significant by how much? Which infrastructure? What does "improvement" mean?
No decision requested: A summary that reads as purely informational when it actually seeks approval leaves the reader uncertain whether action is required.
Too long: If the executive summary is two pages, it is not a summary. It is the document in miniature, and you have merely shifted the reading burden rather than eliminating it.
The Art of Quantification
Decision makers think in numbers. Every qualitative claim should be accompanied by or replaced with a quantitative one.
| Instead of this | Write this |
|---|---|
| "Significant cost savings" | "$150K annual reduction (30%)" |
| "Improved performance" | "Page load time from 4.2s to 1.1s" |
| "Faster time to market" | "6 weeks instead of 14 weeks" |
| "High risk" | "3 of 5 similar projects failed in the past 2 years" |
| "Better customer experience" | "NPS increase from 32 to 58; complaint tickets reduced 60%" |
| "We'll need resources" | "2 senior engineers for 8 weeks plus $20K in tooling" |
When exact numbers are unavailable, provide ranges:
"We estimate 15-25% cost reduction based on benchmarks from three comparable migrations at companies A, B, and C."
Ranges are more credible than false precision and infinitely more useful than qualitative statements like "significant."
Example: McKinsey engages are structured around "impact sizing" -- every recommendation must quantify the expected financial impact before it is presented to the client. Consultants who present recommendations without numbers are sent back to develop them. This discipline ensures that recommendations are concrete enough to act on.
Writing Recommendations That Build Confidence
A recommendation is not a suggestion. It is a specific proposed action, backed by reasoning, that invites a yes-or-no decision.
The Components of a Compelling Recommendation
1. Explicit position: "I recommend..." not "We might consider..." or "One option would be..."
2. Evaluation criteria shown: "We evaluated options against cost, implementation timeline, risk, and strategic alignment."
3. Alternatives addressed: "We considered three alternatives. Option B was close but lacks scalability."
4. Objections preempted: "The main concern is vendor lock-in. We mitigate this through containerized architecture portable across providers."
5. Uncertainties acknowledged: "We have not yet confirmed data transfer pricing. We expect $3K-$8K based on published rates."
6. Evidence provided: "Based on our proof-of-concept last month, we are confident in timeline and cost estimates."
7. Clear ask: "Please approve by March 15."
The goal is to make the reader think: "This person has done their homework, understands the risks, and has a clear point of view." That confidence enables fast decisions.
Adapting to Different Decision-Making Styles
Not all decision makers process information the same way. Knowing your audience's style is as important as the content.
The Reader: Wants thorough written analysis digested on their own time. Send the document 24-48 hours before the meeting. Do not present slides.
Example: Jeff Bezos is famously a Reader. The six-page memo format exists because Bezos believes reading forces deeper engagement than listening to a presentation.
The Interrogator: Decides by stress-testing your reasoning through questions. Prepare for tough challenges. Have supporting data ready but not in the main document -- bring it for Q&A.
Example: Steve Jobs was an Interrogator. Employees at Apple learned to anticipate his questions and prepare exhaustive supporting analysis that lived behind the presentation, ready to be pulled up on demand.
The Data-Driven: Wants numbers, benchmarks, and evidence. Quantify aggressively. Include comparisons to industry standards or past projects. Anecdotes without data are unconvincing.
The Intuitive: Decides quickly based on pattern recognition. Frame your recommendation as an extension of patterns they already believe in. "This is similar to our successful Q2 initiative, scaled to the enterprise segment."
The Consensus Builder: Wants to know that key stakeholders have been consulted and support the recommendation. Include a section on "stakeholder alignment" noting who has reviewed and endorsed the proposal.
The Difference Between Writing for Executives and Writing for Technical Teams
The same project often requires two entirely different documents.
For executives: Organize by business impact. Lead with ROI. Use business language. Minimize technical detail. Focus on "what" and "why."
For technical teams: Organize by architecture and implementation. Lead with technical approach. Use precise terminology. Include edge cases. Focus on "how."
An executive document that says "We will migrate to a microservices architecture using Kubernetes on AWS" communicates nothing useful to the executive and wastes their time on implementation details. An executive document that says "The migration will reduce costs by $150K annually, improve reliability from 99.5% to 99.99%, and enable us to scale for the enterprise segment" communicates everything they need.
For related guidance on clear communication, see our article on effective professional communication practices.
The Five Most Common Mistakes
1. Burying the recommendation. Three pages of context before "Therefore, I recommend..." guarantees the recommendation will not be read.
2. Presenting options without a preference. "Here are five options" pushes analysis work to the person with the least time. Have a point of view.
3. Using passive voice. "It was decided that..." -- by whom? "Mistakes were made..." -- by whom? Decision makers notice evasion.
4. Including everything you know. Your full analysis belongs in an appendix. The executive communication contains only what the decision requires.
5. Forgetting the "so what." Every fact should connect to the decision. If removing a paragraph would not change the recommendation, remove the paragraph.
The One-Minute Test
Before sending any communication to a decision maker, apply this test: Can someone read only the first paragraph and understand (a) what you recommend, (b) why, and (c) what you need from them?
If yes, the communication is ready.
If no, rewrite until the answer is yes. Then the rest of the document becomes optional supporting material that the reader can engage with if they want to, rather than mandatory reading that stands between them and your point.
Respect their time. Lead with your conclusion. Be specific. Ask for what you need.
References
Minto, B. "The Pyramid Principle: Logic in Writing and Thinking." Pearson Education, 2009.
Porter, M. E. & Nohria, N. "How CEOs Manage Time." Harvard Business Review, 2018. https://hbr.org/2018/07/how-ceos-manage-time
Bryar, C. & Carr, B. "Working Backwards: Insights, Stories, and Secrets from Inside Amazon." St. Martin's Press, 2021.
Duarte, N. "Resonate: Present Visual Stories that Transform Audiences." Wiley, 2010.
Heath, C. & Heath, D. "Made to Stick: Why Some Ideas Survive and Others Die." Random House, 2007.
Zelazny, G. "Say It with Charts: The Executive's Guide to Visual Communication." McGraw-Hill, 2001.
Garner, B. A. "Legal Writing in Plain English." University of Chicago Press, 2013.
Williams, J. M. & Bizup, J. "Style: Lessons in Clarity and Grace." Pearson, 2016.
Zinsser, W. "On Writing Well." Harper Perennial, 2006.
U.S. Army. "Army Regulation 25-50: Preparing and Managing Correspondence." Department of the Army, 2013. https://armypubs.army.mil/