You stop firefighting in your business by doing two things at the same time.

First, deal with today's genuine emergencies.

Second, change whatever allowed those emergencies to keep reaching you in the first place.

Most businesses only do the first.

A customer complains. You fix it.

A job is going late. You intervene.

Someone doesn't turn up. You reshuffle the team.

A supplier lets you down. You find another.

An employee needs a decision. You make it.

Cash looks tight. You chase invoices.

Problem solved.

Until something very similar happens next week.

That is the trap.

You become extremely good at saving the business from problems the business never learns how to prevent.

And because you are good at fixing them, everybody keeps bringing them to you.

Eventually firefighting stops being something that occasionally happens inside the business.

It becomes how the business operates.

If that describes your working week, the answer is not becoming a better firefighter.

Your business needs fewer fires.

What does firefighting actually mean in business?

I would define business firefighting as repeated, urgent and largely unplanned intervention required to keep normal operations moving.

The important word is repeated.

Every company has genuine surprises.

A key piece of equipment fails unexpectedly.

A major customer changes something at the last minute.

A supplier suddenly collapses.

Someone important becomes seriously ill.

That is business.

I would not redesign the entire organisation because something genuinely unusual happened once.

Firefighting becomes a structural problem when the same categories of issue keep appearing.

Delivery problem.

Staffing problem.

Customer complaint.

Quote needs approval.

Production delay.

Cash panic.

Supplier issue.

Quality issue.

Employee dispute.

And somehow the answer is repeatedly:

"Get the owner."

That is not an emergency response system.

It is an operating model.

Being busy and firefighting are not the same thing

A business can be extremely busy and still be well controlled.

People know their responsibilities.

Managers make decisions.

Problems have owners.

Performance is visible.

The company can handle a heavy workload without everything becoming urgent.

Firefighting is different.

Priorities keep changing because the next problem determines the day.

Planned work gets pushed aside.

Senior people are continually dragged down into operational detail.

Improvement work rarely happens because all available capacity is spent restoring normal service.

The Office for National Statistics found that 36% of UK firms with 10 or more employees said having too little time to think about or implement changes was their biggest barrier to improving management practices.

That is almost a perfect description of the firefighting loop.

The problem consumes the capacity required to fix the system creating the problem.

The Firefighting Loop

This is one version of what I call the Fixer Loop.

Something goes wrong.

The team is uncertain.

The issue reaches the most capable person.

Usually the owner.

The owner fixes it quickly.

Immediate pressure disappears.

Everyone gets back to work.

Because the immediate pressure disappeared, nobody spends enough time investigating why the problem happened.

Then it happens again.

The team already knows the fastest solution.

Ask the owner.

So the next escalation happens even faster.

The owner becomes better at firefighting.

The business becomes worse at operating without them.

That is why being capable can become a trap.

Your competence starts compensating for weaknesses the organisation should have been forced to fix.

The first rule: separate the fire from the cause

Imagine an important order has not shipped.

The immediate problem is obvious.

Get the order out.

You may need to intervene.

But that is only the containment action.

You still need a second question:

Why was the order able to reach this point without anybody seeing the problem earlier?

Maybe:

Production planning was wrong.

Materials arrived late.

Nobody owned the deadline.

Capacity was exceeded.

A machine failed.

The customer changed the specification.

Someone knew there was a problem but didn't escalate it.

The scheduling information was inaccurate.

These are very different causes.

If you stop at:

"We got the order out."

you have resolved the customer issue.

You have not necessarily resolved the business issue.

Borrow one idea from incident investigation

I spent a large part of my career around health, safety and asbestos compliance, and there is a useful discipline from incident investigation that applies far beyond safety.

The Health and Safety Executive distinguishes between immediate causes and deeper underlying or root causes. Its guidance emphasises that addressing only the immediate cause may stop one occurrence, while investigating underlying organisational causes gives you a much better chance of preventing recurrence.

I am not suggesting you conduct an HSE investigation every time somebody forgets to order printer paper.

The thinking is useful.

Take a recurring late delivery.

Immediate cause:

The job wasn't completed on time.

Underlying cause:

Production was overloaded.

Go deeper:

Why was production overloaded?

Sales committed to a deadline without checking capacity.

