One thing I have noticed in large organizations is how easy it is to confuse motion with progress. When a team is behind, something important breaks, a launch is at risk, or a customer issue escalates, the organization often knows exactly how to respond: meetings appear, leaders get involved, people work late, and decisions that normally take weeks suddenly happen in hours. From the outside, that can look like the organization operating at its best, but I think it is usually a sign that the system has learned how to survive urgent problems better than it has learned how to prevent them.
Firefighting feels productive because the problem is visible and the response is immediate. There is a clear before and after. Something was broken, people jumped in, and now it is less broken. That kind of work is easy to recognize and easy to reward because everyone can see the effort. The harder thing to see is the work that would have prevented the emergency from happening in the first place.
That is the part of Repenning and Sterman’s paper that really resonates with me. Their argument is not simply that organizations should work smarter instead of harder. Most people already agree with that in theory. The more interesting point is that the structure of the organization often pushes people in the opposite direction, even when everyone involved is trying to do the right thing. When performance falls short, the fastest response is to apply more pressure, ask for more updates, push people to work longer, and take shortcuts that free up time right now. Those choices can help in the moment, but they also take time away from the slower work of improving the system.
Over time, that tradeoff becomes cultural. Teams learn that the way to survive is to keep the machine running, even if the machine itself is getting harder to operate. Documentation gets skipped because the delivery date is close. Preventive maintenance gets deferred because the outage has not happened yet. Root-cause analysis gets postponed because there is another urgent issue waiting. None of those decisions seem unreasonable in isolation, but together they create an organization that is always busy and never quite getting healthier.
The paper calls this the capability trap, and I think it is one of the better descriptions of how enterprise dysfunction actually develops. It is rarely because people are lazy or careless. It is usually because the system rewards the visible rescue more than the invisible prevention. The person who saves the launch is celebrated, while the person who quietly made future launches less fragile may never be noticed at all. That creates a strange incentive structure where the organization says it wants stability, quality, and long-term thinking, but often gives the most attention to the moments when those things have already failed.
The benefit of fixing underlying systemic problems is that the improvement compounds. When a team reduces rework, improves a brittle process, automates a manual step, clarifies ownership, or makes a system easier to understand, the gain is not limited to a single incident. It changes the future shape of the work. The next release is a little easier. The next incident is less likely. The next person who joins the team can understand the system faster. The organization slowly creates more room to keep improving instead of spending all of its energy recovering from the same kinds of problems.
That kind of work can feel unsatisfying at first because it does not always produce an immediate win. In fact, it can make things feel slower for a while. Taking time to fix the process means less time spent pushing today’s work through the system. But that short-term discomfort is often the price of escaping the cycle. If the organization never creates space for improvement, then the only available strategy is to keep asking people to absorb more complexity through effort, and eventually effort becomes the operating model.
I think the cultural lesson is that leaders have to be very careful about what they celebrate. There will always be emergencies, and there will always be moments when people need to rally. The problem is not that firefighting exists. The problem is when firefighting becomes the primary way the organization proves value. A healthier culture still appreciates the people who step up in difficult moments, but it is just as intentional about recognizing the people who make those moments less common.
That shift matters because it changes the story an organization tells about performance. Instead of assuming that every gap is a motivation problem, it asks what the system is making hard. Instead of responding to every miss with more pressure, it asks what capability is missing. Instead of treating process improvement as extra work that happens after everything else is done, it treats improvement as part of the work itself.
That is the part I keep coming back to. Enterprise culture is not only shaped by values, slogans, or operating principles. It is shaped by the daily choices leaders make about whether to spend all available energy getting through the current problem or whether to reserve enough capacity to make the next problem less likely. The organizations that get better over time are usually the ones that learn how to protect that second kind of work, even when the first kind feels more urgent.