How to Stop Firefighting in Your Business (The Permanent Fix, Not the Patch)

The most reliable predictor of tomorrow's crisis is today's workaround.

Think about the last fire you dealt with in your business. Trace it back. Somewhere upstream, someone hit an obstacle — a gap in the process, a decision they couldn't make without you, a handoff where something got dropped. They improvised. The improvised solution worked well enough, and then it quietly became the unofficial way of doing things. Until it didn't. And then your phone rang.

That's not bad luck. That's a structural pattern, and it has a name: the firefighting trap. MIT Sloan defines it as "a self-perpetuating cycle in which managers spend their time solving immediate crises, hindering the company's ability to grow, thrive, and compete." The mechanism is always the same — static processes fail to keep up with a changing business, motivated people fill in the gaps informally, those informal fixes accumulate, and eventually the whole structure collapses into a crisis that demands your personal attention.

The reason most small business owners can't fully escape firefighting mode isn't a lack of effort. It's that fighting fires takes exactly the time and attention that fixing the underlying process would require. Every hour spent in crisis mode is an hour not spent on the process gap that caused it. The cycle feeds itself.

This post is about breaking it — not with a mindset shift, but with three specific structural changes that address where fires actually come from.

Why Fighting Fires Makes the Next One More Likely

There's a counterintuitive dynamic at work in most small businesses. The people who fight the most fires get the most recognition. They're the ones who saved the account, resolved the client complaint, got the job back on track. The appreciation is real and well-deserved. But it creates a structural problem.

When MIT Sloan's Nelson Repenning and Donald Kieffer studied this pattern across organisations, they found a concept they called the firefighting arsonist: a person — usually the most capable and committed one in the room — who handles the immediate crisis so effectively that the underlying cause never gets addressed. The fire is extinguished. The kindling stays in place. A week or two later, a variation of the same fire breaks out somewhere else.

This isn't a failure of character. It's what happens when there's no time, no structure, and no expectation for anyone to fix root causes. The system rewards crisis response and quietly starves prevention.

I saw this play out in a user support team I worked with. Ticket volume spiked during a period of turnover — several new people had joined at once, the knowledge transfer was poorly set up, workflows were undocumented, and a single experienced employee was responsible for training a distributed team. Response times that had been measured in hours stretched to days. The team lead's response was to absorb the load personally: processing requests alongside the team, growing increasingly frustrated as the queue didn't shrink, and eventually ignoring escalating complaints while trying to keep the immediate work moving. The situation required a crisis team to step in. What they found — and fixed — wasn't a staffing problem. It was a knowledge transfer gap that had always been there, made visible by the first real pressure.

The scale of this pattern is well-documented, and the direction it runs is worth stating plainly. In Repenning and Kieffer's research across organisations, they found that the tendency to overload — to reward people who deliver under duress while starving time for prevention — "represents perhaps the largest gap between research and practice in the world of management." Leaders consistently reach for the same wrong answer when overloaded: more people, more hours, more budget. That answer always frames the problem as a capacity shortage. But as their Behavioral Scientist research shows, overload is only partly a capacity problem. The bigger damage is what it does to how people manage their work — the constant task-switching, the improvised workarounds, the perpetual reprioritisation. One study they cite found that people spend close to 10% of their working week just switching between apps. That's before a single fire has started.

What this creates is a specific kind of trap: the time you'd need to build a better system is occupied by symptoms of not having one. There's no path out of firefighting mode through firefighting. The only exit is structural, and it starts with understanding what's actually causing the fires.

Where Your Fires Are Actually Coming From

Ask a typical small business owner what causes fires in their business and you'll get answers like "staff who don't communicate," "clients who change their minds," or "supplier problems." These are the presenting crises. They're rarely the root causes.

The root cause, in most cases, is one of two things: a decision that couldn't be made (Waiting waste) or a task that wasn't done correctly the first time (Defects waste). Both sit within the TIMWOODS framework. Understanding which one you're dealing with changes what you do about it.

Waiting waste is operational waste created when work stalls because someone needs a decision, an approval, or a piece of information — and the person who has it is unavailable. The fire doesn't start at the moment of the stall. It starts when the stall becomes visible to the client, the deadline, or the supply chain. By then you're dealing with an emergency that was actually triggered two or three days earlier, when a member of your team couldn't authorise a routine purchase and had to wait for you.