Why could sales commit without checking capacity?

There is no reliable capacity-planning process.

Now we have reached something worth fixing.

Do that and you may remove dozens of future "emergencies."

Every significant fire needs two actions

I would make this normal inside the business.

Action one: contain it

What needs doing now?

Protect the customer.

Make the area safe.

Complete the job.

Find the material.

Cover the shift.

Collect the cash.

Whatever the immediate response genuinely requires.

Action two: prevent recurrence

What changes afterwards?

Process.

Authority.

Capacity.

Training.

Information.

Supplier.

Role.

Standard.

Commercial rule.

System.

If you only ever complete action one, firefighting is practically guaranteed to continue.

Start keeping a fire log

For two weeks, record every unplanned issue that materially interrupts you.

Keep it simple.

What happened?

Who brought it to you?

How much time did it consume?

Has something similar happened before?

Who should ideally have dealt with it?

Why couldn't they?

What would stop this category reaching you next time?

You may be surprised how repetitive your chaos actually is.

Fifty interruptions often turn out to be five problems wearing different clothes.

That matters because five categories can be fixed.

Fifty random crises feel impossible.

Classify the fires

I would put each issue into one of five buckets.

1. Genuine one-off emergency

Unusual.

Hard to predict.

Potentially unavoidable.

Deal with it and move on unless there is a useful lesson.

2. Recurring process failure

Same category keeps appearing.

Quality.

Scheduling.

Handover.

Quoting.

Ordering.

Invoicing.

This needs process improvement.

3. Ownership failure

The issue reaches you because nobody clearly owns it.

This needs responsibility.

4. Authority or capability failure

Someone owns it but cannot decide, lacks information or is not capable enough yet.

This needs authority, training, development or possibly a different person.

5. Capacity or commercial failure

There is simply too much work, insufficient margin, insufficient staffing or commitments the current business cannot reliably deliver.

This requires a commercial or structural decision.

That classification immediately stops you treating every fire the same way.

If the same fire happens twice, stop calling it bad luck

You do not need a mathematically perfect threshold.

My practical rule would be:

If materially the same category of problem happens twice within a relatively short period, ask whether you now have a system problem.

Three times?

I would need convincing that you don't.

A recurring customer complaint is data.

Repeated overtime is data.

Repeated late invoices are data.

Repeated staff shortages are data.

Repeated owner approvals are data.

The business keeps telling you where its weaknesses are.

Firefighting owners are often too busy fixing the signals to read them.

Build a recurring-problem register

This can be incredibly simple.

Problem.

Frequency.

Impact.

Likely cause.

Owner.

Permanent fix.

Review date.

Now your management team has a list of things the business is actively trying to eliminate.

This is different from an action list.

"Call customer" is an action.

"Remove the reason this category of customer order repeatedly fails" is improvement.

You need both.

The Office for National Statistics includes continuous improvement as one of the four dimensions in its UK management-practices measure. Higher-scoring organisations are characterised partly by reviewing processes and responding systematically to problems rather than simply allowing them to recur.

This is basic management work.

Not corporate bureaucracy.

Stop solving problems that somebody else should learn to solve

This one can hurt.

A manager arrives with:

"We've got a problem."

You know the answer.

It will take you approximately nine seconds.

So you give it.

Everyone leaves happy.

Except you just trained the system.

Next problem:

Owner.

Try replacing the answer with:

"What do you recommend?"

Or:

"What are the options?"

Or:

"What decision do you think we should make?"

Now the manager has to think.

If their answer is poor, coach the thinking.

Do not simply take the problem.

Firefighting often reveals weak management before it reveals weak employees

Owners frequently say:

"My staff bring me everything."

Perhaps.

Who should they be bringing it to?

If you employ twenty-five people and everyone effectively reports to the owner, you do not have an employee problem.

You may have a missing management layer.

Or managers who are not actually managing.

Skills England's current Operations Manager standard is instructive here. It describes operational management as including analysing performance, prioritising activity, implementing plans, managing continuous improvement and change, and ensuring business continuity.

In other words, dealing with normal operational complexity is part of management.

If the owner remains the person resolving all that complexity, ask what your managers currently own.

Managers should absorb complexity, not forward it

