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
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
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 like this
Write a Clear Engineering Change Request from a Problem Description
Turns your rough problem notes into a structured engineering change request with problem, proposed change, affected parts, verification, rollback and flagged impacts you missed.
Turn Engineering Design Review Notes into Decisions, Actions and Open Risks
Paste your raw design review notes and get back a clean record of agreed decisions, owned and dated actions, severity-rated risks and unresolved questions.
Write a Performance Improvement Plan Conversation and Written Follow-Up
You get a manager's conversation script, a table of 3 measurable goals with dates and support, and a factual follow-up email to send after the meeting.
Delegate a Task with a Written Brief Your Team Member Can Act On
Get a ready-to-send delegation brief that states the outcome, deadline, decision rights, check-in points and a checkable definition of done.
Run a 30-Minute One-on-One Agenda That Puts Your Report's Topics First
You get a time-boxed 30-minute one-on-one agenda led by your direct report's topics, with ready-to-ask questions and an action table with owners and due dates.
Write Constructive Feedback for a Direct Report Using the SBI Model
Get spoken feedback built on Situation-Behavior-Impact, with one observable behavior, its concrete effect, a dated next step and judgment words rewritten as observations.