An executive summary isn't a shorter version of your report — it's a different document with a different reader. Most executives who open it will read only this section, skim the headings after it, and never reach page four. Write it like a preview of your findings and you've written it for the wrong reader.
It's an order problem, not a length problem
Bad executive summaries usually aren't bad because they're bloated — they're bad because of what comes first. Context, then methodology, then findings, then, three paragraphs in, the actual recommendation. By the time a skimming reader reaches it, they've already stopped reading or drawn their own conclusion from the setup. The fix isn't trimming adjectives. It's moving the recommendation from the end of the summary to the start of it.
Lead with the answer, then the reason
Three sentences, in this order, cover almost every executive summary you'll write:
- The recommendation.What you're telling them to do, stated as a decision, not a topic. "We recommend consolidating the two support teams" — not "this report examines the support org."
- The reason, compressed to one or two sentences. The single strongest piece of evidence, not the full case. The full case is what the rest of the document is for.
- What happens next. The decision or approval you need from them specifically, and by when.
A reader who stops after this paragraph should still know what you found and what you want them to do about it.
A paragraph or two, not a page
Treat the length as a real constraint, not a suggestion. If a recommendation and its reasoning can't fit in a paragraph or two, that's usually a sign the recommendation itself isn't settled yet — not that the summary needs more room. A vague recommendation takes a page to explain. A specific one takes three sentences.
Worked example
Buried version:"Over the past six weeks, we conducted interviews with 14 stakeholders across the support and success organizations, reviewed ticket volume and resolution time data going back two quarters, and benchmarked current staffing against three comparable companies. This report summarizes our methodology and findings, and outlines several considerations for leadership as they think through the future structure of the support function..."
Rewritten:"We recommend merging the support and customer success teams under a single lead by Q3. Ticket resolution time is 40% slower when a request crosses both teams, which is happening on nearly a third of tickets today. This requires sign-off from you and the VP of CS by August 20 to hit the Q3 timeline — the full staffing plan and transition timeline follow below."
The second version doesn't hide the methodology — it's still in the report. It just isn't what a skimming reader has to get through first. The free Consulting Proposal Generatorapplies the same lead-with-the-recommendation structure to the objective section of a proposal, so it's not something you have to remember to reorder every time.