post-mortems-retrospectives

To run a blameless post-mortem, structure the review process from initial incident classification and fact-gathering to diagnosing contributing factors, defining learnings, and creating an action tracker with kill criteria and dissemination plans.

A comprehensive retrospective should include a timeline of events, contributing factors, decisions made, an action tracker with owners and due dates, kill criteria, and a dissemination plan to institutionalize learnings.

A blameless post-mortem prevents future issues by focusing on systemic learning rather than blame, diagnosing root causes and contributing factors to derive actionable decisions and institutionalize learnings through recurring reviews.

Yes, you can facilitate blameless post-mortems for incident management and retrospectives for project or OKR outcomes, transforming either type of result into actionable learnings and structured action plans.

The best way to track actions is to generate a detailed pack with an action tracker that includes specific owners, due dates, kill criteria, and a dissemination plan to ensure accountability and institutional learning.

No specific dependencies are required to facilitate a structured retrospective; the process guides you from initial classification and fact-gathering to defining learnings and creating an action tracker natively.