Post-Mortem
A structured analysis conducted after a project or event to evaluate what happened and extract lessons for future improvement.
Also known as: Post-mortem review, After-action review, Retrospective analysis
Category: Decision Science
Tags: decision-making, learning, improvement, project-management
Explanation
A post-mortem is a retrospective examination conducted after a project, event, or incident has concluded. Its purpose is to understand what went well, what went wrong, and what can be improved for future endeavors. The term originates from medical practice, where it refers to examining a body after death to determine the cause, and has been widely adopted in business, technology, and project management.
The structure of a post-mortem typically includes establishing a timeline of events, identifying contributing factors that led to outcomes (both positive and negative), documenting key findings, and defining concrete action items for improvement. Effective post-mortems go beyond surface-level observations to uncover root causes, asking "why" repeatedly until fundamental issues are identified.
One of the most important advances in post-mortem practice is the concept of the blameless post-mortem, pioneered by organizations like Google and Etsy. In a blameless post-mortem, the focus is on systemic factors and processes rather than individual mistakes. This approach recognizes that errors are usually symptoms of deeper organizational or procedural issues, and that blaming individuals discourages honest reporting and learning.
Creating psychological safety is essential for honest assessment during post-mortems. When team members fear punishment or judgment, they withhold critical information, rendering the exercise superficial. Leaders must actively encourage candor, model vulnerability, and demonstrate that the goal is learning rather than assigning blame.
Post-mortems differ from retrospectives in scope and timing. While retrospectives are typically shorter, recurring reviews conducted at regular intervals (such as sprint retrospectives in Agile), post-mortems are more comprehensive analyses triggered by specific events, usually project completions or significant incidents. Both serve the broader goal of continuous improvement, but post-mortems tend to be deeper and more formal.
To maximize value from post-mortems, organizations should document findings in an accessible format, track action items to completion, and periodically review past post-mortems to identify recurring patterns across projects.
Related Concepts
← Back to all concepts