How to Write an Executive Memo That Gets Read

Takeaway: Put the recommendation and ask first. Then give the reader the context, evidence, tradeoffs, and next steps needed to make the decision.

An executive memo is a decision tool. Its job is to help a specific reader understand what is happening, what you recommend, what you need from them, and what follows.

The writer often discovers the answer by moving through research and analysis. The reader doesn't need that journey in the same order. They need the result and a clear path through the reasoning.

Use this structure

Most executive decision memos can begin with six parts:

1. Recommendation: State the proposed answer in one or two sentences.
2. Ask: Name the decision, approval, resource, or input you need.
3. Context: Explain why the issue matters now.
4. Reasons and evidence: Group the strongest support for the recommendation.
5. Options and tradeoffs: Show the viable alternatives, costs, risks, and uncertainties.
6. Next steps: Name owners and dates if the recommendation is accepted.

Adapt the order when the situation requires it. A formal board paper, legal analysis, or incident report may have required sections. For an internal operating decision, the six-part structure gives the reader a usable first page.

Put the bottom line up front

U.S. Army writing standards use the principle commonly called bottom line up front, or BLUF. Army Regulation 25-50 directs correspondence to state its purpose and required action early.

The same principle works in business because it lets the reader orient immediately.

Don't open with:

Over the past several weeks, the operations team has reviewed our onboarding process and met with stakeholders across the company. Several themes emerged, and there are a number of possible ways to address them.

Open with:

Recommendation: Move new-customer handoffs to one weekly owner review beginning October 1. Decision needed by Friday: approve the proposed owners and a four-week pilot.

The second version doesn't invent a result. It tells the reader what is proposed and what decision is needed. The rest of the memo can explain the problem, evidence, and tradeoffs.

If you don't yet know the recommendation, keep working. A memo can ask for a decision between options, but it should still say what the options are and what input is needed.

Separate the recommendation from the ask

Writers often assume these are the same. They aren't.

The recommendation may be "run a four-week pilot." The ask may be "approve two hours a week from customer success and product operations." A reader can agree with the recommendation and still need to decide the resource.

Write the ask as a sentence:

• Approve the pilot and named owners by Friday.
• Choose option A or B before the contract renewal.
• Confirm whether the team should prioritize speed or cost.
• Review the two unresolved risks and provide direction.

Bullets are useful when they make parallel decisions easy to scan. The problem isn't the format. It is a fragment such as "improve onboarding" that leaves the reader to infer what should change and why.

Give enough context, then stop

Context should answer three questions:

• What is happening?
• Why does it matter now?
• What does the reader need to know before evaluating the recommendation?

Avoid replaying the full history unless a prior decision controls the current one. Link to background or place detail in an appendix.

A useful context paragraph might say:

Three customer launches missed their internal handoff date in August because sales, implementation, and product used different readiness checklists. The proposed pilot tests one shared review before the next renewal cycle.

That paragraph defines the observed problem and why the timing matters. It doesn't claim the pilot will solve it.

Group the reasoning

Barbara Minto's Pyramid Principle organizes communication around a main point supported by grouped reasons and evidence. Her MECE concept asks whether groups overlap and whether they cover the relevant ground (McKinsey).

Use that as a check, not a demand for an exhaustive taxonomy. A short memo usually needs the most material reasons, risks, and uncertainties.

For the onboarding example, the reasoning might have three sections:

1. Problem: Teams use different readiness definitions.
2. Proposed process: One review creates a shared decision point and owner.
3. Cost and risk: The review uses staff time and could become another meeting if the decision rights remain unclear.

Under each heading, place the evidence that belongs there. Remove facts that don't change the recommendation or tradeoff.

Use full reasoning, in prose or structured bullets

Jeff Bezos' 2017 shareholder letter describes Amazon's use of narrative memos instead of slide presentations and the revision required to produce a strong memo (Amazon). Full sentences can expose a missing logical connection that a fragment hides.

That doesn't make every bullet weak or every paragraph rigorous. Choose the format that serves the material:

• Use prose to explain causation, uncertainty, or a sequence of reasoning.
• Use bullets for parallel options, criteria, risks, or actions.
• Use a table when readers need to compare the same fields across options.
• Use an appendix for detail that supports review but shouldn't interrupt the main argument.

Whatever the format, state how one idea leads to the next.

Show real options and tradeoffs

A recommendation is more credible when the reader can see what else was considered.

For each viable option, include:

• expected benefit;
• cost or required resources;
• main risk;
• important assumption;
• reversibility; and
• consequence of waiting.

Don't create two obviously weak alternatives to make the preferred option look inevitable. If only one path is viable, explain which constraint eliminated the others.

State uncertainty directly. "The pilot will fix handoffs" overpromises. "The pilot tests whether one shared review reduces missed handoffs" describes what the decision can establish.

Write for the actual reader

A CFO may look first for cost, financial risk, and the assumptions behind a forecast. A head of product may focus on customer effect, technical dependencies, and team capacity. The underlying facts should remain consistent, but their order can reflect the reader's decision.

Use what you know about the reader to anticipate questions, not to hide inconvenient evidence. Managing up includes understanding how the principal processes information and where they need more context.

If several people will decide, write for the group and make conflicting criteria explicit.

Edit in four passes

Pass 1: decision

Can a reader identify the recommendation and ask in 30 seconds? If not, rewrite the top.

Pass 2: logic

Does each section support the recommendation, explain a tradeoff, or define the next step? Move or cut anything that doesn't.

Pass 3: evidence

Check numbers against the source. Label estimates and assumptions. Confirm that links and attachments open to the intended material.

Pass 4: language

Cut throat-clearing, repeated conclusions, jargon, and inflated claims. Use direct verbs. Break long paragraphs where the reader needs a pause.

Then ask a colleague who wasn't involved in the analysis to state the recommendation, ask, and main tradeoff after one read. Their answer shows what the memo actually communicates.

End with ownership

If the reader approves the recommendation, the memo should make the next move clear:

• owner;
• first action;
• due date;
• review point; and
• record of the decision.

A decision log keeps the approved answer and its owner from disappearing into the document archive.

How long should an executive memo be?

As short as the decision allows. A one-page memo may suit a reversible operating choice. A consequential investment or board decision may require more evidence and formal sections.

Does BLUF mean hiding nuance?

No. It changes the order, not the evidence. State the recommendation first, then give the reader the uncertainty and tradeoffs needed to assess it.

Should an executive memo use bullets?

Use bullets for parallel information that remains clear in that form. Use prose when the reader needs to follow a relationship, cause, or sequence. Complete reasoning matters more than the container.

The Executive Memo Pack includes fill-in structures for decision memos, weekly updates, briefing notes, and announcements, plus three full rewrites.