Post-mortem Culture 2024
Five years ago, I addressed the dilemma of technological failures as an unavoidable part of innovation, one that can provide excellent data for improving products, services and organizations. At that time, companies such as Google, Amazon, Netflix, Facebook and Microsoft used autopsies to capture and share the lessons from those errors. Now, with the advances in…

Five years ago, I addressed the dilemma of technological failures as an inevitable part of innovation and they can provide excellent data to improve products, services and organizations.
At the time, companies such as Google, Amazon, Netflix, Facebook and Microsoft used autopsies to capture and share the lessons from those errors. Now, with advances in artificial intelligence, autopsies are analyzed through machine learning models that help detect and correct problems immediately.
According to the firm CB Insights, for 2018, 70% of the tech startups that go past 20 months from their first funding round treat their operations as if they were a software problem, to describe and detail how important it is for business units to react to errors. At Tabuga we hold that a company that actively collaborates to build a corporate memory is ready to establish a post-mortem culture.
What is a post-mortem culture?
A post-mortem culture, in the business and technology context, refers to an organizational practice or philosophy centered on detailed analysis and reflection after an error, failure or incident occurs, especially in software projects, IT systems and business operations.
The term «post mortem», which literally means «after death» in Latin, is used metaphorically here to describe a thorough analysis after an event (usually a negative one) has occurred.
Key aspects of a post-mortem culture include:
- Incident analysis: After a failure or error, a detailed analysis is carried out to understand what went wrong, why it happened, and how the situation was handled.
- Focus on learning: The main goal is to learn from mistakes so they don't happen again. The aim is to understand all the underlying causes of the incident, not just the most obvious ones.
- Transparency and communication: Open and honest communication about failures and errors is encouraged. Sharing the details and lessons learned from incidents is vital for organizational learning.
- Avoiding blame: A healthy post-mortem culture avoids blaming specific individuals. Instead, it focuses on the processes and systems that allowed the error to occur.
- Continuous improvement: The learnings from post-mortem analyses are used to continuously improve the organization's processes, practices and systems.
- Documentation and archiving: The findings and lessons learned from each post-mortem analysis are documented so they can be referenced and used in the future.
Relevance for organizations
This culture is especially valuable in environments where innovation and rapid change are common, such as the technology industry, since it helps organizations adapt and evolve more effectively and safely.
When an incident occurs, the goal is to resolve the underlying problem and return services to their normal conditions. If left unchecked, incidents can grow in complexity or even cascade, overwhelming the business's systems and their operators and, ultimately, harming the customer experience.
For example, an error arising in an internal IT system at an organization that lacks a modern data-feed architecture for its mobile applications (based on Application Protocol Interface, API or Microservices) can make those applications appear to be out of service to the user, when the real issue is the optimization of communication between those systems. The Marketing department will complain to the Digital Department, and the latter will say the problem belongs to Technology or DevOps. Meanwhile, the customer loses.
Autopsies matter when incidents occur: they let us carefully clarify, document and share the lessons from any error, and in that way we avoid corporate amnesia and the endless cycle of poor customer experience. This model can be applied to any activity that involves the use of software.
How to approach it?
To start a post-mortem culture, we must document a few scenarios: visible service interruptions, impacts on data integrity, slow customer responses or error detection. These should be displayed on a dashboard or scorecard to keep the whole team attentive to the indicators.
The next step is to create a written record of the incident that covers its impact, how it was resolved, and what will be done to prevent it from happening again.
The lessons that go into the corporate memory should be used to build resilience and preparedness for future problems that may arise along the way.
By speaking openly about failures and working to investigate their causes, everyone has the opportunity to learn from each incident and take part in the next steps. Documenting the process and its results provides a highly valuable resource, durable over time, that team members can turn to whenever necessary.
Looking back, there is still ample room to apply good practices that make digitalization easier in business. In 2018 in the country we were barely learning how agile methodologies could speed up work in multidisciplinary digital project teams.
Today we see that this has evolved into multiple cells or teams within organizations, moving forward in an agile way with projects and modules of the complex, digital machinery that the companies of the future must run on.
Elements such as post-mortem culture are a fundamental step –now more than ever– in strengthening technological evolution efforts in companies. Culture is a pivot point for accelerating staff focused on digital projects.
Onward!