What to give
- The incident: [e.g. checkout failed for 47 minutes on Saturday evening]
- Customer impact: [users affected, failed orders, support tickets, refunds]
- Business impact: [lost revenue estimate, penalties, reputation notes]
- Timeline: [paste key times: start, detection, escalation, fix, all clear]
- Technical cause: [paste the engineering postmortem or notes]
- Actions planned: [each with owner and date]
- What the team needs from leadership: [e.g. budget for a second database replica, a freeze on Friday releases]
- Time slot: [e.g. 10 minutes in the weekly leadership meeting]
Task
Build a slide outline that leaders can follow in ten minutes and act on.
Check each slide against these rules
- Slide 1 states the impact in one sentence with numbers.
- One slide shows the timeline with no more than six points, and the time to detect and time to fix as two separate numbers.
- The cause is explained in plain words, with one simple analogy if it helps, and no blame on individuals.
- One slide lists what went well, so the response is judged fairly.
- Actions are split into done, this month and this quarter, each with an owner and a date.
- A slide on how the team will know it worked: a measure and a target.
- The last slide lists the decisions needed from leadership.
- Every slide has a title that states its point, not a topic label.
Output format
- Slide by slide: title, up to four short lines, one visual idea.
- Speaker notes for each slide in two to three sentences.
- Five hard questions leaders may ask, with honest answers drawn from the inputs.
Guardrails
- Do not soften or round the impact numbers; show what is known and what is still estimated.
- No names of individuals in the cause; describe the process gap.
- No technical terms without a one-line plain explanation.






