Many organizations run on urgency. Something breaks. A customer complains. A deadline slips. Leaders jump in to fix the problem. The system is restored, the crisis passes, and everyone moves on to the next issue. It feels productive. It feels responsible. Sometimes it even feels heroic.
But constant firefighting can hide a deeper truth: restoring a system after a problem occurs is not the same as improving it. W. Edwards Deming warned that many organizations stay trapped in cycles of reaction because leaders confuse solving problems with improving the system that creates them.
The trap of solving today’s problems
Leaders are trained to respond quickly when problems appear. A delivery runs late. A customer complains. A system breaks. Responsible managers step in, solve the issue, and get operations back on track. In the moment, this feels like effective leadership.
But Deming argued that reacting to problems is often only temporary relief. When the same kinds of problems appear again and again, the issue is rarely a single mistake or a careless employee. More often, the system itself is producing the outcomes we see.
This is one of the hardest ideas for managers to accept. When an organization is busy and customers need help, stepping back to study the system can feel like the wrong response. Yet without understanding how the system works, leaders may spend years solving the same problems over and over.
A small service company illustrates how this cycle unfolds—and how a different way of thinking can finally break it.
A business that lived in constant emergencies
Carlos owned a growing neighborhood HVAC service company. Business was strong. Phones rang throughout the day. Trucks were constantly on the road.
From the outside, the company looked successful. Inside the office, however, each afternoon felt chaotic.
Technicians called needing parts. Customers demanded urgent visits. Jobs ran longer than expected and the carefully planned schedule began to unravel. Dispatchers scrambled to rearrange appointments while Carlos jumped in to solve problems as quickly as they appeared.
“Move that install to tomorrow,” he told the dispatcher one afternoon. “Send Mike over to Mrs. Jenkins. I’ll call the supplier and see if we can rush that part.”
The day would stabilize. Customers were helped. Emergencies were handled. But the next day looked almost exactly the same. By midweek the technicians were exhausted, dispatchers were frustrated, and Carlos felt like he spent every day racing from one crisis to the next.
Eventually he began to notice something important. The emergencies were not random. They followed patterns.
Jobs were scheduled too tightly. Some technicians were handling complex repairs before they had enough experience. Parts needed for common repairs were not always available when technicians arrived at a job. None of these problems were unusual events. They were built into the way the system operated.
Deming described this distinction clearly in Out of the Crisis: “Putting out fires is not improvement of the process. This only puts the process back to where it should have been in the first place.”
Putting out fires is not improvement of the process. This only puts the process back to where it should have been in the first place.
— W. Edwards Deming
Carlos slowly realized something uncomfortable. His daily heroics were not improving the business. They were simply restoring the system to where it had been before the latest disruption.
At the next team meeting he made an unexpected announcement.
“We’re not fixing today’s schedule,” he told the group. “We’re studying how our schedule works.”
The team began mapping a typical service day. They looked at travel times between neighborhoods. They tracked which types of jobs commonly ran long. They identified repairs that frequently required parts technicians did not carry.
Gradually they began changing the system. Service appointments were spaced differently. New technicians received more structured training. Trucks were stocked with the parts most commonly needed for repairs.
And over time something surprising happened. The emergencies began to fade. Carlos realized that his technicians had never been the problem.
As Deming often reminded leaders: “A bad system will beat a good person every time.”
A bad system will beat a good person every time.
— W. Edwards Deming
Once the system improved, the daily firefighting that once dominated the company began to disappear.
Why leaders keep fighting the same fires
Most managers recognize the exhaustion that comes from constant firefighting. Yet many organizations remain trapped in that pattern for years.
Part of the reason is psychological. Solving problems feels productive. When a leader steps in and rescues a situation, the result is immediate and visible. Customers are satisfied. The crisis ends. The day is saved.
System improvement is different. It requires stepping back. Studying patterns. Slowing down long enough to understand how the work actually functions. In organizations that value speed and responsiveness, this can feel uncomfortable.
We also tend to interpret problems as individual failures. A technician made a mistake. A dispatcher scheduled something incorrectly. A customer service representative handled a call poorly.
But when the same types of issues appear repeatedly, a more useful question emerges: What in the system allowed this to happen?
Without this shift in thinking, managers spend enormous energy reacting to symptoms while the underlying system remains unchanged. And the result is predictable. Tomorrow, the same fires return.
What leaders can do instead
Distinguish between restoring and improving. Solving a problem often restores the system to where it was before the disruption. Improvement means changing the system so the problem is less likely to occur again.
Look for patterns before reacting. When similar issues appear repeatedly, assume the system may be producing them. Studying patterns reveals far more than reacting to isolated events.
Examine how the work is designed. Scheduling rules, training, handoffs, information flow, and resource availability often shape outcomes more than individual effort.
Stop rewarding firefighting. Organizations often celebrate the people who rescue crises. A healthier culture recognizes leaders who prevent those crises by improving the system.
Shift leadership attention upstream. Instead of focusing only on today’s problems, ask how the system itself might be redesigned to produce better results tomorrow.
Improvement begins when firefighting ends
Every organization encounters problems. That will never disappear.
But leaders shape how their organizations respond. Some spend their days racing from crisis to crisis—restoring the system after each disruption. Others step back and study how the system itself produces those disruptions.
Deming believed the difference between these two approaches defines the difference between activity and improvement.
Thoughtful leaders focus not only on solving today’s problems, but on building systems that produce better outcomes tomorrow.
