Explain a Technical Engineering Problem to Non-Technical Managers in a One-Page Brief

Turns your pasted technical notes into a one-page brief with plain-English context, business impact, a costed options table and one clear recommendation.

You getTitle, what is happening and why it matters

Prompt

Prompt
You are a senior engineer who regularly briefs executives and project managers on technical problems. After this message I will paste technical detail about a problem: notes, logs, a ticket thread or part of a design doc. Turn it into a one-page brief that a non-technical manager can read in two minutes and act on.

Rules:
1. Every technical term you keep gets a plain-English explanation in the same sentence. Drop any term that is not needed for the decision.
2. State impact in the manager's terms: days of schedule, money, customers affected or risk of failure. Use only figures from my material. Where a number is missing, write "estimate needed" instead of guessing.
3. Give 2-3 options. For each, say what it fixes, what it does not fix, its cost or time, and its main risk.
4. Make one recommendation and explain why in two sentences or fewer.
5. Keep the whole brief under 350 words.

Output format:
- Title: the problem in under 12 words
- What is happening (3 sentences max)
- Why it matters (bullets on business impact)
- Options (table: Option | What it fixes | Cost / time | Main risk)
- Recommendation
- Decision needed from you, and by when

End with one line that lists the assumptions you made and any information missing from my notes.

Example output

Example for: a hardware engineer at a fictional warehouse-robotics firm, Corvane Robotics, whose drive motors overheat during long shifts.

Drive Motors Overheating on Model R4 Robots During Long Shifts

What is happening
The motors that move our R4 robots get too hot after about 6 hours of continuous work, and the robot shuts itself down to protect them. The cause is a cooling fan part from our new supplier that moves about 30% less air than the old one. The shutdowns are a built-in safety step that stops permanent damage, so no robots have been harmed yet.

Why it matters

  • 3 customer sites run 8-hour shifts and saw 41 unplanned shutdowns last month.
  • Each shutdown stops a robot for about 25 minutes while it cools down.
  • 120 R4 units are scheduled to ship to Halden Logistics on 14 June.
  • Lost customer throughput in dollars: estimate needed.

Options

OptionWhat it fixesCost / timeMain risk
A. Go back to the original fan supplierRemoves the root cause on all new units$18 per unit more; 3 weeks to restockShip date to Halden slips about 10 days
B. Software update that slows robots slightly when warmPrevents shutdowns on units already deployed2 engineer-weeks; no parts costRobots run about 8% slower near end of shift
C. Do both: software now, fans for new buildsCovers deployed and new units$18 per unit plus 2 engineer-weeksMost work at once; needs QA time we have not booked

Recommendation
Choose Option C. The software update stops customer shutdowns within two weeks, and switching fans fixes the cause before the problem spreads to the Halden fleet.

Decision needed from you, and by when
Approve about $2,160 in extra parts cost for the Halden order, and accept a possible 10-day slip, by Friday 24 May so purchasing can place the fan order.

Assumptions and gaps: I assumed all 120 Halden units use the new fan. Customer-side cost of downtime and QA capacity for June were not in the notes.

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

Tips and common edits

Why this works

  • Forcing impact into days, dollars and customers puts the brief in the units managers use to decide.
  • The rule to write "estimate needed" instead of guessing keeps invented numbers out of a document used for real decisions.
  • Ending with a decision and a deadline turns an explanation into an action the manager can take.

Use this before a status meeting or escalation email. Paste your raw notes, ticket thread or logs into ChatGPT, Claude or Gemini right after the prompt. Include any known costs and dates so the brief can use them.

Common edits

  • Ask for a 5-line version to paste into Slack or an email subject plus body.
  • Add your manager's main concern (budget, launch date, safety) so the brief leads with it.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Career & Job Search