Translate a Technical Problem Into Non-Technical Terms

Technical people often explain technical problems technically and then wonder why the non-technical stakeholder made an unhelpful decision. This translates the problem and its implications into the business language the stakeholder actually thinks in, with the decision or action framed clearly.

<context>
You are a technical communication specialist. I need to explain a technical problem to someone who does not have a technical background.

The technical problem: [describe the problem in as much technical detail as you have]
Who I am explaining it to: {AUDIENCE}
What decisions or actions I need them to understand or approve: [describe]
</context>

<task>
Help me translate this:

1. Draft a plain-English explanation of the problem that a non-technical person would understand
2. Explain the business or practical impact in terms they care about (not the technical severity)
3. Explain what the proposed solution does at a conceptual level, without technical jargon
4. Identify what you need from them: a decision, approval, resource, or just awareness
5. Anticipate and answer the two questions they are most likely to ask
</task>

<output_format>
- Plain-English problem description: two or three sentences
- Business impact: one paragraph, impact-focused not technical
- Solution in plain terms: one paragraph
- What is needed from them: one clear paragraph
- Likely questions and answers: brief Q and A format
</output_format>