A book summary of Drift into failure by Sidney Dekker.

"Drift into Failure" is a book by Sidney Dekker that examines the ways in which complex systems can drift into failure, and how these failures can often be traced back to small, seemingly insignificant events or decisions.

The book argues that many large-scale failures, such as plane crashes or nuclear accidents, are not the result of a single catastrophic event, but rather the accumulation of a series of small failures or errors that ultimately lead to disaster. These failures can occur in any complex system, whether it be an airplane, a nuclear power plant, or a hospital.
 
According to Dekker, these failures are often the result of a "drift into failure," where small deviations from normal operation go unnoticed and eventually lead to a catastrophic event. These deviations can be caused by a variety of factors, such as human error, equipment malfunction, or organisational problems.
 
Dekker argues that in order to prevent drift into failure, it is important to focus on the root causes of these small deviations and address them before they become larger problems. He also emphasises the importance of creating a culture of safety within organisations, where employees feel comfortable reporting errors and potential problems without fear of retribution.
 
One example of drift into failure that Dekker discusses in the book is the Exxon Valdez oil spill. On March 24, 1989, the Exxon Valdez oil tanker ran aground on a reef in Alaska, spilling millions of gallons of oil into the ocean. According to Dekker, the disaster was not the result of a single event, but rather the accumulation of a series of small failures and errors.
 
For instance, the captain of the tanker, Joseph Hazelwood, was intoxicated at the time of the accident. However, this was not the root cause of the disaster. Rather, it was the result of a culture within the company that did not prioritise safety and allowed Hazelwood to continue working despite his alcohol abuse. Additionally, there were problems with the ship's navigation equipment and the crew's training, which also contributed to the accident.

New call-to-action

Another example of drift into failure that Dekker discusses is the Space Shuttle Challenger disaster. On January 28, 1986, the Challenger exploded just 73 seconds into its flight, killing all seven crew members on board. Dekker argues that the disaster was not the result of a single event, but rather the accumulation of a series of small failures and errors.
 
For instance, there were concerns raised about the safety of the shuttle's O-ring seals, which were responsible for sealing the joints in the solid rocket boosters. However, these concerns were not adequately addressed, and the decision was made to launch the Challenger despite the potential risks. Additionally, there were problems with communication and decision-making within the organisation, which also contributed to the disaster.
 
In both the Exxon Valdez and Challenger disasters, Dekker argues that the root causes of the accidents can be traced back to a drift into failure, where small deviations from normal operation went unnoticed and eventually led to a catastrophic event.
 
Overall, "Drift into Failure" is a thought-provoking examination of how complex systems can fail by allowing under-reporting and -involvement to happen and how to prevent these failures from occurring. It offers valuable insights into the ways in which organisations can improve safety involvement and prevent disasters.

If you're looking for an incident reporting platform that is hyper-easy to use, ticks all the boxes for anonymity, and two-way communication, has built-in workflows for multiple use cases and more, test drive our incident reporting platform or contact us for more information!

Falcony free trial


We are building the world's first operational involvement platform. Our mission is to make the process of finding, sharing, fixing and learning from issues and observations as easy as thinking about them and as rewarding as being remembered for them.‍

By doing this, we are making work more meaningful for all parties involved.

More information at falcony.io.

Related posts

Who Owns The Failures In Your Organisation?

Many of us dread failure. However, failures are how we learn and that's why reporting them is...

Incident Reporting
3 min read

What's The Value Of Failure?

Reporting failures in many organisations is something people would most often rather avoid. Nobody...

Incident Reporting
3 min read

9 Reasons For Failure (Regardless Of Industry Or Department)

Failures are an inevitable part of running a business, organisation, facility, or any other entity....

Incident Reporting
5 min read

Involve your stakeholders to report

At Falcony, we create solutions that multiply the amount of observations and enable our customers to gain greater understanding of what’s going on in their organisations, areas of responsibility and processes.