The mechanism behind this is described precisely in MIT Sloan research on how knowledge work flows. Most small businesses run on what the researchers call a "push" system: each person works as quickly as they can and pushes completed work to the next person, regardless of whether that person is ready to receive it. Work piles accumulate at every handoff point. When those piles grow large enough, finding a specific piece of work can take days rather than minutes — and the congestion itself becomes the fire. The emergency wasn't created by the triggering event. It was created by the accumulated backlog of waiting work that had no system to manage it.

Defects waste is operational waste created when something has to be done twice because it wasn't done correctly the first time. The rework fire. The quote that went out without checking current supplier pricing. The job that started without confirming the scope. The installation completed to a standard the client didn't expect. These fires are particularly costly because they require fixing the original problem, managing the client relationship, and absorbing the time and material cost of the rework — often simultaneously.

The cause of Defects waste is almost never incompetence. It's ambiguity. When there's no written standard for what "right" looks like, people apply their own judgement. This is especially true in knowledge work, where as Repenning and Kieffer write in Fortune, work is "shaped by thousands of micro adjustments" — the informal tweaks, local workarounds, and improvised fixes that each person builds into their own approach over time. When those micro adjustments go undocumented, there's no reference to return to. Every new person, every pressured moment, and every job that doesn't fit the usual pattern produces a different version of the output. If five people on your team have five different ideas of what a completed job handoff looks like, you'll get five different quality levels — and the one that causes a fire will be the one you hear about from the client.

These two waste types account for the structural source of most fires in most small businesses. That framing matters because it shifts the question from "why does this keep happening to me?" to "what specific condition am I leaving in place that makes this possible?"

The Reason Quick Fixes Stay Quick

When firefighting becomes a pattern rather than an exception, most business owners reach for one of three responses: hire someone to absorb the load, buy a new piece of software to track things better, or personally take on more hours to stay ahead of the chaos.

These aren't wrong as actions. They're wrong as substitutes for addressing the underlying design.

Repenning and Kieffer addressed this directly in their Behavioral Scientist piece on overloaded organisations: "until you fix the design, adding additional resources will be largely ineffective. Adding more people without first fixing the design usually makes small problems into major ones. An already ineffective and chaotic system then becomes even bigger and more inefficient."

The GM and Toyota case from the 1980s makes this visible at a scale that's hard to argue with. When Toyota's production system began outperforming General Motors in both quality and cost, GM's response was to invest billions in factory automation — robots that would match or exceed Toyota's output. As Repenning and Kieffer describe in their Fortune case study, the results were dismal: "robots sometimes painted each other instead of cars or welded doors shut." Toyota, by contrast, spent comparatively little on automation and a great deal on understanding and redesigning how work actually got done. The technology came later, layered onto a process that was already working. GM's technology was layered onto a process that wasn't.

The same logic plays out in small businesses every week. If approval decisions are unclear, a new project management platform doesn't clarify them — it gives you a system for tracking which approvals are backed up. If jobs regularly start with missing information, bringing in a new hire doesn't fix it — it gives you someone else who will encounter the same gaps on their first day.

Software and headcount are legitimate tools. They work poorly when applied ahead of the process fix. What you get is a faster, more expensive version of the same problem. The investment goes into moving the chaos around rather than reducing it.

The distinction worth holding onto is the one between a patch and a structural fix. A patch handles the current fire. A structural fix removes the condition that allows fires to start. Most small businesses are operating on accumulated patches — quick fixes layered on top of each other over years, each one solving the immediate problem while leaving the underlying condition intact. The kindling doesn't go anywhere.

Three Changes That Stop Fires Before They Start

There's no single move that eliminates all operational fires. But the majority of them — particularly the ones that recur — can be removed with three targeted structural changes. One addresses Waiting waste at its source. One addresses Defects waste at its source. And one addresses the transition points where both types of operational waste most often appear.

1. Draw the Decision Line

Waiting waste exists because decisions your team could make are instead queued up for you. The fix isn't to broadly delegate more — it's to write down, specifically, where the line sits.

Start by listing the ten decisions most frequently escalated to you. For most small business owners, the pattern is recognisable: purchases under a certain amount, scheduling changes within an active job, how to handle a client question during delivery, substituting a supplier part when the specified one isn't available. For each item, write the rule. Under what circumstances can the team make this call without you? What's the threshold?

This isn't primarily about trust. It's about replacing an unwritten rule with a written one. When your team escalates decisions to you, they're usually following the implicit rule that's been established by never making an explicit one. Put the line in writing and it stops being a judgement call — it becomes a reference.

