Write a Blameless Post-Mortem from Your Incident or Project Failure Timeline
Paste your incident notes and get a structured blameless post-mortem with a timeline, a five-whys root cause analysis and preventive actions owned by roles, not people.
You getSummary, impact and timeline
Prompt
You are an experienced incident review facilitator who runs blameless post-mortems for engineering, operations and project teams.
I will paste my notes about an incident or failed project right after this prompt: timeline fragments, chat logs, metrics or a rough summary. Turn them into a blameless post-mortem.
Rules:
1. Build the timeline in chronological order with timestamps. Mark any time you inferred with "(approx.)".
2. Describe actions by role or system, never by a person's name, and never name a person as the root cause. If my notes blame someone, reframe it as the condition that made the error possible.
3. Run five whys on the main failure. Each why must cite a fact from my notes. Stop early and say so if the notes do not support the next step.
4. Every preventive action has an owner role, a due window, and a type: Prevent, Detect or Mitigate.
5. Do not invent metrics, customer counts or quotes. If impact numbers are missing, write "Unknown - confirm".
Output format:
1. Summary (3 sentences: what happened, impact, current status)
2. Impact
3. Timeline (table: Time | Event | Source)
4. Root cause analysis (numbered five whys)
5. Contributing factors
6. What went well
7. Preventive actions (table: Action | Type | Owner role | Due | Priority)
8. Open questions
End with one line naming the biggest gaps in my notes the team should fill before sharing this.Example output
Tips and common edits
Why this works
- Forcing role-based language and reframing blame into conditions keeps the review blameless and focused on systems, not people.
- Requiring each 'why' to cite a fact from your notes stops the model from guessing a tidy but invented root cause.
- Tagging actions as Prevent, Detect or Mitigate shows whether you fixed the cause or only made the next incident shorter.
Use within a few days of an outage, missed launch or failed project. Have your Slack thread, alert times and rough notes ready to paste into ChatGPT, Claude or Gemini, then review the draft with the team before circulating.
Common edits
- Ask for a one-paragraph executive summary version to share with leadership.
- Replace the five whys with a fishbone breakdown for complex project failures with many causes.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Find Why Customers Return Products Using Your Return Reasons Data
Groups your pasted return reasons into root causes, estimates what each cause costs, and pairs each with a product page, packaging, or sizing fix ranked by cost.
Turn Messy Meeting Notes into Minutes with Decisions, Owners and Deadlines
Get clean meeting minutes that separate decisions from discussion, list action items with owners and dates, and flag every gap instead of guessing.
Write a Polite Email to a Supplier About a Late, Short or Damaged Delivery
Get a firm, friendly supplier email that lists the exact shortfall and its impact, asks for one remedy by a set date, and includes a follow-up line.
Build a Tight Meeting Agenda with Timeboxes, Owners and a Clear Decision Goal
You get a meeting agenda with a one-sentence decision goal, timed items with owners, pre-reads, and a list of topics cut to email instead.
Choose Between Business Options with a Weighted Decision Matrix
You get a weighted scoring table that shows the math, a ranked result, the smallest change that would flip the winner, and the top risks with mitigations.
Turn a Task Description Into a Step-by-Step SOP a New Hire Can Follow
You get a complete standard operating procedure with verb-first numbered steps, decision points, a quality checklist and a common-mistakes table.