It Wasn't Urgent Until It Bloody Well Was: How to Stop Firefighting in Your Business

There are genuine emergencies in business.

People get ill. Technology fails. A client suddenly has a problem that nobody could have predicted. A supplier lets you down. Something happens and whatever you had planned for the day has to move.

That's part of running an organisation.

You deal with it, rearrange things and carry on.

But there is another type of business emergency that I'm fairly sure most of us have experienced.

The entirely predictable one.

The insurance renewal that's been sitting in your inbox for three weeks.

The event that's been in the diary for six months.

The invoice that hasn't been paid but nobody followed up.

The proposal that was sent and then forgotten about.

The report deadline everyone knew was coming.

The annual campaign that has somehow managed to surprise everybody by happening at exactly the same time as last year.

They weren't emergencies when they first appeared.

They quietly sat there until eventually they became urgent.

I've certainly had those moments myself.

You're halfway through a busy day thinking, "Why am I having to deal with this TODAY?"

And then comes the slightly uncomfortable realisation that you actually knew about it three weeks ago.

The problem wasn't necessarily the deadline.

The problem was that nothing happened between knowing about it and it becoming urgent.

And when that starts happening regularly across a business, it's worth looking at why.

Why do businesses get stuck in firefighting mode?

Firefighting can feel surprisingly productive.

There's a problem. You solve it.

Someone needs an answer. You give them one.

Something needs fixing. You jump in.

By the end of the day you may have dealt with twenty different things, made dozens of decisions and been incredibly busy.

But being busy and moving the business forward aren't always the same thing.

Constant reactive working comes with a cost.

Planned work gets interrupted. Deadlines become tighter. Mistakes are more likely. Other members of the team start reacting too. Decisions are made quickly rather than thoughtfully.

Most importantly, there is very little space left to look ahead.

That's when businesses can find themselves stuck in a cycle.

Everyone is so busy dealing with today's urgent work that nobody has time to prevent next week's urgent work.

Firefighting isn't always a time-management problem

When an organisation tells us they're overwhelmed, one of the most useful things we can do is look underneath the workload.

Because "we're too busy" doesn't necessarily tell us what the actual problem is.

It might be capacity.

But it might also be unclear responsibilities.

It might be a lack of follow-up.

It might be information sitting with one person.

It might be a process that hasn't kept pace as the organisation has grown.

It might be that nobody is looking far enough ahead to see what's coming.

Or it could be several of those things at once.

This is why simply adding another person to an overwhelmed business doesn't automatically solve the problem.

If the underlying way of working remains reactive, you've sometimes just added another person to the firefighting team.

Good business support should help you understand why the fires keep starting.

Look at the next 7, 30 and 90 days

One simple habit I find incredibly useful is regularly looking at the business through three different windows.

The next 7 days

What definitely needs to happen?

This is the immediate operational view.

Look at meetings, client commitments, payments, deadlines, events and anything the team needs to deliver.

Is it clear who owns each thing?

Does everyone have what they need?

Is there anything that could cause a problem this week if it's ignored?

You're not trying to plan every minute. You're simply making sure nothing obvious is about to catch you out.

The next 30 days

This is where you start asking a slightly different question:

What needs starting?

Perhaps you've got an event next month.

A contract is coming up for renewal.

A client project will need resources.

A marketing campaign needs creating.

Something needs approval from a trustee, director, client or external organisation.

It might not need to be completed today, but something may need to happen today to make sure it isn't being done in a panic four weeks from now.

The next 90 days

This gives you enough distance to start seeing patterns rather than individual tasks.

What projects are coming?

Are there seasonal campaigns?

Funding deadlines?

Busy periods?

Events?

Staff holidays?

Contract renewals?

Reporting requirements?

Business development opportunities?

This isn't about predicting every possible thing that could happen.

It's about giving yourself enough visibility to prepare for the things you already know are going to happen.

Stop using your memory as a business system

This links closely to something I wrote about recently: the amount of business knowledge that can end up living in one person's head.

Your memory is brilliant for lots of things.

Running the operational side of a growing organisation probably shouldn't be one of them.

If something needs doing every month, create a recurring task.

If someone needs following up, put the follow-up in your CRM.

If there's an important deadline, set a reminder well before the actual deadline.

If a process happens regularly, create a simple checklist.

If somebody else is responsible for something, make that ownership clear.

None of this needs to involve complicated software or enormous procedure manuals.

Sometimes the best business system is incredibly simple.

The important part is that the organisation isn't relying on somebody remembering something at exactly the right moment.

Because eventually they won't.

Clear ownership prevents a lot of unnecessary emergencies

One of the biggest causes of reactive working isn't that nobody knew something needed doing.

It's that everybody thought somebody else was doing it.

A task without a clear owner can sit very happily on a list for weeks.

Then the deadline arrives and suddenly several people are asking:

"Who's doing this?"

That's why good delegation isn't simply about assigning tasks.

People need to understand what they're responsible for, when it needs to happen, what decisions they can make and when something needs escalating.

This is particularly important when you're using outsourced business support.

You don't want an outsourced team member waiting for you to remember to tell them what needs doing.

Wherever possible, the systems and communication around the role should allow them to look ahead too.

That's when support starts creating capacity rather than simply helping you survive the workload.

Your systems should reduce work, not create more of it

Whenever I talk about systems and processes, I think it's important to say this.

The goal isn't to systemise your business within an inch of its life.

You don't need a 97-page manual explaining how to send an invoice.

You don't necessarily need another piece of software.

And you certainly don't need to spend hours maintaining a system that's more complicated than the problem it was supposed to solve.

A good system should make something easier.

It might be a recurring task.

A shared calendar.

A simple CRM workflow.

A checklist.

A five-minute screen recording.

A reminder.

A clear owner.

A regular 30-minute planning meeting.

The question isn't, "Do we have enough systems?"

It's:

"Does the way we work make it easier for the right things to happen at the right time?"

Try the 7, 30, 90-day test

Take half an hour this week and look at your diary, task list, CRM, projects and commitments.

Ask yourself:

In the next 7 days, what definitely needs dealing with?

In the next 30 days, what needs starting?

In the next 90 days, what can we already see coming?

Then look for anything that currently depends on someone remembering it.

Give it a home.

Give it a date.

Give it an owner.

You don't need to overhaul your entire business in an afternoon.

Start with the things that repeatedly become urgent.

Because you can't prevent every fire.

But you can stop leaving quite so many boxes of matches lying around.


Next
Next

Behaviour is data