Infrastructure Outage Executive Debrief
Draft an executive email summarizing a major engineering incident, root cause, and remediation plan.
Use this template following a critical system outage to communicate incident timelines, business impact, and corrective actions clearly to cross-functional executives. It ensures technical transparency while keeping business leaders aligned on reliability commitments.
Role: Staff Site Reliability Engineer and Incident Commander with 12+ years of production incident management experience.
Context
- Impacted production system: {{service_name}}
- Incident occurrence date and duration: {{incident_date}} lasting {{incident_duration}}
- Root cause category: {{root_cause}}
- Business and customer footprint: {{affected_user_base}}
- Remediation engineering roadmap: {{remediation_steps}}
Task
Draft a concise, high-trust executive incident notification email to business leadership explaining the incident, timeline, core breakdown, and engineering measures taken to prevent recurrence.
Method
- Establish the communication subject line incorporating outage severity, service identifier, and status resolution.
- Summarize the incident in an opening executive overview covering duration and primary customer impact.
- Frame the verified root cause in clear architectural terms accessible to non-engineering leadership.
- Detail the containment actions applied during the incident to stabilize {{service_name}}.
- Enumerate specific preventive engineering workstreams derived from {{remediation_steps}}.
- Highlight SLA metrics and any residual monitoring commitments.
- Provide key ownership contacts and a schedule for the full post-mortem publication.
Constraints
- The email MUST NOT contain unverified speculation regarding hardware or third-party vendor failures.
- MUST present technical details using clear, non-jargon language suitable for C-suite readability.
- Keep the total email body under 450 words.
- Use bulleted lists for impact metrics and action items to maximize scanning efficiency.
Output format
- Subject line format: [INCIDENT DEBRIEF] [SEV Level] {{service_name}} - Status
- Salutation to executive leadership
- Executive Summary (1 paragraph, max 4 sentences)
- Customer & Business Impact (3-4 bullet points)
- Technical Root Cause (1 short paragraph)
- Corrective Action Plan & Ownership (bulleted table or list)
- Next Steps & Post-Mortem Schedule
Self-review
- Did I accurately represent {{affected_user_base}} without exaggerating or downplaying impact?
- Are technical explanations clear without compromising engineering accuracy?
- Are all remediation owners and milestones explicitly structured?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.