The Executive Brief Compressor: Turn a 40-Page Report Into One Page Leadership Will Actually Read
Why this prompt matters
Long reports routinely fail to influence decisions not because the research is weak, but because nobody with decision-making authority reads past the first two pages. Analysts and researchers can spend weeks producing rigorous work that then sits unread in an inbox while a decision gets made on gut instinct instead — the exact outcome the research was commissioned to prevent. A well-built one-page brief is the difference between research that shapes strategy and research that becomes a filed PDF nobody opens again.
What we use it for
You have a 47-page customer research report due to the CEO before Monday's board meeting, and you know from experience that a report this long simply won't get read before the meeting starts. You need the actual findings — the numbers, the causal story, the recommendation — condensed into something a time-pressed executive will read in the elevator on the way to the boardroom.
Prompt
Act as a chief of staff and executive communications specialist who has synthesized hundreds of long reports into one-page briefs for C-suite readers and board members who have five minutes and zero patience for padding. Context — here is what I'm working with: - Full report or key sections: [PASTE THE REPORT TEXT, OR THE MOST IMPORTANT SECTIONS IF THE FULL DOCUMENT IS TOO LONG] - Audience: [WHO IS READING THIS — E.G., CEO, BOARD OF DIRECTORS, A SPECIFIC VP, INVESTOR] - Decision at stake: [WHAT DECISION OR ACTION THIS BRIEF NEEDS TO SUPPORT — E.G., APPROVE BUDGET, GREENLIGHT A LAUNCH, ABANDON A PROJECT] - Why now: [DEADLINE, MEETING, OR EVENT THAT MAKES THIS BRIEF NECESSARY RIGHT NOW] Task: Compress this into a single one-page executive brief that lets the reader make an informed decision without reading the source report. Constraints: - Every claim in the brief must be traceable to something actually stated in the source material — do not infer or invent data points that aren't there. - If the source report doesn't contain enough evidence to support a clear recommendation, say so explicitly instead of manufacturing false confidence. - Use plain, declarative sentences. No jargon unless the audience is technical and the term is unavoidable. - Do not pad. If a section has nothing substantive to say, keep it short rather than filling space. - Target length: this should fit on one printed page (roughly 400-500 words). Output format: 1. **Headline Takeaway** — one sentence stating the single most important conclusion. 2. **Key Findings** — 3 to 5 bullet points, each with a specific number or fact from the source. 3. **Implications** — 2 to 3 sentences on what this means for the business or the decision at hand. 4. **Recommended Actions** — a numbered list, each with a suggested owner and timeframe if the source supports one. 5. **Open Questions or Risks** — bullet points flagging what the report doesn't answer or what could go wrong.
Result
Headline Takeaway
Customer churn in the enterprise tier rose from 4.2% to 7.8% quarter-over-quarter, driven primarily by onboarding friction — not pricing or competition — and is solvable with a $180K onboarding redesign that pays back within two quarters.
Key Findings
- Enterprise tier churn nearly doubled: 4.2% → 7.8% QoQ, representing $2.1M in lost annual recurring revenue.
- 68% of churned accounts cancelled within their first 90 days — the classic onboarding window, not a mid-life renewal decision.
- Exit surveys cite "too complex to set up" as the top reason (41% of respondents), ahead of "found a cheaper alternative" (19%).
- Accounts that completed the guided onboarding flow churned at 2.1%, versus 11.3% for accounts that self-served setup.
- Support ticket volume for onboarding-related issues is up 34% year-over-year, consuming 22% of the support team's total capacity.
Implications
This is a product and process problem, not a market or pricing problem — which means it's fixable without touching revenue strategy. Every quarter this goes unaddressed costs approximately $525K in lost ARR, and support costs will keep climbing as the customer base grows if onboarding stays broken.
Recommended Actions
- Make guided onboarding mandatory (not optional) for all new enterprise accounts — Product team, next sprint.
- Fund a $180K onboarding flow redesign targeting the top 3 friction points identified in exit surveys — Product + Design, Q3.
- Reassign 2 support engineers to a dedicated onboarding response team for the first 90 days of new accounts — Support lead, immediate.
Open Questions or Risks
- The report doesn't break down churn by account size within the enterprise tier — a $50K account and a $500K account may need different onboarding treatments.
- No data on whether competitors have simpler onboarding, which would help confirm this isn't secretly a competitive issue.
A structured prompt that compresses long reports into a single-page executive brief with traceable findings, clear implications, and specific recommended actions — built to survive a five-minute skim from someone who won't read past page two.
Use Case
You have a 47-page customer research report due to the CEO before Monday's board meeting, and you know from experience that a report this long simply won't get read before the meeting starts. You need the actual findings — the numbers, the causal story, the recommendation — condensed into something a time-pressed executive will read in the elevator on the way to the boardroom.
Why It Matters
Long reports routinely fail to influence decisions not because the research is weak, but because nobody with decision-making authority reads past the first two pages. Analysts and researchers can spend weeks producing rigorous work that then sits unread in an inbox while a decision gets made on gut instinct instead — the exact outcome the research was commissioned to prevent. A well-built one-page brief is the difference between research that shapes strategy and research that becomes a filed PDF nobody opens again.