How to Stop Firefighting in Your Business

Learning how to stop firefighting in business starts with an uncomfortable idea: most fires are not accidents. If the same kind of problem lands on your desk every week—a late delivery, a cash crunch, an angry customer, a stock-out—then something in the way the business is set up keeps producing it. Putting fires out faster does not help. Finding where they start does.

Why firefighting feels productive

A day of crises feels like hard work, and it is. Owners and managers who are good at rescues get rewarded for them, by grateful customers and by their own sense of being needed. The cost stays hidden. Planned work slips, the same few people get pulled in every time, and nobody has an hour to ask why the problem happened in the first place. Over months, the team starts to treat firefighting as the job itself.

Keep a fire log for two weeks

You cannot diagnose what you have not recorded, and memory is a poor record when everything feels urgent. For two weeks, ask everyone in a lead role to note each urgent problem in one shared sheet. Keep the columns simple:

• Date, and what happened in one sentence.
• Who noticed it, and how: a customer, a supplier, a report, or by chance.
• Who had to step in to fix it, and roughly how long it took.
• Whether it has happened before.

Make it clear that the log is about the system, not about blame, or people will quietly leave things out. At the end of the two weeks, group similar entries together. Usually a small number of patterns account for most of the noise, and the second column tells you how many problems you only hear about from customers.

Trace each pattern to its root cause

For each pattern, keep asking why until you reach something you can change in the system rather than a person to blame. A delivery went out late. Why? The stock was not there. Why? Nobody reordered in time. Why? There is no reorder level; the storekeeper reorders when the shelf looks low. The fix is a threshold and a trigger, not a warning to the storekeeper.

In our experience the root causes tend to fall into a few families:

• No owner: the task sits between two people or two teams, and each assumes the other has it.
• No rule: a decision is made fresh every time because the limit or standard was never written down.
• Late information: the problem exists for days before anyone can see it.
• Broken handover: work changes hands without the details travelling with it.
• Slow approvals: work waits in a queue for one person, then gets rushed through.
• Real capacity: the team is genuinely too small for the volume, which is less common than it feels.

Fix the system, not the symptom

Each family has a matching kind of fix. No owner needs a named owner. No rule needs a written limit. Late information needs a report or alert that shows the problem early. A broken handover needs a checklist at the point of transfer. Slow approvals need delegated limits or a faster approval flow. Only the last family, capacity, is solved by hiring, so rule out the others before you add headcount.

One event management client of ours had a field team of 85 people travelling across the country. Their recurring fires were about money: advances that stayed unsettled for weeks, lost bills, and a single operations person buried in follow-ups and manual reconciliations. The cause was not careless staff. It was a control system built on spreadsheets and paper. We replaced cash advances with UPI-enabled wallets, had bills uploaded at the moment of spending, and set up same-day approvals. Their expense-to-sales ratio fell from 14% to 8.5%. That is one client's result, but the pattern is common: what looked like a people problem was a design problem.

Once a fix works, write it down so it survives staff changes. A short procedure turns a one-off repair into the way the work is done.

Read our guide to creating SOPs for a small business →

Protect time for the fixes

The trap is that firefighting leaves no time to fix its causes. Break the cycle on purpose. Block two hours a week, at the same time each week, for one person to work on the top pattern from the fire log and nothing else. Fix one pattern at a time and keep the log running, so you can see whether that kind of problem actually drops. When it does, move to the next. For this week:

• Set up the shared fire log and explain to your leads why you want it.
• Ask each lead to add entries every day, without blame.
• Book a one-hour review for the end of week two.
• In that review, choose one pattern and agree the fix and its owner before anyone leaves the room.

Sometimes the fire log points somewhere uncomfortable, or the causes cut across finance, operations and people at the same time. That is where an outside view helps. Our business diagnostic gives you a clear look at where the business stands and what to fix first, based on how it actually runs rather than a generic checklist. Where it makes sense, we then stay to help put the fixes in place.

See our business diagnostic and health check →