What is an executive summary? (and how to write one)

An executive summary is the top of the funnel for your work. The one page (or one to two slides) that helps a busy leader decide three things:

• Do I care?
• What’s the recommendation?
• What decision is needed?

Do it well, they keep reading. Do it poorly, your doc might as well not exist.

The moment it clicks

Early in my first job I got handed a messy spreadsheet task — pull insights and patterns out of a giant Excel file. The analysis was hard but doable. The real problem was that I didn’t have the tooling yet. Pivot tables were still a mystery to me.

This was pre-YouTube-explains-everything. So I went to a bookstore, bought a chunky Excel guidebook (CD-ROM included), and taught myself.

Then came the second challenge — and it’s the one this post is about. Not “do I understand the data?” but “can I explain the point fast enough that a busy person will actually use it?”

That’s what an executive summary is. Not more work. Translation work.

The definition

A short, decision-oriented snapshot of a larger document. Not the whole story. The trailer that convinces someone the movie is worth watching. Aim for ~1 page for a doc, 1–2 slides for a deck.

Your real goal: reduce the leader’s work

A leader reading your summary is doing mental triage. Make triage easy by giving them, in order:

1. context
2. the problem or opportunity
3. the recommendation
4. the decision needed
5. risks and trade-offs
6. what happens next

Bury the recommendation on page three and you’re forcing them to hunt. Don’t.

The template

## Executive summary

**Context (1–2 sentences):**

**Problem / opportunity:**

**Recommendation (1 sentence, BLUF):**

**Decision needed (be explicit):**

**Why this / key evidence (3 bullets max):**
-
-
-

**Risks / trade-offs (2–3 bullets):**
-
-

**Next steps (owner + dates):**
-

If it’s slides

Slide 1: the call. Headline = the recommendation. Three bullets = the evidence that changes the decision. Decision needed (one line).

Slide 2: the reality. Three bullets = risks and trade-offs. Next steps (owner + dates).

If your deck needs twelve slides to explain the summary, you don’t have a summary yet.

Write it last

Write the full doc first. Then write the exec summary. You don’t actually know what matters most until you’ve done the work.

A mini example

Context: Customer support tickets for login issues spiked after the last release.

Problem: Driving churn risk and burning support hours.

Recommendation: Roll back feature X this week and ship a smaller fix by next Friday.

Decision needed: Approve rollback today. Approve one engineer allocation for five days.

Why:

• Top 3 ticket themes point to feature X as the trigger
• Rollback is reversible and reduces immediate customer pain
• Smaller fix preserves the upside without the current risk

Risks and trade-offs:

• Temporary loss of feature X benefits
• Release schedule impact on Project Y (mitigation: de-scope one non-critical item)

Next steps:

• [Me] execute rollback today
• [Eng lead] assign owner by EOD
• [PM] comms to support by tomorrow AM

That’s the bar: tight, explicit, decision-forward.

Five mistakes to fix

1. “Background” takes the whole page. Keep context to one or two sentences. If it needs a history lesson, put it in an appendix.

2. No recommendation. Make a call. Even if the recommendation is “do nothing,” say it.

3. Unclear decision. Write the decision as a sentence that starts with a verb: “Approve $X budget.” / “Choose Option A.” / “Confirm timeline.”

4. Claims not backed up later. Only summarize things you can support in the full doc.

5. Too many bullets. If you have twelve key points, you don’t have key points. Pick the three that change the decision.

—

The exec summary is the highest-leverage writing skill nobody teaches you in college. A good one-pager can change what gets prioritized in your division. A bad one means your work doesn’t get read at all. The asymmetry is wild — and the format itself takes 20 minutes to learn. Steal the template, use it twice, and you’ll never write a doc the same way again.

For the weekly leader-friendly format, use the Status update template.