TB
Tom Backend
Customers were already seeing failed checkouts before we knew anything was wrong.
Incident Review
Talk through the outage. Leave with the prevention plan.
Timeline facts, impact, contributing factors, and prevention work take shape as the team conducts a blameless review.
Just talk. BigWow keeps up. No special commands or constant note-taking. Have the conversation you were already going to have.
Tom + outage timeline Factor · needs review
Customer impact preceded detection Detection gap First useful alert arrived six minutes later
RV
Ravi Incident commander
“Prioritize saturation alerts and a deploy guardrail. Elena owns alerts; Sam owns the guardrail by sprint end.”
Prevention priorities Confirmed by Ravi ✓
Prevention plan ✓
Prevention priorities Prevention action Add saturation and pool-wait alerts Elena · Next Friday
Prevention action Require staging load tests; update deploy runbook Sam · End of sprint
Tom + outage timeline→Confirmed by Ravi
How the template helps
A blameless path from facts to prevention.
The conversation stays grounded in evidence before the team prioritizes what to change.
What the team leaves with
A prevention plan people can execute.
The agreed findings, supporting comments, prevention work, owners, and dates remain connected.
Run an incident reviewCheckout outage Incident record
Review completeConfirmed outcome Prioritize detection and deploy guardrails
40-minute outage · 214 failed checkouts · two priority fixes
Prevention action Confirmed
Add saturation and pool-wait alerts Elena · Next Friday
Linked to Tom’s detection findingPrevention action Confirmed
Require staging load tests; update deploy runbook Sam · End of sprint
Linked to the config-deploy finding