A functioning manager takes:

Ten staff questions.

Three minor problems.

Two conflicting priorities.

One customer issue.

And turns them into:

Decisions.

Actions.

Maybe one genuine escalation.

A weak management layer simply acts as a messaging service.

"The team said..."

"The customer wants..."

"Production needs..."

"What should we do?"

Everything continues travelling upwards.

That is not management leverage.

That is forwarding.

Change the rule for escalation

Define what genuinely needs the owner.

For example:

Material safety issue.

Major legal or regulatory exposure.

Serious cash risk.

A strategic customer likely to be lost.

Expenditure outside agreed authority.

A decision outside the manager's remit.

Something genuinely irreversible.

Everything else should normally be decided at the appropriate level.

This does not mean refusing to support people.

It means support no longer automatically includes taking ownership back.

Make recommendations compulsory

For managers, I like a simple rule.

If you bring me a problem you reasonably own, bring me your recommendation too.

Not because you must be right.

Because I need you to think before I think for you.

Instead of:

"Supplier can't deliver. What should we do?"

Try:

"Supplier can't deliver. We have three options. I recommend B because it protects the customer deadline with a £600 cost impact. Are you comfortable with me proceeding?"

Very different conversation.

Eventually even the final question may disappear because their authority becomes clearer.

Look at where approval is creating fires

Owner approval often masquerades as control.

Every discount.

Every purchase.

Every quote.

Every refund.

Every holiday.

Every recruitment decision.

Every supplier change.

Every exception.

Needs you.

Then you complain about interruptions.

Some controls are sensible.

But approval thresholds should match risk.

Ask:

What decisions genuinely justify owner involvement?

Which could move to managers within agreed limits?

Which could happen automatically within policy?

Every approval you remove from yourself creates fewer potential interruptions.

Give people decision boundaries

"Use your judgement" is often too vague.

Try:

You can refund customers up to £250 where these conditions apply.

You can approve overtime up to this weekly limit.

You can purchase from approved suppliers within this budget.

You can resolve complaints within these commercial boundaries.

You can change the schedule provided priority customers remain protected.

Now people know where independence ends.

That usually reduces unnecessary escalation.

Firefighting may actually be a visibility problem

Sometimes the owner gets involved because nobody saw the issue early enough.

Cash suddenly becomes urgent.

Why?

Nobody had a useful forecast.

Production suddenly becomes urgent.

Why?

No reliable backlog or capacity view.

Sales suddenly becomes urgent.

Why?

Nobody tracked pipeline until orders disappeared.

Quality suddenly becomes urgent.

Why?

Problems were visible only once customers complained.

You cannot manage what you discover too late.

This is where a small number of useful KPIs becomes valuable.

Not dashboards because dashboards look grown-up.

Early-warning information.

Ask which number would have warned us sooner

This is one of the best questions after a fire.

What information, had we seen it two weeks earlier, would have changed what we did?

Maybe:

Backlog hours.

Overtime.

Stock cover.

Debtor days.

Pipeline value.

Quote conversion.

Customer complaints.

Rework.

Absence.

Machine downtime.

Late jobs.

Pick the number that predicts the problem.

Then give someone responsibility for responding before it becomes a crisis.

Your weekly management meeting should reduce future fires

If the meeting is merely a retrospective tour of everything everybody did, change it.

I want management meetings looking at:

What is off track?

What is likely to become off track?

What recurring problem needs fixing?

Which decision is required?

Who owns it?

What is the deadline?

What do managers need from each other?

A strong meeting should catch sparks.

Not gather everybody together after the building is already burning.

Stop rewarding heroics more than prevention

This happens culturally.

Someone stays until 11pm fixing a disaster.

Hero.

Everybody praises them.

Someone quietly redesigns the process and prevents twenty future disasters.

Barely noticed.

Be careful what the business celebrates.

Heroics have their place.

Sometimes people do exceptional things and deserve recognition.

But if the same people repeatedly save the same process, eventually ask why the process still needs saving.

Firefighting can become part of people's identity.

Including the owner's.

You might secretly enjoy firefighting

This is worth considering.

Not every second of it.

But there is a particular satisfaction in being the person everyone needs.

Problem.

Decision.

Action.

