Writing Clear Executive Memos

Why a one-page memo can save a million-dollar decision

Most managers learn to write by sending emails. Emails reward speed, informality, and incremental replies. Executive decisions reward the opposite: a single, coherent argument that a busy leader can grasp in ninety seconds and still trust enough to act on. When a CEO (chief executive officer, the top executive responsible for company strategy and operations) opens your document at 11 p.m. before a board meeting, she is not looking for a diary of your week. She is looking for a decision package: a clear recommendation, the stakes if she says yes or no, the tradeoffs you considered, and the next steps with owners and dates.

Weak memos do not merely waste time. They create bad decisions. A vague headcount request gets approved without budget discipline, or denied without the hiring manager understanding why. A buried recommendation gets skimmed past, and the meeting re-litigates facts that were already analyzed. A memo that reads like journalism (background first, conclusion last) trains the reader to stop before they reach your point. In organizations that run on narrative memos rather than slide decks, the memo is the first draft of the decision. Sloppy thinking on the page becomes sloppy governance in the room.

This lesson teaches you to write executive memos: short, decision-oriented documents that force clarity before calendar time is spent. You will learn BLUF (bottom line up front, stating your answer in the first paragraph), SCR (situation, complication, resolution, a three-part structure for framing decisions), and the discipline of fitting a complex choice onto one page without hiding the hard parts. From Unit 4, you already know that good strategies fail when execution lacks owners, cadence, and honest tradeoffs. Memos are where those execution habits start. If you cannot write the decision in one page, you probably do not understand it well enough to ask others to fund it.

Memos are thinking made visible, not status archives

An executive memo is a written argument aimed at a decision maker. It is not a project update, a meeting recap, or a place to demonstrate how hard your team worked. Status information belongs in dashboards, standups, or operational reviews. Memos belong at decision gates: launch or delay, hire or contract, renew or switch vendors, enter or exit a market, approve capital or hold.

Some firms institutionalize this habit. Amazon famously replaced slide decks for many decisions with narrative memos read silently at the start of meetings. The cultural point is not nostalgia for paper. It is that slides encourage bullet fragments and visual shortcuts that let weak logic survive. Prose sentences must connect. A recommendation must follow from evidence. A tradeoff must be named, not implied behind a cheerful chart. When you write a memo, you are making your reasoning inspectable.

The managerial standard is simple: after reading page one, the decider should know what you want, why, what it costs, what you are not doing as a result, and what happens next. Everything on page two supports page one. Anything that does not support the decision belongs in an appendix or, better, in the trash.

Consider a product director at a SaaS company (SaaS means software as a service, software customers subscribe to rather than buy outright). She wants to delay a European launch by ninety days. A status email might chronicle engineering tickets, compliance meetings, and sentiment from the sales team. A decision memo opens with the delay recommendation, quantifies fine risk and support load, names the tradeoff against U.S. momentum, and assigns compliance and engineering owners for the revised timeline. Same facts. Different managerial function.

BLUF: put the answer where tired eyes will actually read

BLUF (bottom line up front) means the first paragraph states the complete recommendation or answer. Not "we have been analyzing." Not "there are several options." The reader should not need page two to discover what you want. Military communication doctrine popularized BLUF because commanders under stress might read only the opening lines. Corporate executives are not in foxholes, but they are in back-to-back meetings with partial attention. Respect that reality.

A strong BLUF paragraph typically includes four elements woven into two or four sentences: (1) the recommendation, (2) the primary reason it wins, (3) the most important tradeoff or cost, and (4) the requested decision. Numbers should carry units and time frames. Avoid weasel words like "somewhat," "fairly," or "it seems." If you are uncertain, say what would reduce uncertainty and by when (Lesson 4 covers that language in depth).

Weak opening: "Background: In Q1 we observed elevated payment failure rates in EU test markets and began a cross-functional review of compliance requirements."

Strong opening: "Recommend delaying the EU launch ninety days to close payments compliance gaps that create an estimated $2.1M regulatory fine risk; the delay preserves U.S. enterprise momentum and avoids a partial launch that would consume 40% of support capacity in Q3. Approve revised timeline and compliance budget of $480K."

