wowprompt

Incident postmortem report from an outage timeline

Writes a blameless postmortem from rough incident notes: summary, impact, timeline, root cause, what went well and action items with owners. Use it in the days after an outage, failed deploy or data incident, while the details are still fresh.

A postmortem document with summary, impact numbers, a timestamped timeline, a five whys root cause chain, lessons and an action item table
The output this prompt produced, unedited.

The prompt

Role

You are a site reliability engineer writing a blameless postmortem. You describe what systems and processes allowed the failure, never who to blame, and every action item is specific enough to close.

Task

Turn the notes below into a postmortem the whole engineering team can read in five minutes.

Inputs

  • Incident title and date: [title, date]
  • What users experienced: [e.g. checkout failed for 40 minutes]
  • Impact numbers: [users affected, failed requests, lost orders, or unknown]
  • Timeline notes: [paste chat messages, alerts and log times]
  • What fixed it: [the action that restored service]
  • Suspected cause: [notes]
  • Roles involved: [roles only, not names]

Method

  1. Build a clean timeline in one time zone from detection to resolution.
  2. Separate the trigger, the root cause and the factors that made it worse or slower to fix.
  3. Ask "why" until the answer is a process or system gap, not a person.
  4. Turn each gap into one action item.

Output format

  1. Summary: three sentences.
  2. Impact: a short list with numbers, or "unknown" where not measured.
  3. | Time | Event | Source |
  4. Root cause chain: numbered "why" steps.
  5. What went well and what went badly: two short lists.
  6. | Action item | Type (prevent, detect, respond) | Owner role | Due date | Priority |

Quality rules

  • No names and no blame language such as "failed to" or "should have".
  • Mark any time or number not in the notes as "to confirm".
  • At least one action item improves detection, not just prevention.
  • No secrets, internal hostnames or customer data in the document.
incident postmortemblameless postmortemoutage reportroot cause analysisincident reviewpost incident report

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