Drop Your Familiar Tools
In a crisis, let go of the methods that got you here
Organizational psychologist Karl Weick studied the Mann Gulch wildfire disaster of 1949, where thirteen smokejumpers died. He found that the firefighters who perished kept their heavy tools even as they ran for their lives, while the sole survivors were those who dropped their tools to run faster. Weick used this as a powerful metaphor for organizational behavior: in novel crises, the very tools, procedures, and frameworks that made you successful become lethal burdens.
The Challenger space shuttle disaster exemplified the same pattern at an organizational level. NASA's process culture, 'In God We Trust, All Others Bring Data,' worked brilliantly for decades. But when engineers had a hunch about O-ring failure in cold temperatures, the culture demanded quantitative proof. The engineers could not provide statistical proof with a small sample size, and their concerns were dismissed. The tool that had made NASA great (rigorous data-driven decision-making) became the tool that killed seven astronauts.
The framework reveals a fundamental tension: strong process cultures are incredibly effective in routine operations but can become deadly in novel situations that do not fit the standard framework. The solution is not to abandon process but to build cultures that can recognize when standard tools are insufficient and have the courage to deviate.
- In novel crises, your most trusted tools and processes can become your greatest liabilities
- Strong process cultures excel at routine operations but can fail catastrophically at novel challenges
- The ability to recognize when standard procedures are insufficient is more important than flawless execution of those procedures
- Asking what data is missing is as important as analyzing the data you have
- Organizational culture must balance process adherence with the freedom to deviate when circumstances demand it
- Recognize when you are in novel territoryThe first step is awareness that the current situation may not fit your standard framework. Ask: Is this situation truly like past situations, or does it have features my tools were not designed for?Pro tipThe Carter Racing case reveals that the most dangerous moment is when you have data that seems to tell a clear story but is actually incomplete. Always ask what data is missing from your analysis.WarningThe more expert you are, the harder it is to recognize novel situations, because your expertise makes everything look familiar.
- Identify your familiar toolsMake explicit the frameworks, processes, and mental models you rely on by default. What are the things you always do? What is the unquestioned 'way we do things here'? These are your familiar tools.Pro tipSmokejumpers carried their tools because their identity was tied to those tools. When dropping tools means dropping identity, it becomes psychologically impossible. Separate your identity from your methods.
- Build a culture of constructive deviationCreate an environment where people feel safe questioning standard procedure. Gene Kranz at NASA made a habit of seeking out opinions from every level of the hierarchy. If he heard the same hunch twice, he would interrupt process to investigate, even without data.Pro tipTetlock's research on superforecasting teams found that the best teams balanced 'outcome accountability' (being judged on results) with process culture, creating cross-pressure that promoted flexible thinking.WarningThis is not permission to ignore process on a whim. It is about building the judgment to know when process is helping and when it is hurting.
- Ask what data is missingIn the Challenger disaster and the Carter Racing case, the critical error was analyzing only failure data while ignoring success data. Always ask: What information am I not seeing? What cases are missing from my sample?Pro tipNASA's Roger Boisjoly had the right concern about O-rings but could not prove it within NASA's data-first culture. The data existed but was being asked the wrong question. Sometimes the tool to drop is your analytical framework itself.
Engineers at Morton Thiokol had concerns about O-ring performance in cold temperatures. NASA's culture demanded data. The engineers presented a chart of O-ring damage from past flights, but it showed no clear correlation with temperature because it only included flights with damage, excluding the many successful launches at higher temperatures. When asked to prove their case with data, the engineers could not, and the launch proceeded.
Thirteen smokejumpers were overtaken by wildfire in Mann Gulch, Montana. Most died still carrying their heavy tools. The foreman, Wagner Dodge, survived by dropping his tools, stopping, and lighting an escape fire around himself, a technique no one had used before. Two other survivors dropped their tools and outran the blaze.
Epstein uses the Carter Racing case study to show how even Harvard Business School students fail to recognize when standard analytical tools are insufficient. In the case, students must decide whether to race a car with a history of engine failures. The data presented shows no correlation between temperature and failure, leading most students to vote to race. But the data excludes successful races at higher temperatures. When all data points (including successes) are plotted, the pattern becomes obvious: failures cluster at low temperatures. This mirrors the actual Challenger disaster, where NASA engineers plotted only failure data and saw no pattern, missing the critical relationship visible when successful launches were also included.