Solved.

You are useful.

Visible.

Competent.

Strategic work rarely gives the same dopamine hit.

"Reviewed management structure for ninety minutes."

Not particularly dramatic.

No one applauds.

That is one reason owners drift back towards operational problems even while complaining about them.

The Fixer identity is powerful.

You need to notice whether part of the system exists because you keep volunteering to be its emergency service.

Stop jumping in before failure actually happens

You see someone doing something differently.

You think:

"This is going to go wrong."

So you intervene.

Maybe it would have gone wrong.

Maybe not.

If the risk is acceptable, allow people enough room to finish the decision.

Development requires consequences.

You cannot create capable managers while preventing them from experiencing any manageable difficulty.

There is a difference between protecting the business from serious risk and protecting everyone from learning.

Firefighting may be a capacity problem

Not every recurring problem is caused by poor process.

Sometimes the business genuinely does not have enough capacity.

You accepted too much work.

Sales grew faster than operations.

Management span is too wide.

A critical function is understaffed.

One person is covering three jobs.

No amount of root-cause analysis changes the fact that 500 hours of work cannot reliably fit inside 350 available hours.

Now you need a capacity decision.

Hire.

Subcontract.

Automate.

Delay.

Change lead times.

Increase price.

Turn work away.

Remove low-value work.

Do not systemise an impossible workload and call it fixed.

It may also be a margin problem

Low-margin companies often create firefighting because they cannot afford enough structure.

The owner becomes unpaid spare capacity.

Need another supervisor?

Owner covers it.

Need admin?

Owner does it at night.

Need somebody handling customer problems?

Owner.

The company appears profitable only because the owner's labour is absorbing jobs nobody priced properly.

Now firefighting is partly commercial.

You need to look at:

Pricing.

Margin.

Customer profitability.

Complexity.

Labour requirement.

No productivity app fixes a business model that requires permanent owner subsidy.

Some customers create disproportionate fires

Look at who generates the interruptions.

One customer may constantly:

Change specifications.

Ignore deadlines.

Demand priority.

Pay late.

Ring the owner directly.

Request exceptions.

Challenge invoices.

Cause rework.

Yet because they spend a lot, everyone calls them a "key account."

Maybe.

Calculate the cost of serving them properly.

Revenue is not the same as value.

Sometimes reducing firefighting means changing the commercial rules around a customer.

Or walking away.

Fix handovers

A huge amount of business firefighting happens between responsibilities.

Sales to operations.

Operations to finance.

Estimator to delivery team.

Day shift to night shift.

Project manager to site team.

Nobody necessarily performed their individual task badly.

The information simply failed to travel.

Ask after recurring problems:

Where did responsibility change hands?

What did the next person need?

Did they receive it?

Who confirms the handover is complete?

The gaps between roles are often more dangerous than the roles themselves.

Fix standards that exist only in your head

Employees cannot reliably meet invisible expectations.

You think:

"They should know."

Why?

Because you know?

Perhaps quality issues keep reaching you because only you can recognise what "good enough" looks like.

Make the important standard visible.

Example.

Checklist.

Tolerance.

Photo.

Specification.

Customer requirement.

Do not document everything.

Document what repeatedly causes judgement errors or rework.

Stop accepting temporary workarounds as permanent solutions

Temporary fixes are useful.

We need this order out today.

Fine.

Borrow stock.

Move the schedule.

Owner steps in.

But label it temporary.

Then schedule the permanent work.

Otherwise temporary becomes normal.

Six months later everyone thinks:

"Adam always approves that."

Nobody remembers it started as an emergency workaround.

Firefighting creates enormous amounts of accidental process.

Audit them.

Protect improvement time before the fires stop

This sounds contradictory.

You are firefighting because there is no spare time.

I am telling you to find time.

Yes.

Because if you wait for the fires to stop before fixing the causes, nothing changes.

Start small.

Ninety minutes.

Two hours.

Once a week.

Protected.

Use it exclusively for removing recurring operational problems.

Not email.

Not catch-up.

Not today's customer issue.

Article #24 dealt specifically with creating time to work on the business.

This is where you use it.

Every improvement block should target one repeated fire

Do not write a five-year transformation plan.

Choose something painful and recurring.