Notice what the strong version does economically. It names the action (delay), duration (ninety days), reason (compliance gaps and fine risk), quantified stake ($2.1M), opportunity cost (U.S. momentum, support load), and implicit ask (approve timeline and budget). A CEO can agree, disagree, or ask one sharp question immediately.

BLUF does not mean being rude or skipping context. It means not forcing the reader to mine for the point. Context comes after the answer, organized so each paragraph deepens understanding of a decision they already grasp.

SCR: situation, complication, resolution

SCR (situation, complication, resolution) is the backbone structure for the body of a memo after BLUF. Think of it as answering three questions in order: What is the stable context? What changed or threatens us? What should we do and why?

The situation is shared context the reader needs, stated in three to five sentences. Assume intelligence, not memory. Remind them of the goal, the prior decision, or the metric baseline, but do not dump history. If your situation section is a page long, you are writing a report, not a memo.

The complication is the disruption: a new risk, a missed target, a competitive move, a budget gap, a regulatory change. This is where stakes become vivid. Tie complications to outcomes the decider cares about: revenue, margin, cash, customer trust, regulatory exposure, or strategic position.

The resolution is your recommendation plus rationale, explicit tradeoffs, rejected alternatives, key risks, and next steps. This is not a menu of options unless you were explicitly asked for options only. Default to one clear recommendation. If you present multiple paths, say which you prefer and why.

A sample one-page memo structure you can copy and adapt:

TO: [Decider name and role]
FROM: [Your name and role]
DATE: [Date]
RE: [Decision in eight words or fewer]

BLUF (paragraph 1): [Recommendation + primary rationale + key tradeoff + ask]

Situation (paragraph 2): [Goal, baseline, prior decision]

Complication (paragraph 3): [What changed; quantified stakes]

Resolution (paragraph 4): [Why this recommendation wins]

Tradeoffs and rejected alternatives (3 bullets max):
• [Tradeoff you accept]
• [Alternative considered and why rejected]
• [Risk and mitigation owner]

Next steps (table or bullets with owners and dates):
| Action | Owner | Due |
|--------|-------|-----|
| ... | ... | ... |

Ask: [One sentence: what approval you need today]

The structure is not magic. It is a checklist for completeness. If any box is empty, the decision is probably undercooked.

One-page discipline: constraints that improve thinking

The one-page discipline is a forcing function. Constraints do not dumb down decisions. They surface what matters. A useful rule of thumb: twelve-point readable font, one-inch margins, no appendix required to understand the recommendation. Appendices are for skeptics who want sensitivity tables, legal citations, or survey crosstabs. The decider should not need them to vote.

Practical limits that keep memos executive-grade:

• Maximum three supporting bullets per major argument. More bullets usually means you have not synthesized.
• Charts only if one glance conveys the insight. If the chart needs a paragraph to interpret, fix the chart or move it to the appendix (Lesson 3 covers visual design).
• Active voice and short sentences. "We recommend delaying launch" beats "It is recommended that launch be delayed."
• Numbers always carry units and time frames: "$2.1M fine exposure over eighteen months," not "significant regulatory risk."
• Name tradeoffs honestly. Every real decision inconveniences someone. Pretending otherwise destroys trust.

If you genuinely need eight pages, you likely have not decided what the decision is. Split the work: a one-page memo for the approval, a separate technical annex for implementation staff. Do not make the CEO read both.

Tone, precision, and the habits that build trust

Tone in executive memos is professional and direct, not theatrical or defensive. You are a fiduciary of the reader's attention. Write as if you respect their time and intelligence. Avoid sarcasm, blame storms, and passive voice that hides ownership ("mistakes were made"). When something went wrong, state what happened, what you learned, and what changes.

Precision is a form of respect. Vague requests breed vague outcomes. Compare two headcount asks. Weak: "We need two more engineers because we are busy." Strong: "Request two backend engineers for the payments squad to reduce incident MTTR (mean time to recovery, average minutes to restore service after an outage) from 4.2 hours to under one hour by Q4, enabling enterprise tier launch tied to $3.2M pipeline. Tradeoff: mobile roadmap slips six weeks. Alternative considered: contractor surge for six months, rejected due to security review backlog and knowledge transfer risk."

