Executive Summary Writing
When to Use
- Leadership needs a short decision memo from longer analysis.
- Governance updates must communicate impact quickly.
- Users ask for concise summary of findings, risks, and actions.
- A board, steering committee, or executive sponsor is the audience.
Workflow
- Apply
governance-writing-style-guidebefore drafting. - Identify audience, decision required, and urgency.
- Extract the 1-3 most material findings from source content.
- Quantify business impact (financial, operational, compliance, or risk).
- State key risks and assumptions in plain language.
- Recommend actions with owner and timeline.
- Tighten for brevity and remove implementation-level detail.
Executive Writing Rules
- Lead with decision and implication, not background narrative.
- Use plain language and avoid jargon unless it is standard executive terminology.
- Include numbers only when they change prioritization or decisions.
- Separate facts, assumptions, and recommendations.
- Keep the summary scannable with short sections and bullets.
- Use takeaway-oriented headers that communicate the conclusion.
- If visuals are included, keep them minimal and highlight only the key signal.
Output Template
# Executive Summary: [Topic]
## Decision context
[What decision is needed now and why]
## Key findings
- [Finding 1 with material evidence]
- [Finding 2 with material evidence]
- [Finding 3 with material evidence]
## Business impact
- Financial impact:
- Operational impact:
- Risk/compliance impact:
## Risks and assumptions
- Risk:
- Assumption:
## Recommended actions
1. [Action] - Owner: [Role] - Timeline: [Date/Window]
2. [Action] - Owner: [Role] - Timeline: [Date/Window]
## Requested executive decision
[Explicit approval, choice, or escalation needed]
Acceptance Criteria
- A leader can understand the issue and choose an action in under 2 minutes.
- Findings are prioritized by materiality, not chronology.
- Impact and recommendation are explicit and connected.
- Actions include named ownership and timeline.
Quality Checklist
- Decision ask is explicit and singular where possible.
- Findings are evidence-backed and non-duplicative.
- Risks and assumptions are clearly separated.
- Recommendation language is actionable, not generic.