What We Do When We Get Something Wrong

Origin and history

The cultural and philosophical concept of "What We Do When We Get Something Wrong" does not originate from a single country or region. Its formal examination is deeply rooted in global philosophical traditions, with significant contributions from Western academic discourse on ethics and error in the late 20th century. The terminology itself gained broader cultural traction in the early 21st century, particularly within organizational psychology and technology sectors focused on failure analysis. It synthesizes ancient ideas of repentance and learning from mistakes with modern frameworks for systemic improvement. The concept's documentation and standardization as a topic for study became more prevalent with the rise of literature on high-reliability organizations and just culture. Its evolution reflects a shift from viewing error as purely individual culpability to understanding it as a complex interplay of systems, processes, and human factors.

What it is for

This framework exists to provide a structured approach for individuals, teams, and organizations to respond constructively to errors, failures, and unintended outcomes. Its primary purpose is to transform negative events into opportunities for learning and systemic enhancement, rather than allowing them to fester as sources of blame or shame. It serves to establish clear protocols that separate the analysis of the event from the punitive judgment of the person, where possible. The practice is for building psychological safety, ensuring that people feel able to report mistakes without fear of disproportionate retribution. It aims to interrupt the instinctive cycle of cover-up and denial that often follows an error, replacing it with transparency and corrective action. Ultimately, it is for preventing the repetition of the same or similar mistakes by embedding the learned lessons into revised procedures, designs, or training.

Overview

"What We Do When We Get Something Wrong" is a procedural and ethical framework governing the post-error response cycle. It encompasses the immediate actions taken to mitigate harm, the investigation process to understand root causes, the communication strategy to relevant parties, and the implementation of changes to prevent recurrence. The overview includes recognizing the error openly, which is the critical first step that many systems fail to achieve due to cultural barriers. It then involves a methodical analysis, often using tools like the "Five Whys" or fishbone diagrams, to move beyond superficial cause to underlying systemic factors. The framework also covers the act of apology or amends, where appropriate, which is a formal component aimed at restoring trust and acknowledging impact. Finally, it closes the loop by documenting and sharing the findings and the new safeguards established, making the knowledge gained from the error a permanent organizational asset.

What to know

It is crucial to know that this framework is not a single policy but a cultural norm that must be consistently modeled by leadership to be effective. One should know that the most challenging phase is often the initial acknowledgment, as it requires overcoming powerful cultural and personal incentives to minimize or hide the error. Readers should understand that a key component is distinguishing between reckless negligence, which may warrant sanction, and unintended error within a complex system, which warrants analysis. It is important to know that the process is resource-intensive, requiring dedicated time and a blame-free environment for investigation to uncover true root causes. One must know that successful implementation directly correlates with higher reporting rates for near-misses, which are invaluable for proactive risk management. Finally, it is essential to know that the framework fails if it becomes a performative ritual where investigations are superficial and lessons are filed away without changing actual practice.

Common questions

A common question is how to balance accountability with a no-blame approach, which is addressed by holding individuals accountable for following known procedures while analyzing why a procedure failed or was absent. People often ask who should be involved in the analysis, with the best practice being a multidisciplinary team that includes those closest to the event and those with system-wide perspective. Many inquire about the necessity of a formal apology, which is guided by the principle that a sincere apology for the outcome does not always equate to an admission of gross misconduct. A frequent question concerns what happens if an error is caused by a single person's clear violation, which shifts the focus to why the system allowed that violation to occur and cause harm. Readers commonly question how to measure the success of such a framework, typically through metrics like reduced recurrence of similar events, increased incident reporting, and employee surveys on psychological safety. Organizations often ask how to start implementing it, which begins with analyzing past responses to failure and publicly committing to a more structured, learning-oriented protocol.

Pros and cons

A significant pro is the demonstrable improvement in safety, quality, and reliability over time, as organizations stop repeating the same errors and proactively address vulnerabilities revealed by incidents. It builds immense institutional trust and credibility, both internally with employees and externally with clients or the public, by demonstrating integrity and a commitment to improvement. A major con is that the initial implementation can be slow and met with deep skepticism, especially in cultures with a long history of punitive responses, requiring sustained leadership commitment to overcome. The framework can be exploited if bad actors perceive the protective analysis as a shield for genuine misconduct, necessitating clear and consistent boundaries between error and violation. A common mistake is conducting a root cause analysis that stops at "human error," which is a conclusion that prevents any meaningful systemic change and renders the entire process futile. Some organizations regret adopting it superficially, as the effort required is substantial and a half-hearted attempt can cynically erode trust more than having no framework at all.

Who it suits

This framework suits organizations in high-risk sectors like healthcare, aviation, and nuclear power, where learning from failure is literally a matter of life and death and is already embedded in their operational doctrine. It suits technology companies and software development teams that operate in complex, fast-moving environments where errors are inevitable and rapid iteration based on failure is a core competitive advantage. It is well-suited for leadership teams that possess the humility to acknowledge their own fallibility and the patience to invest in long-term cultural change over short-term scapegoating. The approach suits educational institutions and training programs aiming to instill a growth mindset, where error is reframed as a fundamental part of the learning process rather than a mark of incapacity. It does not suit organizations seeking a quick public relations fix after a crisis, as the required depth of change is incompatible with a purely cosmetic application. It is ideally suited for any group or individual who views perfection as an unattainable standard and continuous improvement through managed fallibility as a more realistic and robust goal.