The strong version gives the decider a basis to say yes, no, or yes with conditions. They can test whether $3.2M pipeline justifies a six-week mobile slip. They can ask whether contractors could clear the security backlog. The weak version invites a political debate about "busy."

Finally, match memo to decision type. Use memos for approvals with stakes: budget, policy, hiring plans, market entry, major vendor selection. Use email for coordination. Use meetings for negotiation where real-time debate adds value, not for read-aloud of information that should have been a pre-read. The memo is the thinking; the meeting is the judgment.

Northwind Analytics is a 420-person B2B data platform. Finance has identified overlap among four customer support tooling vendors totaling $1.86M annual spend. You are the VP Operations drafting a memo to the CFO and CEO requesting approval to consolidate to one platform.

Part A: Fact pattern and draft goal

Migration cost estimate: $290K one-time (integrations, training, parallel run). Expected annual savings after migration: $740K beginning month 10. Risk: six-week period of dual tooling during enterprise renewal season (September-October). Customer-visible incident target: no increase above baseline 0.9% tickets escalated to engineering.

Your job: one-page SCR memo with BLUF, not a vendor beauty contest slideshow.

Part B: BLUF and SCR draft (excerpt)

BLUF paragraph:

"Recommend consolidating four support vendors to Zendesk Enterprise by October 1 to save $740K annually starting month 10, at one-time migration cost of $290K and net three-year benefit of $1.93M. Accept six weeks of dual-tooling risk during September enterprise renewals; mitigate with dedicated migration squad and frozen workflow changes. Approve $290K project budget and vendor termination notice by July 15."

Situation: Northwind runs four overlapping support tools inherited from acquisitions. Baseline customer satisfaction (CSAT) is 4.2/5; escalations to engineering are 0.9% of tickets.

Complication: Tool fragmentation adds 12-minute average handle time for agents switching systems and blocks unified reporting for enterprise accounts renewing in Q3-Q4.

Resolution: Zendesk covers chat, voice logging, and QA via APIs; migration vendor has completed three similar B2B rollouts. Rejected staying on HelpDesk One plus partial additions (saves only $210K). Rejected Rippling Desk (saves $680K but lacks VoiceBridge telephony integration without custom build).

Part C: Tradeoffs, next steps, and check

Financial check: Annual savings $740K × 3 years = $2.22M; minus $290K migration = $1.93M net three-year ✓. Payback: $290K / ($740K/12) ≈ 4.7 months after go-live ✓.

Part D: Managerial read

The CFO will test whether savings are real or recycled headcount fantasy. The CEO will ask what happens if CSAT dips during renewals. Your memo pre-answers with quantified stakes, rejected alternatives, and owners. Board question: "What is the cost of delay one quarter?" Delay pushes savings start to month 13, reducing three-year net benefit to $1.75M ($1.93M − $185K) and leaving $465K annual spend on the table an extra quarter ✓.

Before (weak): Three paragraphs of team biography, a list of seventeen Jira tickets, and a closing line "Therefore we need two senior data engineers."

After (strong, BLUF + SCR):

"Request two senior data engineers for the pricing squad to ship dynamic packaging by November 1, protecting $4.8M ARR renewals tied to pricing flexibility. Without them, model deployment stays manual and renewal risk rises for 14 enterprise accounts. Tradeoff: data platform roadmap loses one contractor slot ($180K). Alternative rejected: outsource model serving (adds 9-week security review).

Situation: Pricing committed dynamic packaging to enterprise customers in March roadmap. Complication: serving layer still manual; two renewals in December cited inflexibility in exit interviews. Resolution: two hires integrate serving with existing feature store; recruiter pipeline has three screened candidates. Next steps: approve reqs by Aug 5; start dates by Sept 9. Ask: approve two FTE reqs and repurpose one contractor slot."

Managerial read: The rewrite turns sympathy into a fundable business case tied to ARR (annual recurring revenue, subscription revenue expected each year) and a dated deliverable. The decider can negotiate the tradeoff (contractor slot) without re-opening the entire hiring philosophy.

