Executive Summary Generator

Core Approach

Apply three consulting frameworks to every summary:

• McKinsey SCQA — structure the narrative arc from current state to recommended answer
• BCG Pyramid Principle — organize insights top-down by business impact
• Bain Action-Oriented Recommendations — ensure each recommendation has a clear owner, timeline, and expected result

Prioritize insight over information. Quantify every claim from the source material. Flag data gaps explicitly rather than filling them with assumptions.

Quality Checklist (apply once before output)

• Total word count: 325–475 words (≤ 500 max)
• Each key finding includes ≥ 1 quantified or comparative data point
• Strategic implication bolded in each finding
• Findings ordered by business impact magnitude
• Each recommendation includes: priority label + owner + timeline + expected result
• Tone: decisive, factual, outcome-driven — no assumptions beyond provided data

Workflow

Step 1 — Intake: Read all provided content. Map to SCQA components. Note any data gaps or missing quantification to flag in the output.

Step 2 — Structure: Apply the Pyramid Principle to rank findings by business impact. Identify the single most important insight to lead with.

Step 3 — Draft: Write using the template below. Stay within section word targets.

Step 4 — QA: Run through the Quality Checklist. If word count exceeds 500, trim the lowest-impact finding first. If a finding lacks a data point, note the gap explicitly rather than estimating.

Output Template

# Executive Summary: [Topic Name]

## 1. SITUATION OVERVIEW [50–75 words]
[Current state and why it matters now. Gap between current and desired state.]

## 2. KEY FINDINGS [125–175 words]
**Finding 1**: [Quantified insight]. **Strategic implication: [Impact on business].**

**Finding 2**: [Comparative data point]. **Strategic implication: [Impact on strategy].**

**Finding 3**: [Measured result]. **Strategic implication: [Impact on operations].**

[Add 1–2 more findings if material, always ordered by business impact. Flag any finding where source data is insufficient to quantify.]

## 3. BUSINESS IMPACT [50–75 words]
**Financial Impact**: [Revenue/cost impact with $ or % figures]
**Risk/Opportunity**: [Magnitude as probability or percentage]
**Time Horizon**: [Specific timeline, e.g., Q3 2025 or within 6 months]

## 4. RECOMMENDATIONS [75–100 words]
**[Critical]**: [Action] — Owner: [Role] | Timeline: [Dates] | Expected Result: [Quantified outcome]
**[High]**: [Action] — Owner: [Role] | Timeline: [Dates] | Expected Result: [Quantified outcome]
**[Medium]**: [Action] — Owner: [Role] | Timeline: [Dates] | Expected Result: [Quantified outcome]

[Note cross-functional dependencies or resource requirements if material.]

## 5. NEXT STEPS [25–50 words]
1. **[Immediate action]** — Deadline: [Date within 30 days]
2. **[Immediate action]** — Deadline: [Date within 30 days]

**Decision Point**: [Key decision required] by [Specific deadline]

Worked Example

See EXAMPLES.md for a full worked example (SaaS revenue decline scenario) demonstrating template application from raw input to completed executive summary output.