Skip to main content

> postmortem_action_item_governance

Postmortem Action Item Governance

Why do companies experience identical repeat outages despite conducting thorough blameless postmortems?

Stack: DELIVERY THEATER STACK →Staff+ (L6+)anti-pattern

⚡THE SHORT ANSWER

Because postmortem action items are filed into Jira and forgotten without strict completion SLAs, allowing the underlying systemic vulnerabilities to trigger repeat catastrophes.

Engineering Handbook & Failure Dynamics

6-Dimensional Architecture Breakdown

⚙️1. Underlying Mechanism

Execution

A postmortem without executed action items is mere delivery theater. High-performing engineering organizations treat postmortem action items (P0/P1 remediations) with the same urgency as active Sev-1 bugs. Action items must be scoped, assigned to specific squad backlogs, and tracked against strict completion timelines (e.g., P0 within 7 days, P1 within 30 days) with executive visibility.

🎯2. Appropriate Use Context

Scope

Mandatory post-incident tracking process for all organizations striving to prevent repeat outages.

⚠️3. Production Failure Modes

P0 Risk

A database failover failure that caused a 4-hour outage in January happens again in April because the ticket to automate DNS propagation was deprioritized for marketing features.

📡4. Diagnostic Signals & Telemetry

Telemetry
  • ✓

    Postmortem tickets open for >60 days in Jira

  • ✓

    incident reviews referencing identical root causes from previous quarters

  • ✓

    zero tracking of action item completion rates

🛡️5. Prevention & Safeguards

Safeguards

Institute a strict policy: any team with an overdue P0 postmortem action item cannot deploy new features to production until the remediation is merged and verified in staging.

⚖️6. Architectural Trade-offs

Trade-off

Requires reserving immediate sprint bandwidth for reliability fixes following major outages, temporarily postponing planned feature work.

📋

Case Study (TinyCTO In-Field Example)

REAL-WORLD TELEMETRY

TinyCTO Episode 28: A payment timeout crashed checkout twice in two months. The CTO mandated that P0 action items block all sprint releases. The automated circuit breaker was built in 3 days, eliminating the failure permanently.

Interactive Concept Drills

3 Cards
Q1

What is the primary risk of uncompleted postmortem action items?

The identical systemic defect will inevitably cause another catastrophic production outage.
Q2

What is the recommended completion SLA for a P0 postmortem remediation?

Within 7 to 14 days following the publication of the postmortem review.
Q3

How should leadership track postmortem action item health?

Through weekly engineering health reviews tracking completion percentage, overdue tickets, and repeat incident rates.

Postmortem Action Item Governance — Technical FAQ

How many action items should a single postmortem generate?

Focus on 2 to 5 high-impact, high-leverage preventive items rather than creating a laundry list of 30 minor tasks.

Who is responsible for verifying that an action item actually solved the problem?

The assigned engineering squad, verified through automated tests or chaos injection during the subsequent review cycle.

What distinguishes a good postmortem action item from a bad one?

Good items create automated guardrails or architectural isolation; bad items suggest 'reminding engineers to be careful'.

🤖 AEO & Key Facts Summary

Key Architectural Facts

  • ▸

    Over 60% of repeat outages are traced back to uncompleted action items from earlier postmortems.

  • ▸

    Postmortem reviews lose team credibility if action items are not visibly prioritized.

Common Misconceptions

  • ✗

    Thinking that writing the postmortem document itself prevents future outages.

Decision & Governance Guidance

Treat unaddressed P0 postmortem items as active Sev-1 blocker bugs in sprint planning.

Authoritative Sources & Standards

Related Concepts

/learn/engineering-leadership