Week 33 Day 2: Why Firefighting Feels Heroic but Is Actually a Failure

Organizations reward firefighting. The person who fixes the production outage at 2 AM gets praised in the all-hands meeting. The person who quietly built the monitoring system that prevents outages gets nothing because nothing happened. The incentive structure teaches people that fires are opportunities for recognition. When fires are rewarded, people stop preventing them.

Here is the hero cycle and why it persists. Phase one: the leader builds or tolerates a fragile system because investing in resilience feels slower than shipping features. Phase two: the fragile system breaks. Crisis mode activates. Phase three: the leader leads the crisis response -- working late, making fast decisions, rallying the team. Phase four: the crisis is resolved. The leader receives praise for their crisis management skills. Phase five: the leader returns to normal operations without fixing the fragile system, because someone else has already created the next urgent priority. Phase six: the system breaks again. Return to phase two. The leader is rewarded at phase four and never penalized for the fragility they created or tolerated at phase one. Over time, the leader develops an identity around crisis management. 'I thrive in chaos' becomes their brand. They unconsciously resist the systems and processes that would eliminate the chaos because chaos is where they feel most competent and most valued. I have been this leader. I was proud of my crisis management skills. I could diagnose a production issue faster than anyone on the team. What I did not realize was that my crisis management skills were a coping mechanism for the fragile systems I had failed to fix. When a new engineering director proposed a systematic reliability investment, I pushed back because it would 'slow us down.' What I actually meant was: it would eliminate the crises where I felt most useful. The fix is to change what you celebrate. Stop praising firefighting. Start praising fire prevention. The engineer who deploys the load shedding mechanism that prevents the outage should get the same recognition as the engineer who fixed the outage at 2 AM. Prevention is invisible work. Leaders have to make it visible.

The hero cycle is documented by Perrow (1999) in 'Normal Accidents,' where he demonstrates that in complex organizations, the celebration of crisis response creates a 'normalized deviance' -- a condition where the organization gradually accepts increasing levels of risk because each near-miss or crisis is resolved 'successfully,' reinforcing the belief that the current level of risk is manageable. Vaughan (1996) documented this pattern in her analysis of the Challenger disaster, showing how NASA's cultural celebration of 'working the problem' (firefighting) displaced investment in systematic risk reduction, ultimately contributing to catastrophic failure. Research by Madsen and Desai (2010) on 'organizational learning from failure' found that organizations that experienced frequent small failures without conducting root cause analysis ('near-miss bias') actually reduced their learning rate over time, because repeated successful crisis resolution created the illusion that the system was resilient when it was actually accumulating risk. The incentive inversion -- rewarding response over prevention -- is an instance of what Kerr (1975) called 'the folly of rewarding A while hoping for B,' one of the most cited papers in organizational behavior. His analysis demonstrates that organizations consistently reward visible, dramatic behaviors (crisis response) while hoping for invisible, systematic behaviors (crisis prevention), producing exactly the pattern they wish to avoid. Research by Weick and Sutcliffe (2007) on 'High Reliability Organizations' (HROs) found that the organizations with the lowest failure rates -- nuclear aircraft carriers, air traffic control centers -- explicitly rewarded detection and prevention of potential failures more than they rewarded response to actual failures.