What is a postmortem in DevOps?
⚡
Quick Answer
A postmortem is a structured, written retrospective of an incident — its timeline, impact, contributing factors, and action items — done to learn and prevent recurrence rather than to assign blame.
Detailed Answer
A good postmortem documents what happened, why (systemic contributing factors, not a single scapegoat), how it was detected and resolved, and concrete, owned, tracked follow-ups. Sharing them widely spreads learning. The blameless framing is what makes people honest enough to surface real causes.
💡
Interview Tip
Emphasize blameless + tracked action items — a postmortem without follow-through is just a document.
postmortemincidentlearning