by Brent Voelker
April 23, 2026
In high‑risk, high‑consequence environments, reliability is never the product of optimism. One of the most counterintuitive findings in the study of high‑reliability organizations (HROs) is that their success depends not on confidence, but on a disciplined, almost obsessive attention to the possibility of failure. Weick and Sutcliffe (Managing the Unexpected, 2015) describe this posture as Preoccupation with Failure: a continual alertness to small errors, weak signals, and anomalies that others might dismiss as noise.
At Novellum Partners, we prefer to call this orientation Vigilance for Failure. Preoccupation carries with it a sense of being stuck or distracted, while vigilance suggests that we are on the move, even as we pay close attention to every detail that is going on around us.
Vigilance for failure means that even near misses and minor deviations are treated as important data points, not inconveniences or artifacts of the analysis or test environment. This approach reflects the understanding that major accidents are rarely the result of single catastrophic errors; rather, they emerge through the accumulation of unnoticed small failures over time. A culture that rewards silence around “harmless” mistakes gradually conditions team members to disregard emerging risk until it is too late.
In the US nuclear navy, the incident report – telling on ourselves – after a mishap is a foundational practice that shares knowledge across the entire fleet. Well-trained as they are, the youthful and unwise find it easy to scoff at incident reports from other ships. Of course, wewould never do that. “No,” our engineer officer would remind us, “There – but for the grace of God – go we. There were nine mistakes in this sequence of events. We have made eight of them.”
What distinguishes truly reliable organizations is their ability to amplify weak signals instead of explaining them away or hoping they won’t repeat. Vigilance for failure requires leaders to resist the human tendency toward cognitive comfort – the desire to preserve positive narratives, protect status, or maintain the appearance of control. High‑reliability cultures encourage the timely reporting of bad news, framing detection as a contribution to collective performance rather than a personal liability.
Vigilance for failure is not about fault‑finding; it is about sustaining sensitivity to complexity and surprise. Enacted through a rigorous change management process that never prejudges the importance of any one cue and generates Institutional Knowledge, Vigilance for Failureis the first and most foundational hallmark of a highly reliable organization.
Key to the process is to provide all team members with an accessible means of prompt reporting. As soon as they know something new – even if contrary to their own prior assessments – they should be rewarded for making an immediate report. The more rapid and meaningful the response, the more willing the frontline will become to share information. The process becomes a virtuous cycle that solves problems in real time and provides leadership with complete knowledge and control of their development program.
Ultimately, vigilance for failure is a discipline of humility. It reflects the recognition that complex systems can never be fully understood – especially as new complexities emerge in the design process. High Reliability Organizations remain dependable not because they eliminate error, but because they expect it. They work relentlessly to detect, interpret, and learn from failure.
In an era that celebrates confidence and speed, vigilance for failure offers a crucial counterpoint: Enduring reliability is sustained not by certainty, but by ongoing doubt, careful attention, and a deep respect for the likelihood that, at every turn, something can go wrong.
At Novellum Partners we provide our clients with the tools and processes they need to build and sustain reliable culture through daily practice. We’d love to talk to you about what that means in your organization.