Example:

"We have had four late installations this month."

Use the session to understand why.

Change one thing.

Assign ownership.

Test it.

Review what happens.

Then tackle the next category.

This creates a positive loop.

One problem disappears.

Capacity returns.

That capacity fixes another.

Over time, improvement begins funding more improvement.

Do not try to systemise the entire company

This is how overwhelmed owners turn firefighting into a different overwhelming project.

"We need systems."

Suddenly someone wants to document 147 processes.

No.

Start where the pain is.

What breaks repeatedly?

What requires owner intervention repeatedly?

What creates material cost?

What creates customer risk?

Systemise that first.

The rest can wait.

Use a 30-day firefighting reduction plan

Here is a practical starting point.

Week 1: Capture

Log every meaningful owner interruption and operational fire.

Do not fix the whole business yet.

Look for patterns.

Week 2: Classify

Group the issues into categories.

Recurring process.

Ownership.

Authority.

Capability.

Visibility.

Capacity.

Commercial.

Identify the two categories consuming the most owner attention.

Week 3: Fix one cause

Take the biggest recurring category and ask:

What is the immediate cause?

What is underneath it?

Who should own the permanent fix?

What needs changing?

Implement something.

Week 4: Move responsibility

Define who owns that problem category going forward.

Give authority.

Create the relevant measure.

Agree escalation boundaries.

Then track whether the fire returns.

If it does, investigate again.

That is already considerably more sophisticated than spending another month simply reacting faster.

Track fires per week

If firefighting is the problem, measure it.

How many significant reactive incidents required owner involvement this week?

You might start at:

Then:

Perhaps eventually:

The number does not need to reach zero.

Businesses have problems.

The objective is that normal operating problems stop requiring extraordinary owner intervention.

Also track repeat fires

This matters even more.

If twenty issues happened but nineteen were genuinely different, that tells you something.

If ten issues happened and eight were repeats, your continuous-improvement process is failing.

Ask:

Did the problem come back?

That is a better measure than:

Did we close the action?

Completed actions do not matter much if the same issue returns next Thursday.

Put a name beside permanent fixes

Firefighting businesses often have endless collective responsibility.

"We need to improve scheduling."

Who?

"The team."

No.

Who owns improving it?

What specifically changes?

By when?

How will we know it worked?

HSE's investigation guidance uses the same basic logic in a different context: remedial actions should be clear about what must be achieved and by whom, with action aimed at underlying causes if recurrence is to be prevented.

Again, that guidance is about safety investigations.

The management discipline travels rather well.

When should the owner still get involved?

Absolutely sometimes.

This article is not about pretending the owner should become unreachable while everyone else deals with a disaster.

Owner involvement may be appropriate for:

Major strategic decisions.

Serious legal or regulatory exposure.

Material safety events.

Large capital commitments.

Critical customer relationships.

Severe financial risk.

Issues outside delegated authority.

A true business-continuity event.

The objective is not:

"Never involve me."

It is:

"Involve me where owner-level judgement is genuinely required."

That is a very different business.

Do you need an Operations Manager?

Perhaps.

But do not automatically hire one because you are overwhelmed.

First determine why the fires exist.

If nobody currently owns day-to-day operational performance, an Operations Manager may be exactly what is missing.

If you already employ an Operations Manager but everything still reaches you, another employee may not fix it.

Perhaps:

Their authority is unclear.

You undermine them.

Their capability is insufficient.

Staff bypass them.

Management information is weak.

Article #15 covered Coach versus Operations Manager, and the new roadmap also includes a dedicated article on when a growing small business should hire one.

Recruit against a real structural gap.

Not a feeling of exhaustion.

Do you need more staff?

Same answer.

Maybe.

But more people can create more communication, more handovers and more management complexity.

If your current problems are caused by unclear responsibility, adding four employees may produce four additional sources of escalation.

Capacity problems need capacity.

Management problems need management.

Process problems need process improvement.

Do not prescribe headcount before diagnosing the disease.

Do you need better software?

Perhaps.

Technology can improve:

Visibility.

Scheduling.

Workflow.

Communication.

Automation.

Data.

But bad processes do not automatically become good processes when software gets involved.

