Most managers do not start the day planning to spend eight hours putting out fires.
They usually have a reasonable list.
- Coach two employees.
- Review last week’s performance.
- Fix the handoff problem that’s creating customer complaints.
- Prepare for a client meeting.
- Maybe even eat lunch somewhere other than their desk.
Then the day starts.
An employee needs an answer.
A customer issue gets escalated.
The numbers on a report look wrong.
A meeting gets added to the calendar.
Slack lights up.
Someone marks an email URGENT, which apparently means all existing priorities have now been canceled.
By 5:00, the manager has been productive all day.
They have also accomplished almost none of the work they planned to do.
That distinction matters.
And when everything is a fire, managers spend all their time holding the hose.
Busy Managers Aren’t Necessarily Effective Managers
There is a version of management that looks incredibly productive from the outside.
The manager answers quickly. They jump into difficult calls. They resolve customer complaints. They know where to find every number. Employees come to them when something goes wrong because they know the manager will fix it.
That manager is valuable.
They can also become a serious operational bottleneck.
The more problems managers personally solve, the less time they have for the work that prevents those problems from happening again: coaching, training, planning, documentation, process improvement, and developing better decision-making throughout the team.
This is not just a feeling created by a busy calendar.
Managers rarely get an invitation labeled:
“Spend 45 uninterrupted minutes fixing the root cause of a problem that will save you 20 escalations next month.”
They get a Teams message asking if they have “two seconds.”
Guess which one wins.
What Actually Counts as a Fire?
Operational problems are inevitable.
If you work in financial services, healthcare, customer service, insurance, or just about any business involving customers and employees, something will go wrong today.
That does not make it an emergency.
A useful place to start is by giving the word fire a higher bar.
A true operational fire generally has a few characteristics. There is meaningful risk. The consequences get significantly worse if nobody acts quickly. Existing processes cannot adequately contain the problem. And management involvement is actually necessary.
A compliance breach could qualify.
So could a serious security incident, patient safety issue, major outage, significant financial exposure, or a situation that puts an important customer relationship at immediate risk.
Those are moments when someone should absolutely interrupt the meeting, call the manager, and get the right people involved.
An incorrect report?
Probably not.
A customer who is annoyed but already moving through the normal escalation process?
Probably not.
An employee who is unsure which of two acceptable options to choose?
Definitely not.
The problem is that many organizations have lost the distinction between important and urgent.
Something can matter and still wait until 2:00.
Real Fires, Fake Fires and Repeat Fires
One way to make that distinction easier is to separate operational problems into three categories.
Real Fires
These are the situations where speed matters.
A healthcare organization discovers a potential privacy breach. A financial services team identifies a significant compliance issue. A SaaS platform experiences an outage affecting a large portion of its customers.
Delay creates additional exposure.
Escalation makes sense.
You want managers who recognize these situations quickly and act decisively.
The problem is not real fires.
It is everything else being treated like one.
Fake Fires
A fake fire does not mean the underlying issue is fake.
The problem is legitimate. The urgency is not.
A reporting discrepancy needs investigation, but the report is not due until Friday.
A customer wants an answer, but there is already an established process for resolving the complaint.
An employee encounters a situation they have handled before but asks their manager anyway because getting approval feels safer.
These things should get solved.
They just do not require a manager to abandon whatever they are currently doing.
This distinction is surprisingly difficult inside organizations where responsiveness has become a measure of performance. The manager who answers in 30 seconds looks engaged. The manager who says, “Put it on the list for this afternoon,” can look less helpful, even when that is the better operational decision.
Repeat Fires
These are the most interesting.
The first time something goes wrong, it may genuinely be unexpected.
The fifth time the same thing goes wrong, the conversation needs to change.
Imagine that every Monday a report fails and a manager spends 30 minutes fixing it.
After a few months, that manager may become extremely good at fixing the report.
That is not the win it appears to be.
The actual question is why the report still requires emergency intervention every Monday.
Recurring fires usually point somewhere else: unclear ownership, inadequate training, bad handoffs, missing procedures, poor technology, unnecessary approvals, or employees who were never given enough authority to make routine decisions themselves.
At some point, repeated firefighting stops being responsive.
It becomes the process.
Organizations Are Surprisingly Good at Manufacturing Urgency
Employees are paying attention to what gets results.
If sending a normal request means waiting until tomorrow but writing URGENT gets an answer in five minutes, people learn something.
If asking a coworker gets no response but escalating to a manager gets immediate action, they learn something else.
If copying an executive onto an email suddenly causes six people to care deeply about a problem that existed yesterday, well, congratulations. You have created an escalation strategy.
People are not necessarily trying to be difficult.
They are adapting to the organization.
The same thing happens with decision-making.
Suppose an employee makes a reasonable judgment call and gets criticized because their manager would have handled it differently. The next time, the employee asks.
Soon they ask about everything.
The manager becomes frustrated that nobody can decide without them, while the employees have quietly learned that making decisions without the manager carries more risk than waiting for approval.
That is how an organization manufactures urgency and dependency at the same time.
And before we put all of this on frontline employees, leadership deserves some attention too.
Managers can have perfectly organized priorities until an executive asks for an unexpected report “ASAP,” forwards a customer complaint asking what happened, or decides one metric needs a meeting this afternoon.
Senior leaders create fires too.
Especially when a new priority gets added without an old one being removed.
Every Fire Has a Second Cost
The obvious cost of an interruption is the time it takes.
A manager spends 20 minutes on an escalation, so we lose 20 minutes.
But that math misses the larger problem.
What was supposed to happen during those 20 minutes?
Maybe the manager canceled a coaching session.
That employee keeps making the same mistake.
The mistake creates another customer issue.
The customer issue creates another escalation.
The escalation consumes more of the manager’s time next week.
Now the manager has even less time available for coaching.
The cycle becomes:
Fire → preventative work gets postponed → the underlying problem continues → more fires
Coaching does not usually feel urgent.
Neither does workforce planning.
Neither does documenting a better process, reviewing performance patterns, or figuring out why three teams keep experiencing the same problem.
But those are the activities that make an operation stronger six months from now.
If preventative work always loses to immediate work, managers eventually inherit exactly what you would expect: more immediate work.
The Hero Manager Can Become the Problem
Organizations love a manager who can save the day.
Something is reassuring about having that person around.
When things get messy, send it to Sarah.
Sarah knows the customer.
Sarah understands the system.
Sarah knows the workaround.
Sarah will fix it.
Eventually, everyone knows that Sarah will fix it.
Including Sarah.
This is where strong managers can accidentally create weak systems.
If a manager routinely steps into problems before employees have a chance to work through them, the team never develops judgment. If managers approve every exception, employees never learn the boundaries of their own authority. If managers immediately provide answers, people stop looking for them elsewhere.
The manager becomes indispensable.
That sounds flattering until they go on vacation.
Great managers should be highly valuable.
They should not be required for routine operations to function.
Their job is not to become exceptionally good at putting out fires.
It is to build a team that can handle more situations without needing one.
Audit the Last Two Weeks, Not the Next Two
There is no need to launch a major productivity initiative to figure out whether this is happening.
Look backward.
Have managers review the previous two weeks of calendars, escalations, and major interruptions.
Which situations genuinely required their involvement?
Which could have been handled by someone else?
Which happened more than once?
Which could have waited?
And, most importantly, what planned work was displaced because of them?
Patterns usually appear quickly.
You may discover that managers are spending hours producing reports nobody uses.
Or that one particular type of customer escalation always lands with management despite having a defined process.
Maybe employees need approval for decisions that carry almost no real risk.
Maybe managers are repeating the same coaching because expectations were never standardized.
The goal is not to account for every 15-minute block of the week.
It is to identify the work your organization has quietly decided managers must own.
Then decide whether they actually should.
The goal is not a perfectly calm operation. The goal is knowing what deserves the alarm.
Because your managers may actually be extremely busy.
The better question is what they are busy doing.
If most of their day is spent solving problems that could have waited, been delegated, or been prevented, the company does not have a calendar problem.
It has an urgent problem.
And the next time something gets escalated, there is one question worth asking before everyone starts running:
Is this actually a fire, or have we simply gotten very good at treating everything like one?