The executive summary is the most important page of your business case. For many decision-makers, it is the only page they will read end-to-end before forming a view. If this page is clear, decision-oriented, and well-structured, the rest of the pack becomes supporting evidence rather than a battlefield. If this page is vague, overlong, or muddled, no amount of detail in the appendix will save your case.
This chapter focuses on how to write an executive summary that is truly decision-grade: one screen, one story, one clear ask.
7.1 Purpose and “One-Screen” Criteria
The executive summary has a very specific job. It is not a teaser, a marketing page, or a generic introduction. Its purpose is to enable a senior decision-maker to:
- Understand what decision you are asking them to make.
- Grasp why now and what is at stake.
- See what options exist and which you recommend.
- Absorb the headline economics and key trade-offs.
- Gauge the major risks and your plan to manage them.
- Judge whether the team can execute and how progress will be governed.
If a director can read your executive summary and confidently answer those points without turning the page, you have done your job.
The “one-screen” test
Design the summary so that it fits comfortably on a single laptop screen or a single printed page:
- As a slide: one page that can be read from a meeting room screen without squinting.
- As a memo: one page with normal margins and readable font, not crammed text.
In practice, that usually means:
- Around 250–400 words if mostly text, or
- Roughly 6–10 short bullets plus a small exhibit (e.g., a cost/benefit bar or options table), or
- A hybrid: a few short paragraphs and 4–6 bullets.
The content should be self-contained: no numbered cross-references needed to understand the story. References to later sections are fine (“see Section 6 for detail”) but the reader should not need them to decide.
What does not belong in the executive summary
- Detailed methodology, data sources, or model mechanics.
- Long historical narratives about how you got here.
- Technical details of architecture, contracts, or process flows.
- Lists of every risk or issue; only the top few that move the decision.
Those belong in the body and appendices. The executive summary is premium real estate: only put content that directly helps the decision.
7.2 Crafting the Ask and Decision Headlines
At the core of a good executive summary are two elements: a crisp ask and a handful of decision headlines.
Crafting the ask
The ask is a single sentence that states, without ambiguity, what you want the decision-maker to approve. A useful pattern is:
“We ask [decision body] to approve [option] requiring [funding/resources] to deliver [outcomes] by [timeframe].”
For example (stripped of any sensitive specifics):
- “We ask the Executive Committee to approve the phased rollout of the new customer service platform, requiring $18m over three years to reduce service costs by 15% and improve NPS by 10 points by FY28.”
A strong ask typically includes:
- Decision body: who is being asked (boss, ExCo, Board, investment committee).
- Action: approve, deny, proceed with pilot, release tranche, sign contract, etc.
- Option: the labeled option from your options section (e.g., “Option B – phased rollout”).
- Scale: order of magnitude of funding or resources.
- Outcome: the key metric or value (NPV, IRR, benefit level, risk reduction).
- Timeframe: when major outcomes or stage gates are expected.
Avoid vague asks like “endorse the direction” or “support continued work” unless the genuine decision is only about exploration. If the real purpose is to get funding or binding approval, say so explicitly.
Decision headlines
Immediately after the ask, present 3–5 decision headlines—short, high-signal statements that summarize the case. They should cover:
- Recommendation and rationale
- Headline economics
- Risk and controls
- Execution readiness and path
- (Optional) Strategic or stakeholder angle if particularly important
For example:
- “Option B (phased rollout) maximizes NPV while staying within current capacity constraints.”
- “Investment of $18m delivers $42m NPV, 31% IRR, and 3.5-year payback over 7 years.”
- “Top risks are migration failure and vendor dependency; mitigations reduce residual risk to within our appetite.”
- “We have a cross-functional delivery team identified, with phased funding tied to three stage gates.”
These are headlines, not supporting paragraphs. Each should be one sentence, ideally one line. They act as the “table of contents of the argument” that the rest of the document elaborates.
A useful discipline: if a statement cannot be supported elsewhere in the case with evidence or analysis, it does not belong as a headline.
7.3 Storyline Using the Pyramid Principle
The Pyramid Principle is a simple, powerful way to structure your executive summary: start with the answer, then support it with logically grouped reasons, each backed by evidence.
At its simplest, your pyramid has three levels:
- Top line: The recommendation and ask.
- Key supporting points: Usually three clusters (Strategic fit / Economics / Risk & Execution).
- Evidence: The data and analysis that support each cluster (kept brief in the summary, detailed later).
Level 1 – The answer (top of the pyramid)
This is the ask plus a short statement of the recommendation. It should answer:
- What are we recommending?
- What decision do we need?
- Why now?
Example structure:
- Paragraph 1: One or two sentences: the ask and the headline reason (e.g., “to unlock X value and avoid Y risk”).
Level 2 – The three story “pillars”
Group your supporting points into three logical pillars. A simple default is:
- Pillar A – Strategic logic and problem/why now
- What problem or opportunity we are addressing.
- How this aligns with strategy and external/internal trends.
- Pillar B – Economics and value
- How much we invest.
- What we get in return (NPV/IRR/payback, key benefit drivers).
- How sensitive the case is to a few key assumptions.
- Pillar C – Risks and execution
- Top risks and mitigations.
- Feasibility, capacity, and delivery approach.
- Governance, funding stages, and benefit ownership.
In the executive summary, each pillar typically appears as a short paragraph or a set of 2–3 bullets, not a long exposition.
Level 3 – Evidence (brief in the summary, deep elsewhere)
At the bottom level, you have the facts and analysis that support each pillar:
- Market data, internal performance trends, regulatory drivers (for strategic logic).
- Model outputs, benefit breakdowns, cost profiles, scenarios (for economics).
- Risk register highlights, roadmap, resource plan, vendor status (for execution).
In the executive summary, you only surface the most decision-relevant pieces, e.g.:
- “Demand for X is growing 8% annually versus 2% for our legacy product, and we are losing share in segments A and B.”
- “Total incremental cost is $18m, delivering $60m gross benefits and $42m NPV over seven years.”
- “Critical path runs through data migration and integration with Y; we have identified a two-phase cutover to reduce downtime.”
Everything else is moved to the relevant sections later in the case.
7.4 Step-by-Step Writing Guide
Many people leave the executive summary to the end and then rush it. A better mindset is: use the summary to clarify your own thinking, then refine it as the case matures.
Here is a practical step-by-step approach.
Step 1 – Clarify the decision and audience
Before writing a word:
- Write down, in plain language, the decision you want and who will make it.
- Note their main concerns (e.g., cash, risk, regulatory exposure, EPS, reputation, employee impact).
This will shape the emphasis in your executive summary.
Step 2 – Gather the raw materials
Pull together:
- The current problem/opportunity statement and “why now.”
- The latest options set and which one is recommended.
- Headline numbers from the model: costs, benefits, NPV/IRR/payback or equivalents, key sensitivities.
- Top risks and mitigations from the risk register.
- The high-level roadmap and governance structure.
Do not start from a blank page; start from these building blocks.
Step 3 – Draft the ask and 3–5 headlines
Write:
- A single sentence for the ask using the pattern from 7.2.
- Three to five one-line headlines covering recommendation, economics, risk, and execution.
At this stage, ignore elegance; aim for clarity. If you cannot write these in 10–15 minutes, your case is probably not yet conceptually ready.
Step 4 – Sketch the pyramid
On a scratch page (or a simple outline), write:
- Top line: your ask and one-sentence rationale.
- Under it, three labelled buckets: “Strategic/Why now,” “Economics,” “Risk & Execution.”
- Under each bucket, list 2–3 supporting points (short phrases, not full sentences).
Check that:
- The buckets are mutually exclusive and collectively exhaustive enough for a senior reader.
- Each supporting point is genuinely necessary—if removing it would not change the decision, cut it.
- There is a logical flow from one bucket to the next.
Step 5 – Turn the outline into prose
Convert the outline into a one-screen narrative, typically in this order:
- Paragraph 1: Ask + core rationale.
- Bullets or short para: Decision headlines.
- Short para or bullets: Problem/why now and strategic fit.
- Short para or bullets: Economics summary and sensitivities.
- Short para or bullets: Risks, execution, and next steps.
Aim for clear, declarative sentences. Avoid hedging or marketing language.
Step 6 – Cut for brevity and sharpen language
Now edit ruthlessly:
- Remove any sentence that does not help a decision-maker answer: “What, why now, why this, what if it goes wrong, can they execute?”
- Replace vague terms (“significant,” “material,” “strong”) with specifics (numbers, ranges, or at least directionally clear descriptors).
- Shorten sentences; split long ones into two.
- Use active voice and name owners where relevant (“The COO will sponsor delivery…”).
If you are writing a slide, pay attention to layout: no long blocks of text; use 6–8 words per line and avoid tiny fonts.
Step 7 – Align with the numbers and the body
Check consistency:
- All numbers in the summary match those in the model and the main body (NPV, IRR, payback, cost totals, benefit totals).
- Option names and labels are consistent (“Option B – Phased rollout” everywhere, not “Option 2” elsewhere).
- Risks, dates, and milestones are the same across summary, roadmap, and risk register.
Inconsistencies are poison; they prompt readers to question everything else.
Step 8 – Test with a fresh reader
Ask a colleague who has not been immersed in the detail to read only the executive summary and then tell you:
- What decision they think is being asked of whom.
- Why are you recommending this option?
- What the value and risk look like at a high level.
- What they are still confused about.
If they cannot explain it back in their own words after one read, simplify and clarify.
Step 9 – Tailor for the specific forum
Adjust emphasis depending on the audience:
- For your boss: slightly more execution and near-term impact.
- For ExCo: more portfolio and trade-offs with other initiatives.
- For Board: more risk, resilience, and assurance; fewer operational details.
- For investors: more unit economics and cash profile; clear milestones.
- For regulators: more controls, compliance, and residual risk.
The facts stay the same; the ordering and emphasis can shift.
Step 10 – Freeze and protect the summary
Once you have stakeholder alignment:
- Lock the executive summary as the “single source of truth.”
- Update the rest of the document and deck to align to it.
- Avoid making late, unreviewed edits that can desynchronize the summary and body.
In practice, you will tweak language until the last minute, but treat the summary as the anchor that everything else must match.
7.5 Executive Summary Checklist
Use this checklist just before you circulate your draft. If you cannot honestly tick an item, fix it.
A. Decision clarity
- The first sentence clearly states the decision body and the ask (approve/deny/fund/pilot/etc.).
- The recommended option is named and distinguishes itself from alternatives.
- “Why now” is explicit, not implied.
B. One-screen and stand-alone
- The summary fits on a single laptop screen or printed page with readable font.
- A senior reader can understand the recommendation, economics, risks, and plan without reading any other section.
- There are no long digressions, definitions, or methodology explanations.
C. Storyline and structure
- The narrative follows a clear logic: Ask → Why now → Options/recommendation → Economics → Risks & execution → Next steps.
- There are 3–5 crisp decision headlines that summarize the case.
- Supporting points are grouped into a small number of coherent buckets (e.g., strategy, economics, risk & execution).
D. Economics and assumptions
- Headline metrics (NPV, IRR, payback or equivalents) are shown and clearly linked to the recommended option and time horizon.
- Total costs and total benefits are shown at a high level, including timing (e.g., “over 5 years”).
- At least one sensitivity or scenario is mentioned (what moves the case).
- All numbers in the summary match the latest version of the model and body.
E. Options and trade-offs
- The existence of other options, including the baseline, is acknowledged (even briefly).
- Key trade-offs (e.g., cost vs. speed, risk vs. scope) are explicit.
- It is clear why the recommended option is superior, given the decision criteria.
F. Risk, controls, and feasibility
- Top 3–5 risks are named in business language (not just categories).
- For each, the presence of mitigation and residual risk is indicated.
- Execution feasibility is addressed: there is at least a brief statement on roadmap, capacity, and governance.
- Any material regulatory, security, or reputational aspects are mentioned.
G. Ownership and next steps
- The sponsor is identifiable (by title if not by name).
- Post-decision next steps are clear (e.g., “If approved, we will… in the next 90 days”).
- Stage-gates or major milestones are indicated at a high level.
H. Style and tone
- Language is plain, direct, and free of jargon where avoidable.
- Sentences are concise; there is minimal hedging and no marketing spin.
- Voice is confident but not over-certain; uncertainty is acknowledged where it matters.
- The tone matches the audience (e.g., more formal for Board, more operational for internal steering).
If you can tick these boxes, your executive summary will do what it is supposed to do: give busy decision-makers everything they need on a single screen to make a high-quality decision—and set up the rest of your business case as supporting evidence rather than competing noise.
