What this covers
A 20-minute AI workflow to compress a 30-page report or 90-minute meeting into a 1-page exec summary that survives the C-suite skim test.
Who this is for
Anyone presenting up — PMs, analysts, founders preparing board / leadership materials.
When to reach for it
When you have substantial content (long report, big meeting, deep analysis) and 15 minutes of C-suite attention. If the next step is presenting the same material live, pair this with the 10-slide work-presentation outline workflow so the summary and the deck carry the same single message.
Step by step
Every step ships a copy-paste prompt. Replace <...> with your real info.
-
Upload source + lock audience. Attach report PDF / transcript / deep doc in the same chat, then send:
The attachment is <type, e.g. "30-page market report" / "90-min board transcript" / "compilation of 12 user interviews">. Audience: <e.g. "CFO. Cares about cost, risk, timeline. Not familiar with product detail."> Scenario: <e.g. "Decides Tuesday whether to approve $2M extra budget. Has 15 minutes."> Voice: <direct, no adjective stacks, no buzzwords> Before generating anything, tell me: 1. Your read of the source's structure (≤3 sentences) 2. Which 3 parts are most relevant to <audience> and which 3 parts are largely irrelevant 3. What's missing that would let you write a summary that's actually useful for <audience> Do NOT generate the summary itself yet. -
Force the “why” — what decision do you want?
Based on the source and audience, give me 3 candidate "decisions the reader should make" — each as verb + object + how-to-measure. Examples: - Approve / reject the $2M Q3 channel budget - Move "renew vs switch" to the next monthly review - Hold the status quo (no action) Do NOT give vague "be informed" / "for reference" framings.Pick one ask. Even if AI picks wrong, you now know what to correct.
-
3-bullet TL;DR: conclusions only, no descriptions:
The ask is: <selected ask from previous step> Now write a 3-bullet TL;DR. Each bullet must: - Be a judgment / conclusion, not a description ("X grew 22%" is description; "X grew 22%, above renewal threshold" is judgment) - ≤14 words - Not repeat points across bullets - Bullet 1 directly answers the ask; bullet 2 gives critical nuance; bullet 3 names risk / next step -
Evidence layer: one sentence per bullet, must carry a number:
Continuing from the 3-bullet TL;DR, write 1 evidence sentence per bullet: - Must include a specific number / date / source citation (e.g. "report p.14") - No vague intensifiers ("significantly", "substantially", "materially") without magnitude - After the number, 1 short subordinate clause on why that number matters - ≤25 words per sentence -
Counter-view: “if I’m wrong, most likely because”:
Write 1 sentence of "counter-view / risk": if the TL;DR conclusion is wrong, what's the most likely reason? Requirements: - Not a catch-all ("macro changes", "market risk" — these say nothing) - Must point to 1 observable leading indicator (e.g. "If Q3 new logos < 8, this conclusion fails") - ≤20 words -
Hand-write the opening 2 sentences. AI’s openings are 90% “This report is based on…” / “Following recent analysis…” filler. Write your own:
Sentence 1: tell the reader, in 1 line, what decision they have to make after reading. Example: "By month-end, you decide: renew SaaS platform Y, or switch to in-house." Sentence 2: give your recommendation directly ("I recommend..."). Example: "Based on the last 90 days of cost and reliability data, I recommend renewing for 12 months." -
Force 1 page. Stitch TL;DR + evidence + counter-view + your 2-sentence open. Body (excluding header) must be ≤ 250 words. Over budget? Cut with this prompt:
Below is a summary draft, currently <X> words, target ≤250 words. <paste draft> Cut to target length. Rules: - No font shrinking. No translation tricks. - Don't delete numbers, decisions, or counter-view. - You CAN delete: adjective stacks, transition sentences, "as you can see" lead-ins. - Break long subordinate-clause sentences into two short ones. - Keep all [p.14]-style citations. Return the final version + how many words you cut. -
Send + archive as template. Save this round’s source + ask + the prompt chain to
exec_summary_templates/<topic>.md. Next quarterly review or board update: swap the source file and the ask, reuse everything else.
Recommended workflow
Source + audience context → 1-line ask → 3-bullet TL;DR → evidence layer → counter-argument line → human-written open → 1-page length check → ship. If you are drafting the summary on the move, the ChatGPT voice workflow covers how to use Voice mode to talk through the 1-line ask and counter-argument before you sit down to write.
Common mistakes
- No 1-line ask — readers don’t know what to do
- Burying the strongest evidence in paragraph 4
- Skipping the counter-argument — looks naive to senior readers
- Letting AI write the open — generic, executives smell it
Practical depth notes
For AI Executive Summary Workflow: A Page That Earns the Next Meeting, treat the workflow as a small controlled run before trusting it on real work. Start with one representative input, define what a good result must include, and keep the original beside the AI output so you can see what changed. The model should explain tradeoffs, assumptions, and weak spots instead of only producing a cleaner-looking answer.
The safest review pattern is: run once for structure, once for quality, and once for risks. Check facts, names, numbers, links, file paths, and commands manually. If the output affects users, money, legal terms, production code, or published claims, keep a human approval step even when the draft looks confident.
FAQ
- Is 1 page really enough?: For C-suite, yes. If they want more, they ask.
- Bullets or prose?: TL;DR bullets; supporting layer prose. Mixed format reads fastest.