What the executive summary slide is for
An executive summary slide is the deck in one page. It sits right after the title slide, states the conclusion, gives the three to five reasons for it and, where there is a decision to make, says what that decision is. Everything that follows in the deck is evidence for what this page claims.
It exists because senior audiences read in a particular way. A chief executive or a board member will read the summary, decide whether they agree, and turn to the pages where they do not. Some will read nothing else. If the summary carries the argument, the deck works for them; if it only lists what the deck covers, they learn nothing until slide twelve.
The test of an executive summary slide: could an executive stop here and make the decision?
Two classic formats: SCR and dot-dash
Most consulting-style summaries use one of two structures. The first follows Situation, Complication, Resolution: a sentence of context, a sentence on what has changed, then the recommendation and its reasons. It reads like the opening of a memo and suits audiences who need a line of background first. Our guide to the SCQA framework covers the full version, with the question stated.
The second is the dot-dash form. Each dot is a bolded statement in a full sentence; beneath it sit two or three dashes, shorter points that give the evidence. Here is one for a software company deciding how to change its pricing. The numbers are illustrative.
- Move new customers to usage-based pricing from January: it raises expected revenue per account by 12% with no rise in churn
- – Usage, not seat count, now predicts what customers are willing to pay
- – A pilot with 140 new accounts converted at the same rate as the per-seat control group
- Keep existing customers on seat pricing until their renewal date
- – Moving them mid-contract would put about $3M of annual revenue up for renegotiation
- – Renewals spread the change over 12 months, which support and billing can absorb
- Billing changes are the critical path, so they need to start this quarter
- – Metering and invoicing changes take about 14 weeks
- – Sales needs new quotes and training before the January launch
Read the dots alone and you have the argument. Read the dashes and you have the proof. Each dot should match, word for word or nearly so, the title of the section divider it leads to, so the summary doubles as a map of the deck.
Five layouts, before and after
The same content can sit on the page in several ways. Each layout below pairs a weak version, the kind that often appears in real decks, with a stronger rewrite. The rules behind all five are the same; pick the one that fits the audience and the decision.
1. SCR paragraphs · before
Three boxes headed “Background”, “Issues” and “Recommendations”, each filled with bullet fragments
After
Three short paragraphs: “Renewal rates have held at 90% for five years.” “Two new competitors now undercut us on price for small teams, and new-customer growth has halved.” “Move new customers to usage-based pricing from January, for three reasons…”
2. Dot-dash · before
Twelve bullets of equal weight, each a finding, none of them bolded
After
Three bolded statements in full sentences, each with two or three supporting dashes beneath it
3. Three pillars · before
Three columns headed “People”, “Process” and “Technology”
After
Three columns headed with claims: “Hire 12 field engineers”, “Cut approval steps from five to two”, “Replace the scheduling system by Q3”, each with its impact and cost underneath
4. Numbers-led · before
A dashboard of eight KPIs with no comment
After
Three key numbers, each with a sentence that says what it means: “$4.1M saved a year, from closing the duplicate site”
5. Decision ask · before
“Next steps: discuss and align”
After
“Decision needed today: approve the $2.2M budget so the pilot can start in March”, with the two or three reasons beneath it
- SCR paragraphs suit a mixed audience that needs context, or a deck that will be read without a presenter.
- Dot-dash suits a decision with several distinct reasons, and senior readers who skim.
- Three pillars suit a plan or program with parallel workstreams.
- Numbers-led suits performance reviews and business cases where a few figures carry the case.
- The decision ask suits a short meeting with one approval at stake. It still needs the reasons beneath it.
How to write it
- Write the governing thought first: one sentence that states your answer and takes a position.
- List the three to five reasons that support it. These are the key line of your storyline, and they become the bolded statements.
- Under each reason, pick the two or three facts that prove it best. Use numbers wherever you have them.
- Choose the layout that suits the audience, and add a decision line if the meeting must decide something.
- Draft the summary at the start of the work as a hypothesis, then rewrite it last, once the analysis is done.
- Read it as the only page a busy reader will see, and cut anything that does not bear on the decision.
Step 5 is the one teams skip. Those who write the summary only at the end tend to summarize what they did rather than what they found. Those who draft it on day one have a target for the analysis, and they change it as the evidence comes in. For how the rest of the storyline is built around it, see our guide to McKinsey-style presentations; for grouping and ordering the reasons, see our guide to the Pyramid Principle.
Design and length
- One page. If it needs two, the argument is not yet clear.
- Three to five bolded statements. Beyond five, readers stop holding them in mind.
- As a rule of thumb, about 80 to 150 words, at a size that can be read from the back of the room without zooming in.
- Bold the statements, not scattered phrases, so the eye can read the argument in a few seconds.
- No chart, as a rule. The summary makes the case in words, and the charts that prove it come later. A single key number shown large is the exception when that number is the point.
- A title that states the governing thought rather than the words “Executive summary”. Many teams keep that label small, in the tracker.
Common mistakes
- An agenda pretending to be a summary. “Market overview, Financial analysis, Options, Next steps” tells the reader what is coming, not what you concluded.
- A wall of text: paragraphs pasted from the report, with nothing bolded and no hierarchy.
- Findings without a recommendation. Ten accurate observations still leave the executive to do the thinking.
- Statements that do not match the section titles, so the reader cannot find the proof.
- Hedged language such as “may”, “could potentially” or “it appears that” where the analysis supports a firmer claim.
- A summary written for the project team rather than the audience, full of internal project names and abbreviations.
- Holding the recommendation back for the final slide.
Executive summary slide checklist
- Could an executive stop here and decide?
- Does the title or first line state the answer as a position?
- Are there three to five bolded statements, each a full sentence?
- Does each statement carry at least one number or specific fact?
- Does each statement match a section divider later in the deck?
- Is the decision you need stated, with a date if one applies?
- Does it fit on one page without shrinking the text?
Questions
The page right after the title slide that states the whole argument of a presentation: the conclusion, the three to five reasons for it and the decision needed. The rest of the deck supplies the evidence.
Start from the summary your storyline already makes
Arcdeck drafts the whole deck as editable action titles first, with the executive summary up front: your answer, the key reasons and the decision needed, followed by the sections that prove them. Check that the summary and the sections match, change any headline, then let it write and design every slide with charts, key numbers and speaker notes. Upload a PDF, Word or PowerPoint file to build from your own analysis.
No card needed.