A practical note: if you're thinking "every situation is different," that's accurate for roughly 20% of the decisions that come to you. The other 80% follow a pattern, even if it doesn't feel that way. Write the rule for the 80% and let your team handle those. The 20% that genuinely require your judgement will be easier to give real attention to when they're not buried under the rest.

If you're finding that your team escalates everything to you even when they technically shouldn't, that's a slightly deeper structural issue — one that goes beyond decision rules. The post on whether you're the bottleneck in your own business covers why that pattern forms and how to address it.

2. Write Down What "Right" Looks Like

Defects waste — the fires that come from rework — almost always trace back to the same gap: people are applying their own judgement because there's no written standard to reference. The fix isn't a training programme. It's a reference document.

Pick the five to eight tasks in your business that produce the most rework or complaints. For each one, write down what a correct output looks like. Not a manual — a single paragraph. "A completed quote includes: supplier pricing confirmed against current rates, margin calculated at the agreed minimum, labour and materials listed separately, sent to the client within 24 hours of the site visit." That's the standard. When someone follows it, the output is right. When they don't, the deviation is visible.

A small electrical firm I worked with had persistent callbacks after project completions — the team's working explanation was "difficult clients." When they mapped what "completed" meant across the team, they found four different interpretations. Some engineers included a written handover summary; others moved on as soon as the physical work was done. The fix wasn't more training — it was a single paragraph stating what every completed job included before the client was asked to sign. The callbacks dropped, not because the team got better at their craft, but because "done" finally meant the same thing to everyone.

Michael Gerber's franchise prototype concept captures why this matters: if you had to have a different person do this task in each of 5,000 locations, what would need to be true for all of them to produce the same result? The answer to that question is your standard. You don't need 5,000 locations to benefit from the thinking. You just need to stop relying on institutional memory and individual habit to maintain consistency.

A useful test: if a new person joined your team tomorrow and had to do this task on their first day, what would they need to know to do it correctly? Write that down. That's the standard. It doesn't need to be long. It needs to be clear enough that there's only one reasonable interpretation.

3. Check Before the Handoff, Not After

The most fire-prone moments in any business are the transition points — when work moves from one person to another, from one phase to another, or from your team to the client. These are the moments where information gets dropped, assumptions get made, and the conditions for a future fire get set in place.

For the three transitions in your business where things most frequently go wrong, build a pre-flight checklist. Not an audit — five to seven questions that catch the most common failure points before work moves forward. In a trades business: "Do we have confirmed site access? Is all material on-site? Does the client know the expected arrival time?" In a service business: "Is the brief signed off? Do we have all assets to start work? Has the delivery format been confirmed in writing?"

The checklist moves the catch point earlier. Instead of discovering the missing information when a job is already underway — or worse, at the point of delivery — you catch it at the moment you have the most leverage to fix it at the lowest cost. That shift, from discovering problems after the fact to preventing them at the handoff, is the mechanical definition of moving from reactive to proactive.

This is the least glamorous of the three changes. It's also consistently the one that delivers the fastest visible reduction in operational fires.

The Business That Doesn't Need to Be Rescued

When these three changes are in place, something shifts that's hard to anticipate in advance: the business becomes quieter. Not simpler, exactly — but more predictable. The fires don't disappear entirely. But the recurring ones, the ones you've dealt with in some variation a dozen times, stop happening. The energy that was going into crisis management becomes available for something else.

The goal isn't a perfect operation. It's a business where the structural conditions for preventable fires — unclear decision authority, inconsistent output standards, unchecked handoffs — have been deliberately removed. Where problems that do arise are genuinely new ones, not the same old ones wearing a slightly different face.

One practical starting point: look at the last two weeks of operational fires. For each one, ask a single question — was this Waiting waste or Defects waste? Was it triggered by a decision that stalled, or by a task that wasn't done correctly the first time? The answer will tell you which of the three fixes to build first.

If firefighting is one piece of a larger pattern — the sense of always being busy without getting ahead — the post on why your small business is always busy but not getting ahead maps that wider picture. Firefighting is usually the most visible symptom. It's rarely the only one.

Ready to See This in Your Own Business?

The TIMWOODS categories described in this article are the exact framework HiddenDrain uses to analyse your specific responses. Answer a few questions — usually six to eight — and get a personalised waste report, free, in under 10 minutes. No signup required.

→ Get My Free Report