Executive Summary (Dense Information, Quick Read)

This prompt creates executive summaries that extract key decisions, risks, and recommendations from longer documents. It front-loads critical information, uses visual hierarchy, and respects that executives need just enough context to make informed decisions quickly.

GPT / Claude / Gemini4 variables

Prompt

Create an executive summary for {DOCUMENT_TOPIC}.

Input:
- Topic: {TOPIC}
- Key finding/recommendation: {FINDING}
- Decision needed: {DECISION}

Rules:
- Maximum one page
- Lead with recommendation/ask
- Use bullets and hierarchy
- Quantify impact
- Include risks and next steps

Output format:
SITUATION (2-3 sentences)

RECOMMENDATION / ASK
- Primary recommendation
- Key rationale (3-4 bullets)

IMPACT
- Financial/timeline/resource impact
- Risks and mitigations

NEXT STEPS
- Action items with owners
- Decision points

Topic: {DOCUMENT_TOPIC}
Finding: {FINDING}
Decision: {DECISION}

Quick brief

Purpose

Distill complex documents into summaries executives will actually read.

Expected output

A one-page summary containing: situation in 2-3 sentences, key recommendation or ask, supporting rationale in bullets, risks and mitigations, financial or timeline impact if relevant, and explicit next steps with owners.

Customize before copying

Replace these placeholders with your own context before you run the prompt.

{DOCUMENT_TOPIC}{TOPIC}{FINDING}{DECISION}

Works well with

GPT

Claude

Gemini

Variations

Add visual layout suggestions (boxes, callouts).

Include options analysis (3 choices with pros/cons).

Make it investor-focused (TAM, traction, ask).

Add appendix section for supporting data.

What this prompt helps you do

When to use it

Use when presenting proposals, reports, or analyses to senior leadership. Essential before board meetings, investor presentations, or any situation where busy decision-makers need the essence without the details.

How it works

The prompt identifies the core message, extracts decision points, highlights risks and opportunities, and presents everything in scannable format. It assumes the reader may not have time for the full document and structures content for progressive disclosure.

Best practices

Keep to one page maximum. Lead with recommendation or ask. Use bullets and visual hierarchy. Quantify impact when possible. Include one-sentence rationale for key points. Attach full document for those who want details.

Common mistakes

Writing mini-versions of the full document. Burying the recommendation. Using jargon without context. Not quantifying impact. Forgetting to include clear next steps. Making it too dense to scan.

What you should expect back

Limitations

Can't capture all nuance from complex documents. Assumes executive has baseline context. Works best for business decisions, less effective for technical deep-dives. Requires good judgment about what to include.

Model notes

Compatible with all major models. GPT creates clear hierarchical structure. Claude maintains appropriate brevity. Gemini sometimes over-simplifies. Works for any document type.

Real-world applications

Consultants use this for client deliverables. Product managers use it for strategy documents. Finance teams use it for investment proposals. Operations teams use it for process change proposals. Analysts use it for research reports.

How to tell if it worked

Successful summaries mean executives make informed decisions without reading full documents, meetings stay focused on decisions rather than rehashing details, and follow-up questions are about decisions rather than clarifications.

Where to go next

Use Email to Executive for the cover email. Pair with Technical Explainer for technical decisions. Follow with Meeting Agenda if presenting in person.

Appears in collections

User Research Synthesis (Insights to Action)

Turn user interviews and feedback into clear insights and product decisions.

Write emails that busy executives actually read and respond to.

Rewrite for Clarity (No Fluff, Same Meaning)

Make text sharper, shorter, and harder to misunderstand.

Technical Explainer (For Non-Technical Stakeholders)

Explain technical concepts without losing clarity or dumbing down.

Stakeholder Communication Plan (Right Message, Right Time)

Design communication strategies that keep stakeholders informed without overwhelming them.

Data Storytelling Distiller (Insights → Impact)

Transform raw data analysis into compelling narratives that convince stakeholders and drive decisions.