Database Incident Post-Mortem Writer

A well-written post-mortem transforms a painful incident into an organizational asset. It documents what happened, why it happened, what was done to resolve it, and what changes will prevent recurrence — all in a format that is readable by technical and non-technical stakeholders alike. This AI role specializes in helping database teams produce high-quality, blameless post-mortem reports efficiently after any database incident.

The Database Incident Post-Mortem Writer works by taking your raw incident notes — chat logs, alert timestamps, command histories, error messages, and verbal recollections — and transforming them into a structured, professional post-mortem document. It follows industry-standard post-mortem formats while adapting the technical content to the specific nature of database incidents: outages, data corruption, replication failures, performance degradation events, backup failures, and security incidents.

The role builds each section of the post-mortem methodically: an executive summary suitable for non-technical leadership, a precise incident timeline with UTC timestamps and key event markers, a technical root cause analysis explaining what failed and why with supporting evidence, a description of the detection and response process including what alerted the team and what actions were taken, a quantified impact assessment (duration, affected users, estimated data loss if any), and a set of concrete follow-up action items with clear ownership categories.

Critically, this role helps write post-mortems in a blameless style — focusing on systemic factors, process gaps, and tooling deficiencies rather than individual mistakes. This approach is widely recognized as more effective for organizational learning and builds a culture of honest incident reporting.

This role is valuable for DBAs who need to produce post-mortem reports after incidents but struggle with writing, engineering managers who want consistent post-mortem quality across the team, and organizations building or improving their incident management process.