Turn a Dense Technical Memo into a Plain-English Executive Briefing
Rewrites a technical memo as a two-minute executive briefing that keeps every number and risk, maps jargon to business impact, and ends with the decision needed.
You getBottom line, what is happening and term-to-impact table
Prompt
You are a technical writer who briefs non-technical executives. I will paste a dense technical memo right after this message. Rewrite it as a plain-English executive briefing a leader can read in two minutes.
Rules:
1. Keep every number, date, cost, percentage and risk exactly as written. Do not round, drop or soften any of them.
2. Translate each technical term into its business consequence: money, time, customers, compliance or reputation. If the memo does not state the consequence, write "consequence not stated" instead of guessing.
3. Keep sentences under 25 words. Spell out every acronym once.
4. Add no facts, estimates or recommendations that are not in the memo.
5. If the memo asks for or implies a decision, state it in one sentence with owner and deadline.
Output format:
1. Bottom line (2-3 sentences)
2. What is happening (3-5 bullets)
3. Term-to-impact table: Technical term | Plain meaning | Business consequence
4. Numbers and risks table: Item | Figure from memo | Why it matters
5. Decision needed: one line, or "No decision requested"
6. Questions executives should ask (4-6, each aimed at a gap or risk in the memo)
End with one line listing anything the memo leaves unclear or missing.Example output
Tips and common edits
Why this works
- Forcing every figure to stay exact stops the model from rounding or dropping the risks executives most need to see.
- The term-to-impact table makes jargon answer "so what" in money, time or customers, not just definitions.
- Writing "consequence not stated" instead of guessing exposes memo gaps and feeds the executive questions list.
Use before a leadership meeting or board update. Paste the full memo, including appendices with figures, into ChatGPT, Claude or Gemini right after the prompt. Remove confidential details your policy forbids sharing.
Common edits
- Ask for a 5-sentence email version for leaders who will not open attachments.
- Add a sixth column to the risks table for likelihood if your memo includes risk ratings.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Convert fragmented meeting bullets into clear narrative memo paragraphs
Transform scattered brainstorm bullets into cohesive, professional prose. Use it when updating leaders who prefer structured narrative over raw lists.
Convert technical software features into clear business outcomes
Reframe complex technical release notes into clear commercial benefits. Use it to update sales teams, executives, and clients without technical jargon.
Explain complex technical systems using everyday analogies
Turn dense technical documentation into simple, relatable concepts for non-technical stakeholders. Ideal for product updates, pitches, and customer guides.
Turn technical specs into a help article
Translate complex technical notes and engineer specifications into a friendly, step-by-step troubleshooting guide that everyday users can follow without confusion.
Turn Engineering Notes Into Clear API Documentation
Convert raw technical notes into a structured, professional API endpoint specification including request headers, payload examples, and response codes.
Turn Raw Commit Logs Into Human Readable Changelogs
This prompt transforms technical commit logs into a clean, user-focused changelog categorized by functional impact for your end users.
- Write a Persuasive Executive Memo for Process Changes
- Change the Tone of Any Text to Formal, Casual or Warmer Without Losing Facts
- Generate a Professional README for Your Open Source Project
- Write a How-To Tutorial Blog Post with Checkable Steps and Troubleshooting
- Summarize a Long Article into Key Points, Proven Claims and Open Questions
- Audit a business memo using the Pyramid Principle