wowprompt

Incident review presentation for leadership after an outage

Turns an outage write-up into a short deck for senior leaders: what customers felt, what it cost, why it happened in plain words, and what is being done with owners and dates. Use it when leadership asks for a briefing after downtime, a data issue or a failed release.

An 8-slide incident review deck outline with impact in numbers, a simple timeline, the plain-language cause, actions with owners and dates, and the decisions needed
The output this prompt produced, unedited.

The prompt

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

  1. Slide 1 states the impact in one sentence with numbers.
  2. One slide shows the timeline with no more than six points, and the time to detect and time to fix as two separate numbers.
  3. The cause is explained in plain words, with one simple analogy if it helps, and no blame on individuals.
  4. One slide lists what went well, so the response is judged fairly.
  5. Actions are split into done, this month and this quarter, each with an owner and a date.
  6. A slide on how the team will know it worked: a measure and a target.
  7. The last slide lists the decisions needed from leadership.
  8. Every slide has a title that states its point, not a topic label.

Output format

  1. Slide by slide: title, up to four short lines, one visual idea.
  2. Speaker notes for each slide in two to three sentences.
  3. 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.
incident reviewoutage presentationleadership briefingpost incident reviewreliabilityexecutive update

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity