Jun, an engineering lead, needed to build a timeline without a villain. Notes say the export failed at 1 pm, a rollback finished at 2:10, and the cause is still a hypothesis. No person is named as at fault. The first draft looked polished, then it added a line nobody had approved: "Alex caused the outage by being careless."
After this guide you will be able to explain AI incident postmortem in your own words, copy a prompt that fits the job, and catch the extra sentence before anyone else sees it.
What Is AI Incident Postmortem?
AI incident postmortem means using an AI tool to build a timeline without a villain, while a person checks every factual line against a source.
It is not a magic phrase you drop into a chat. It is a short method: one job, one source, one shape, one ban, and one human send. Jun, an engineering lead, is a clear picture of the method. You already have this in the source: 1 pm failure, 2:10 rollback, cause still a hypothesis. The draft is only useful if it stays inside that.
This matters now because the tools are easy to open and the extra sentence is easy to miss. A beginner can produce a page that sounds finished. Sound is not the same as truth. If you remember one definition, remember this: a good draft is one you can point at.
Why AI Incident Postmortem Matters
- You start from something true. You already have this in the source: 1 pm failure, 2:10 rollback, cause still a hypothesis. The guide keeps the draft tied to that, instead of asking the tool to invent a better story.
- You can see the mistake. The mistake in this story is easy to quote: "Alex caused the outage by being careless." Once you can quote it, you can delete it. Vague worry is harder to edit.
- You get a prompt you can reuse. The prompt below is written for this job. Next time you change the notes, not the rules.
- A person still owns the send. Do not blame a person or state a hypothesis as a fact. The tool can draft. It cannot be the name on the email, the post, the file, or the decision.
People searching for postmortem template or blameless timeline prompt are usually stuck on the same gap. They have notes. They do not have a safe way to turn the notes into something they can send. The method below is that way.
How AI Incident Postmortem Works
- Name one job before you name a tool. The job here is simple: build a timeline without a villain. AI incident postmortem starts after that sentence exists. Why it matters: A tool list feels like progress, but the blank page is still there.
- Show the source, then ask for a shape. Notes say the export failed at 1 pm, a rollback finished at 2:10, and the cause is still a hypothesis. No person is named as at fault. The shape is short enough that a colleague can check it quickly. Why it matters: The tool cannot be careful about a fact you never gave it.
- Hunt for one extra sentence. Delete "Alex caused the outage by being careless." and read what remains. If the piece still does the job, that line was never needed. Why it matters: Most bad drafts are fine except for one confident addition.
A useful AI incident postmortem request is a fence, not a wish. The fence has four posts.
- The job. build a timeline without a villain. If you add a second job, the draft will mix them.
- The source. Notes say the export failed at 1 pm, a rollback finished at 2:10, and the cause is still a hypothesis. No person is named as at fault. Anything outside that source stays outside the draft.
- The shape. Say how long the answer should be, and what parts it needs. A shape stops the tool from writing a speech when you needed a note.
- The ban. Do not blame a person or state a hypothesis as a fact. Write the ban in the prompt. Do not hope the tool guesses it.
Here is why the bad line appears. These tools are trained to sound finished. A finished voice will fill a gap. The gap in this story is easy to see: the source has 1 pm failure, 2:10 rollback, cause still a hypothesis, and the draft still said "Alex caused the outage by being careless." That sentence is a hallucination. A hallucination is a smooth line that was not in the source and is not a general fact you already know. It is not a small style choice. It is a new claim.
A postmortem is a timeline you can learn from next week. A villain story feels complete and teaches the wrong lesson. Jun can say what happened at 1 and at 2:10, and that the cause is not confirmed. If a name appears, it should be an owner of a follow-up, not a target. Customer counts you did not pull stay out.
Read the draft the way an editor reads a junior writer. Point at 1 pm failure, 2:10 rollback, cause still a hypothesis for every factual sentence. If you cannot point, delete the sentence. Then the piece is yours.
A Prompt You Can Copy
Use this with Claude. Replace the notes. Do not delete the ban.
Write a timeline from these notes: failed at 1 pm, rollback finished at 2:10, cause is a hypothesis. Do not name a villain. Mark the cause as unconfirmed. Do not add customer counts.The weak prompt, for contrast, was: "Write a postmortem that names who messed up." Keep the weak one in your head only as a warning. Do not paste it.
Best Tools for AI Incident Postmortem
You do not need a large stack. Three tools cover the job. If you are choosing software for a whole company, start with the company buying shortlist after you can do this one task by hand.
Claude
Claude can order the times.
Best for: a first draft when you already have the source
Price: Claude Pro is about $20 a month on Anthropic's pricing page. Confirm before you buy.
How it helps: It turns the source into a draft of this job: build a timeline without a villain.
Good to know: Do not blame a person or state a hypothesis as a fact.
ChatGPT
ChatGPT can draft a second version.
Best for: a colder edit after the first draft
Price: ChatGPT Plus was about $20 a month in public pricing notes, and Pro started near $100. Confirm the live plan on OpenAI's pricing page before you buy.
How it helps: It is good at listing lines that add a fact, including a line like "Alex caused the outage by being careless."
Good to know: Do not blame a person or state a hypothesis as a fact.
Notion AI
Notion AI stores the review.
Best for: a last pass in the tool that fits this file
Price: Check the current price on the vendor page before you buy. This guide does not invent a seat price.
How it helps: It stores the review.
Good to know: Do not blame a person or state a hypothesis as a fact.
Step-by-Step: How to Get Started
Step 1: Write the job in one line
Write: build a timeline without a villain. Put that line above the chat. If you need a second sentence to explain the goal, you are mixing two tasks. Split them. AI incident postmortem works on one task at a time.
Step 2: Bound the source
Notes say the export failed at 1 pm, a rollback finished at 2:10, and the cause is still a hypothesis. No person is named as at fault. Copy only what you are allowed to share. Keep 1 pm failure, 2:10 rollback, cause still a hypothesis visible. Remove passwords, customer lists, health details, and legal files you do not have permission to upload.
Step 3: Use a prompt that draws a fence
Do not start with "Write a postmortem that names who messed up." That prompt asks for a nice tone and leaves the facts open. Paste the prompt from the section above. Then replace the notes with yours.
Step 4: Keep only the version you can point at
Do not blame a person or state a hypothesis as a fact. Read every factual line and point at the source. The version you keep must pass this test: The timeline has the two times and labels the cause as unconfirmed. You send it. The model does not.
When the same shape comes up every week, copy a workflow or a prompt template instead of starting from a blank chat. Change the source. Keep the ban.
Real Examples
Example 1: Jun
Situation: Notes say the export failed at 1 pm, a rollback finished at 2:10, and the cause is still a hypothesis. No person is named as at fault.
What to do: Use the prompt above. Tell the tool the job is to build a timeline without a villain. Reject any line like "Alex caused the outage by being careless."
Why this works: Do not blame a person or state a hypothesis as a fact
Result: The timeline has the two times and labels the cause as unconfirmed.
Example 2: A school
Situation: A drill started late. The notes have times, not a guilty teacher.
What to do: The review lists times.
Why this works: Blame would shut down reporting.
Result: The next drill has a clock.
Example 3: A kitchen
Situation: The oven failed at 6. Dinner service adapted at 6:20.
What to do: The note says those times.
Why this works: Naming a cook as careless is not the repair.
Result: The oven is the issue.
These are practice examples, not customer results. The test is the same in each one: if you cannot point at the source, it does not ship.
Common Mistakes to Avoid
- Opening with "Write a postmortem that names who messed up.". The tool fills the silence with a confident extra claim. Do this instead: Name the job, the source, the length, and the ban in the same prompt.
- Leaving "Alex caused the outage by being careless." because it sounds polite. Polite and untrue is still untrue. The reader may act on it. Do this instead: Delete it, even if the paragraph feels shorter.
- Pasting a whole inbox, folder, or database. You only need 1 pm failure, 2:10 rollback, cause still a hypothesis. Extra text gives the tool more chances to grab the wrong fact. Do this instead: Paste the smallest source that still contains the detail.
- Asking the tool to pick a plan, a price, or a legal conclusion. Those are decisions. A draft can list what the source says. It cannot make the decision for you. Do this instead: Write 'not in the source' and decide yourself, or ask the person who owns the decision.
Quick Comparison
| Option | Best for | Difficulty | Cost | Beginner tip |
|---|---|---|---|---|
| Claude | First draft from a small source | Easy | Free plan, paid if you need more | Paste less than you think |
| ChatGPT | Second pass on a smooth draft | Easy | Check the vendor page | Ask it to mark new claims |
| Notion AI | stores the review. | Easy | Check the vendor page | Do not move secrets into a personal login |
Tips That Actually Help
- Tip 1. Keep 1 pm failure, 2:10 rollback, cause still a hypothesis in the first three lines of the prompt so the model cannot skip it.
- Tip 2. Use verbs of systems: failed, rolled back, hypothesized. Avoid adjectives about people.
- Tip 3. If the draft uses a number, a date, or a name, find it in the source before you keep it. "Alex caused the outage by being careless." fails that test.
- Tip 4. Run the same notes through ChatGPT only after the first draft exists. A second tool is an editor, not a new source of facts.
- Tip 5. Save the prompt in your notes or in the prompt library. Next week, swap the source and keep the ban: Do not blame a person or state a hypothesis as a fact.
FAQ
What is the practical way to do AI incident postmortem?
Start with one source. Notes say the export failed at 1 pm, a rollback finished at 2:10, and the cause is still a hypothesis. No person is named as at fault. Ask for a draft of this job: build a timeline without a villain. Then delete any line the source does not support. The line to practice on is "Alex caused the outage by being careless." The version you keep should match this: The timeline has the two times and labels the cause as unconfirmed.
Why did the draft say "Alex caused the outage by being careless."?
Because the first prompt was too open. "Write a postmortem that names who messed up." asks for a polished result and does not forbid new claims. The tool prefers a complete sound. Do not blame a person or state a hypothesis as a fact. Put that ban in the prompt, then check the draft yourself.
Which tool should I open first?
Open Claude for the first shape. Open ChatGPT when the draft sounds sure and you want extra lines marked. Open Notion AI when the work should stay in that product or needs a different kind of pass. Confirm the live price before you buy.
What should never go into the prompt?
Do not blame a person or state a hypothesis as a fact. Also leave out passwords, payment data, private customer lists, and health or legal records you are not allowed to upload. If you would not email it to a stranger, do not paste it.
Is this useful for a complete beginner?
Yes. You only need an account and one real note. Jun, an engineering lead is not an expert in the story. The skill is the check, not a secret setting. You can practice on a free plan, then pay only if a limit blocks a real task.
The Bottom Line
AI Incident Postmortem is a small, strict way to build a timeline without a villain. Jun, an engineering lead, almost sent "Alex caused the outage by being careless." because the first prompt was vague. The fix was not a new subscription. The fix was a source, a ban, and a read-aloud.
Your next step is small. Open Claude, paste the prompt, and use a note you already have. Keep the draft only if this is true: The timeline has the two times and labels the cause as unconfirmed.
For more walkthroughs, browse the AI tools directory and these related guides: How to Start Using AI Tools and A Runbook for One Failed Task.