← Workflows

阅读中文版本

Incident Postmortem Blameless Workflow

Conduct a blameless postmortem after an incident to identify root causes, action items, and systemic improvements.

advanced~90 minpostmortemblamelessworkflow

Objective

Run a blameless postmortem to learn from incidents and prevent recurrence.

Environment

  • A recently resolved incident with timeline and impact
  • Participants from all involved teams
  • A postmortem template

Steps

1. Gather timeline

Collect the incident timeline: detection, response, mitigation, and resolution.

Expected state: A complete incident timeline is assembled.

2. Identify root causes

Analyze the timeline to identify contributing factors and root causes without blame.

Expected state: Root causes are identified and documented.

3. Generate action items

Create specific, owned, and dated action items to prevent recurrence.

Expected state: Action items are assigned with owners and due dates.

4. Review with team

Present the postmortem to the team for feedback and additional insights.

Expected state: The postmortem is reviewed and refined with the team.

5. Track to completion

Add action items to the tracking system and monitor progress to completion.

Expected state: All action items are tracked until resolved.

Decision points

Public or internal postmortem?

  • Public for transparency
  • Internal for privacy

Share internally by default; publish publicly for major incidents to build trust.

Expected outcome

A blameless postmortem is completed with root causes, action items, and a tracking plan.

Verification

Verify all action items have owners and due dates; confirm the postmortem is shared with the team.

Cleanup

No cleanup needed; postmortems should be archived for future reference.

Blameless culture finds systemic issues

When people feel safe reporting mistakes, the organization can fix the system instead of the people.

Implementation Notes

This workflow provides a structured approach to ensure consistent results across team members and environments.

Common Pitfalls

Skipping verification steps or rushing through the process can lead to incomplete results. Always follow each step in order and verify before proceeding.

Quick Reference

# Execute the workflow steps as documented above
echo "Workflow completed successfully"