post-mortem

A blameless post-mortem standardizes the engineering record of a resolved bug through structured sections like root cause, fix, and action items. It requires inputs such as a reliable repro and validated outcome to ensure accountability and traceability without assigning individual blame.

A standard incident report includes a summary, root cause, how the bug was found, why it slipped through, the fix, validation results, and actionable follow-up items. It references precise code identifiers and links to commits for full reproducibility and future prevention.

You need a reliable reproduction of the issue, a known root cause, an identified fix, and validated outcome results. Providing these inputs allows the post-mortem process to generate a structured artifact with precise analysis and traceable follow-up items.

You need a post-mortem after validating a bug fix or completing a post-incident debugging scenario. It serves as the canonical engineering record for post-release learning, ensuring clear accountability, traceability, and future prevention across teams.

You document why a bug slipped through using the structured 'Why it slipped through' section of a post-mortem. This enables blameless analysis by focusing on systemic gaps and measurable evidence rather than individual errors.