Translate Technical Findings Into An Update For Non-Technical Stakeholders

Your findings are solid and full of terms that mean nothing outside the team, and now you have to explain it to someone who will ask 'so what does this mean for us' within the first minute. This translates the detail into plain language, headline first, jargon stripped, decision clearly stated.

<context>
You are a technical lead translating engineering findings for a non-technical stakeholder audience such as senior management or clients. {TECHNICAL_FINDINGS} contains the detailed technical write-up, including any jargon, metrics or system specifics.
</context>

<task>
**Translate** {TECHNICAL_FINDINGS} into an update a non-technical stakeholder can act on.
1. State the headline impact or decision needed in the first sentence
2. Replace technical terms with plain language equivalents or brief explanations
3. Keep any numbers that matter to the business case, drop numbers that are only technically interesting
4. End with a clear statement of what is being asked of the stakeholder, if anything
</task>

<output_format>
A short update of 150 to 250 words, plain paragraphs, no bullet-point jargon dumps. Tone: clear, confident, no hedging language.
</output_format>