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

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

At a glanceOrders database: today vs managed serviceFigures from the memo
ItemToday (PostgreSQL 11)Managed cloud service
Monthly running cost$3,100$4,700
Security fixesEnd 30 JuneProvider patches
DowntimeNone6 hours overnight
One-time costNone$84,000
Staff effortNot stated2 engineers, 5 weeks

Example for: a platform team memo proposing to move the orders database at a fictional retailer, Larkfield Goods, to a managed cloud service.

1. Bottom line

Our orders database runs on software that loses security updates on 30 June. The platform team wants $84,000 and a 6-hour overnight outage in May to move it to a managed service. Without the move, we carry an unpatched system that processes every customer order.

2. What is happening
  • The orders database runs PostgreSQL 11, which stops receiving security fixes on 30 June.
  • The team proposes moving it to a managed cloud database by 18 May.
  • The move requires one 6-hour window of downtime, planned for 02:00-08:00 on a Sunday.
  • Running costs rise from $3,100 to $4,700 per month after the move.
  • Two engineers would spend about 5 weeks on the project.
3. Term-to-impact table
Technical termPlain meaningBusiness consequence
End of life (EOL)Vendor stops fixing security holesHigher breach risk on order and payment records
Managed serviceCloud provider runs patching and backupsFewer staff hours on maintenance; consequence not stated in hours
Replication lagDelay before backup copy catches upUp to 15 minutes of orders could be lost in a failure
Cutover windowTime the site cannot take orders6 hours of no online sales
4. Numbers and risks
ItemFigure from memoWhy it matters
One-time cost$84,000Not in current quarter budget
Monthly cost change$3,100 to $4,700Adds $19,200 per year
Downtime6 hoursLost sales during window
Security fix deadline30 JuneAfter this, known flaws stay open
Rollback time if migration fails2 hoursExtends outage to 8 hours
5. Decision needed

CFO and CTO to approve $84,000 and the 18 May outage window by 25 April.

6. Questions executives should ask
  1. What revenue do we normally take between 02:00 and 08:00 on a Sunday?
  2. What happens if we miss 30 June: what is the realistic exposure?
  3. Has the rollback plan been tested, and by whom?
  4. Does the $4,700 monthly cost include backups and support?
  5. Which other projects slip while two engineers spend 5 weeks on this?

Unclear or missing: the memo gives no estimate of lost sales during the outage and no fallback date if 18 May fails.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Writing
Writing

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.