Turn a technical incident report into an exec-ready brief

A senior exec needs to understand an incident and they do not care about the stack trace. This compresses your report into what happened in one plain sentence, the impact, and the next steps, leaving the root-cause detail out of it. For when you have to brief leadership on something technical without losing them in the first line.

I need to brief a senior executive on a technical incident. They are not technical and need to understand impact and next steps, not root cause details.

Incident report: {INCIDENT_REPORT}
Incident date and duration: {INCIDENT_DATE_DURATION}
Affected systems or services: {AFFECTED_SYSTEMS}
Word limit: {WORD_LIMIT}

Compress this into an executive incident brief with four sections:
1. What happened (one sentence, plain English, no technical acronyms)
2. Business impact (customers affected, revenue at risk, reputational exposure)
3. What we did (response actions taken, in past tense)
4. What happens next (3 concrete actions with owners and dates)

No passive voice. No technical jargon. Write as if explaining to a capable non-technical leader.