You are Director of Product at LumenPay, a payments startup. Fraud losses rose from 0.8% to 1.4% of volume ($2.1M annualized at current run rate). Vendor Sardine offers a fraud module for $380K/year plus $120K implementation. Building in-house is estimated at two engineers for nine months ($850K fully loaded) plus $90K data vendor costs.

Tasks:

1. Write BLUF paragraph recommending one path (vendor or build) with primary rationale and tradeoff.
2. Write Situation and Complication paragraphs (3-5 sentences total).
3. Add three bullets: tradeoff, rejected alternative, risk with owner.
4. Draft next-steps table with three rows (owner, date).
5. Explain in prose why BLUF should mention the tradeoff even when it weakens your case.

Solution

1. BLUF (vendor path example):

"Recommend purchasing Sardine fraud module for $380K/year with $120K implementation to cut fraud losses toward 0.9% within two quarters, saving roughly $750K annually at current volume. Tradeoff: nine-month in-house build would delay other wallet features and forgo $750K annual savings in year one. Approve $500K year-one vendor budget and implementation start by August 1."

2. Situation and Complication:

Situation: LumenPay processes $150M annualized volume; fraud losses historically ran 0.8% ($1.2M). Product roadmap prioritized wallet features for Q3-Q4. Complication: fraud rose to 1.4% ($2.1M annualized) after cross-border expansion; two partner banks flagged remediation by December or fee increases of 15 bps (basis points, hundredths of a percentage point).

3. Bullets:

• Tradeoff: vendor spend reduces available budget for wallet loyalty features by $380K/year.
• Rejected alternative: nine-month in-house build ($850K people + $90K data) due to bank remediation deadline and opportunity cost of delayed savings.
• Risk: false positive rate may rise; mitigation owner Product Analytics, weekly review with Fraud Ops.

4. Next steps:

5. Why BLUF must state the tradeoff:

Deciders allocate scarce budget and attention. If you hide that wallet features slow down, the CFO may approve fraud spend then reverse the decision when loyalty slips appear in a later memo. Naming the tradeoff early signals intellectual honesty and lets the executive re-balance priorities in one conversation instead of two adversarial ones. Trust compounds when your opening paragraph matches the full story on page one.

Check: Expected savings if loss rate returns to 0.9%: (1.4% − 0.9%) × $150M = $750K/year ✓. Year-one net vs status quo after vendor costs: $750K − $500K = $250K positive ✓.

Rewrite this opening as a BLUF paragraph for a CEO who has thirty seconds:

"Over the past two quarters, the customer success team has gathered feedback indicating onboarding friction. Several enterprise accounts mentioned training gaps. We analyzed usage data and interviews. There are multiple paths forward."

Include: recommendation (hire two onboarding specialists), stake ($1.1M expansion revenue at risk in Q4), tradeoff (delay self-serve tutorial project six weeks), and explicit ask.

Solution

"Recommend hiring two enterprise onboarding specialists starting September 1 to protect $1.1M Q4 expansion revenue at risk from activation gaps in seven accounts. Tradeoff: self-serve tutorial project slips six weeks. Approve two FTE reqs and $240K Q4 fully loaded cost by August 10."

The rewrite removes chronological throat-clearing and states answer, reason, cost, tradeoff, and ask. A CEO can approve, deny, or probe the $1.1M linkage immediately. Check: all four BLUF elements present ✓.

Key takeaways

• Executive memos are decision packages, not status archives; write them at approval gates.
• BLUF puts the complete recommendation in paragraph one; SCR organizes the supporting story.
• One-page discipline forces synthesis; appendices hold optional proof, not hidden conclusions.
• Name tradeoffs and rejected alternatives; precision and honesty earn repeat reads.
• End with an explicit ask, owners, and dates so approval converts to execution.

1. Take a recent email where you asked for approval. Rewrite the opening as BLUF in four sentences with numbers and a tradeoff.
2. Which decision on your calendar deserves a one-page SCR memo instead of a live read-aloud meeting?
3. Continue to Lesson 2: Presenting Recommendations to Decision Makers.