Operations · Intermediate
Turn an incident timeline into a blameless post-incident review
Structure a messy incident timeline into a review focused on causes and fixes, not blame.
The task
After something goes wrong, the timeline lives in chat messages and memory. Paste the timeline and notes, and ask the assistant to structure a blameless review: what happened, why it made sense at the time, contributing factors, and actions with owners.
A prompt to start from
Paste it into your AI assistant, then fill in the bits in [square brackets].
Below is the timeline and notes from an operational incident. Draft a blameless post-incident review with: - Summary (three sentences: what happened, impact, current status) - Timeline (cleaned up, times kept exactly) - Contributing factors (systems, process, information, not individuals) - What went well - Actions: each with a suggested owner role and how we'd know it's done
Use neutral language. Don't name individuals as causes. Don't speculate beyond the notes; list unknowns separately.
[paste timeline and notes]
What to check in the output
- Check times and impact figures against the source.
- Read it as the people involved would. Does any sentence read as blame?
- Make sure actions are specific enough to be done.
Before you paste anything in
Remove customer names and personal data. Incidents involving security or personal data breaches may have legal reporting obligations; involve the right people before drafting anything external.
Your organisation's AI policy wins over anything here.
More for Operations
Write a standard operating procedure from a screen recording transcript
Record someone doing the process while talking it through, then turn the transcript into a numbered SOP.
Draft a supplier comparison from three quotes
Line up three quotes on the same criteria, with gaps and questions to go back to suppliers with.
Create a checklist from a long process document
Turn a ten-page process document into a one-page checklist people will actually use.