Sometimes they become faster bad processes with £700-a-month subscriptions.

Understand the fire first.

Then decide whether technology removes its cause.

What if the team is simply not good enough?

That can be true.

Not every problem is structural.

You might have:

The wrong manager.

Someone promoted beyond their capability.

An employee repeatedly failing to perform despite clear expectations and support.

Deal with it.

Firefighting can become a way for owners to compensate indefinitely for poor performance.

Person fails.

Owner catches it.

Customer stays happy.

Person fails again.

Owner catches it.

Eventually the business appears functional because the owner is hiding the performance problem.

That is not kindness.

It is delayed management.

Firefighting also hides business risk

This is one of the reasons it can survive for years.

The business looks better than it is because the owner keeps correcting it.

Customers receive their orders.

Cash gets found.

Problems are solved.

Employees get answers.

The company appears resilient.

But remove the owner and you discover how much resilience was actually one person's availability.

That is why firefighting and owner dependency so often appear together.

A controlled absence can reveal where the fires really are

Once the business has some structure, test it.

Take a day where you do not intervene in routine operations.

Then review:

What reached you anyway?

What went wrong?

What was solved without you?

What waited unnecessarily?

What authority was missing?

What information was missing?

This is not a holiday.

It is an operational test.

You learn far more about dependency by temporarily removing the dependency than by asking people whether they rely on you.

What should a less reactive business feel like?

Not quiet.

Not problem-free.

That is unrealistic.

It should feel more predictable.

Managers know what they own.

Problems get solved closer to where they occur.

Recurring issues trigger improvement work.

Key information arrives before a crisis.

Meetings identify risks early.

The owner is not the default destination.

There is enough capacity to improve how the company operates.

And when something genuinely unusual happens, the organisation has more energy available to deal with it because it did not spend the morning solving the same problem it had last Tuesday.

How Evolve works on firefighting

I do not start by telling an owner to manage their diary better.

I want to know what keeps breaking.

For a couple of weeks, we might look at:

What interrupts you?

Who brings it?

Why does it need you?

Has it happened before?

Which managers should own it?

Which decisions remain too high?

What information arrives too late?

Where is the business overloaded?

Which fires are created commercially?

Then we start removing categories.

One decision type.

One recurring problem.

One management gap.

One approval.

One customer dependency.

One broken handover.

The aim is not to make Adam Fox the person who helps you fight fires faster.

That would be a fairly terrible coaching proposition.

The aim is to redesign enough of the business that fewer fires require you at all.

This is where coaching can help, but you may not need it

You can do a lot of this yourself.

Start the fire log.

Identify the repeat problems.

Follow causes deeper than the immediate event.

Give managers clearer ownership.

Transfer authority.

Build one useful early-warning measure.

Protect improvement time.

Track recurrence.

You could make a substantial difference without paying anybody.

Outside help becomes useful when:

You cannot see the pattern because you are too close to it.

You keep solving problems faster than you investigate them.

Managers remain dependent despite repeated attempts to delegate.

You know you are the bottleneck but keep jumping back in.

The structure has outgrown what worked when the company was smaller.

Or you cannot determine whether the problem is people, process, capacity, management or your own behaviour.

That is where an external challenge can be useful.

The goal is not a business without fires

That business does not exist.

The goal is a business that learns.

Something goes wrong.

You contain it.

Understand it.

Change something.

Watch whether it returns.

Over time, yesterday's emergency becomes tomorrow's normal management.

That is continuous improvement.

And it is the opposite of firefighting.

So, how do you stop firefighting in your business?

Start by recognising that every urgent problem is not automatically unique.

Track the interruptions.

Group them.

Separate immediate fixes from underlying causes.

Stop solving every problem personally.

Make managers bring recommendations.

Clarify authority.

Improve early-warning information.

Fix weak handovers.

Address capacity honestly.

Look at customers and margins creating disproportionate complexity.

Protect a small amount of time every week to remove repeat problems.

Then measure whether those problems actually stay gone.

Do that consistently and the number of fires should begin to fall.

Not because you became more productive.

Not because your inbox got organised.

Not because everyone suddenly stopped having problems.

Because the business itself became better at preventing, detecting and solving them without needing you to arrive with the extinguisher every time.