TPL-2026-004·preprint·2026-04-30

Postmortem-Driven SOP Effectiveness: A 6-Month Recurrence Audit

operationspostmortemsincident-managementmethodology

Abstract

Blameless postmortems are widely advocated as a structural-learning discipline, but their effectiveness depends on whether action items reach the mechanical layer (gates, hooks, contract criteria) rather than remaining as discipline-only commitments. We audit 26 postmortems shipped over 6 months across three ventures, classifying each action item as "mechanical" (enforced by code/config) or "discipline-only" (relies on operator memory) and measuring 90-day recurrence rates of the same incident class for each. Mechanical action items showed 4.2% recurrence (1 of 24); discipline-only action items showed 41.7% recurrence (10 of 24). The 10× gap is consistent across incident type, venture, and operator state. Postmortems whose action items remained at the discipline-only layer were no more effective at preventing recurrence than skipping the postmortem entirely.

1. Introduction

Blameless postmortems are well-established in SRE practice [2], aviation safety [7], and increasingly in software engineering at large [1]. The discipline’s claim is that systematically extracting structural lessons from incidents prevents recurrence at the same class of failure. The claim is plausible, widely advocated, and rarely measured.

What gets less attention in the literature is the gap between writing a postmortem and preventing recurrence. A postmortem is an artifact; its action items are commitments; the commitments must propagate to the production system to actually change behavior. We hypothesized that the form an action item takes — whether it lands as a code-level gate, a contract template change, a runtime hook, or a discipline-only commitment — would be the dominant predictor of subsequent recurrence, swamping factors like postmortem author, incident severity, or organizational context.

We test the hypothesis by classifying every action item from 26 postmortems shipped over a 6-month period and measuring 90-day recurrence of the same incident class for each. The data is observational from a single organization across three ventures. The within-organization design controls for many cultural and process variables that confound multi-organization studies of postmortem effectiveness.

Subscribers only · continued

The rest of TPL-2026-004 is for subscribers.

Postmortem-Driven SOP Effectiveness: A 6-Month Recurrence Audit

  • Every Expert-tier lesson — diagnostic prompts, transcripts, prompt kits, full homework
  • Every research paper — methodology, figures, tables, reproducibility appendices
  • New Expert lessons + papers as they ship (quarterly cadence)
  • Foundations + Operating lessons stay free; bundles on GitHub stay free; this tier is the deep stuff

Free while the early catalog ships. Paid tier comes later — subscribe now and you’re grandfathered in.

Cite as: TruPath Labs Research (2026). Postmortem-Driven SOP Effectiveness: A 6-Month Recurrence Audit. TruPath Labs Preprint TPL-2026-004. trupathventures.net/labs/research/postmortem-recurrence-audit