Executive summaries fail when they read like an article intro — backstory, context, “the team has been working on…” and the actual ask buried in paragraph 4 where the exec already gave up. These prompts force conclusion-first writing: the decision or the takeaway in line 1, the evidence beneath, and the ask in a place where the exec can act without scrolling. Most should sit under 200 words; anything longer needs a justification of its own. Pair with the cross-team alignment memo prompts when the summary feeds into a multi-team decision.
Best for
- Long-doc TL;DRs
- Decision memos
- Investment / strategy summaries
- Pre-meeting reads
- Status escalations
1. Decision-memo exec summary
Write a 200-word executive summary for a decision memo. Decision: "{decision}". Recommendation: "{recommendation}". Key trade-offs: {paste}. Format: recommendation in line 1, top 3 reasons, top 2 risks, the decision asked of the exec.2. Long-doc TL;DR
Below is a 5,000-word doc on "{topic}". Write a 250-word TL;DR that captures: the question, the answer, the 3 strongest pieces of evidence, the 1 counter-argument and how it is handled.
{paste doc}3. Strategy summary
Write a 300-word executive summary of our {quarter} strategy. Inputs: {strategy doc}. Format: where we are, where we are going, 3 bets we are making, 3 things we are not doing, top metric to watch.4. Status escalation summary
Write a 150-word executive summary for an escalation. Project: {project}. Situation: {state}. Help me lead with the ask: "I need {exec} to {action} by {date}", then evidence, then options I considered.5. Investment-pitch summary
Write a 250-word internal investment-pitch summary asking for {budget / headcount}. Project: {paste}. Output: ask in line 1, expected outcome, 3 supporting reasons, 2 risks, what we will commit to measuring.6. Pre-meeting one-pager
Write a one-page pre-read that makes the upcoming meeting 30% shorter. Meeting topic: "{topic}". Output: state of play, 3 decisions needed, what we recommend, what each decision unblocks.7. M&A / partnership summary
Write a 300-word exec summary of a {acquisition / partnership} opportunity. Inputs: {paste data}. Output: target, strategic fit, top 3 reasons to do it, top 3 reasons not to, recommendation with confidence level.8. Post-incident summary
Write a 200-word post-incident exec summary. Incident: {paste}. Format: impact in line 1, customer-facing severity, root cause, what we did, what we will change. No blame language.9. Customer-feedback rollup summary
Below are 30 customer interview notes. Roll into a 250-word exec summary: top 3 themes (with frequency), top 3 surprising findings, top 3 recommended actions.
{paste notes}10. Competitive-landscape summary
Write a 300-word competitive-landscape exec summary. Players: {list}. Inputs: {paste analysis}. Output: where the market is going, where each competitor is positioning, where we win/lose, recommended response.11. Quarterly results summary
Write a 250-word quarterly-results exec summary. Inputs: {paste metrics}. Format: lead with the headline number vs target, explain biggest mover, list 3 things working, 3 things to address, next-quarter priority.12. Skip-level review summary
Write a 200-word summary for a skip-level review with {senior exec}. My team is doing {paste work}. Format: 1-line state, top 3 outcomes, top risk needing exec air-cover, what I want them to walk away thinking.Common mistakes
- Burying the conclusion
- No specific ask
- Recap instead of summary
- Treating the exec as a peer instead of a decision-maker
- Over 1 page — execs will not scroll
Related
- Weekly report prompts
- Monthly business review prompts
- Meeting agenda prompts
- Handover document prompts
- Project planning prompts
- Executive Update Prompts: 12 Templates Execs Actually Read
- One-on-One Preparation Prompts: 12 Templates Beyond “Anything on Your Mind?”
- Policy Summary Prompts for One-Page Internal Policies