The Manager Who Is Always Drowning

Every operation has one. The manager who is first in and last out, who answers calls at night, who knows where every problem on the floor is hiding — and who is, by every visible measure, drowning.

Owners tend to read this as commitment, and they are not wrong. It is commitment. But it is also a signal, and most businesses read it the wrong way round.

When your most dedicated manager is always underwater, the usual conclusion is that they have too much on their plate. So the business adds a supervisor, a system, or another pair of hands. A few months later the manager is underwater again. The workload was never the real problem.

Busy Is a Pattern, Not a Verdict

In my experience, a manager who is permanently overloaded is usually doing one or more of three things, almost always without realising it.

They are still doing the job they were promoted out of. They were the best on the line, so when pressure rises they step back in and fix it themselves. It is faster, and it feels like leadership. It is actually the old job, done again.

They are holding on to decisions. Every question routes through them because nobody was ever told what they are allowed to decide. The team waits, and the manager becomes the queue.

They are rewarding the urgent. Because they respond fastest to whatever is on fire, the fires keep coming to them. The team learns that problems get solved when they are escalated, not when they are anticipated.

A manager who is always firefighting is not short of time. They are short of structure, and the structure starts with themselves.

What Covey Saw

Stephen Covey's time management matrix, in The 7 Habits of Highly Effective People, sorts work by two questions: is it urgent, and is it important? The quadrant that matters most for a manager is the one that is important but not urgent: planning, building the team's capability, preventing the problem before it arrives.

It is also the quadrant that gets squeezed first, because it never shouts. Nobody phones to demand that you develop your supervisor. So the manager spends their days in the urgent quadrants, and the important, non-urgent work — the work that would reduce the fires — is the work that never gets done.

That is how the cycle sustains itself. The fires are the symptom of the neglected work, and the neglected work is the result of fighting the fires.

The Hidden Cost to the Team

The damage is not confined to the manager. A leader who is always drowning teaches the people around them three things: that bringing problems early is pointless because nobody has time to hear them, that deciding for themselves is risky, and that the way to be noticed is to wait until something breaks.

Capable people disengage. The ones who care most start covering for the gaps, and then they begin to drown too. Eventually the manager is not just overloaded; they are the ceiling on what the team can do.

A Manager's Guide: Getting Out of the Water

1. Track where your week actually goes. For five working days, note what you spent time on and who it was for. Most managers are surprised by how much of it is work that someone else could own.
2. Name the task you keep taking back. There is usually one. A report, a changeover, a supplier call. Ask honestly why you do it yourself. If the answer is “it's quicker,” it is the first thing to hand over.
3. Hand over the outcome, not just the task. Say what a good result looks like, what the person may decide without you, and when you will check in. Then let them carry it, including the first wobble.
4. Protect one block a week for the important work. Treat it like a customer meeting. Use it to build someone's capability or fix a recurring problem at its source.
5. Change what you reward. Recognise the person who spotted the problem early, not only the one who rescued it late. The team will follow what you notice.

The Real Work

None of this is a time management trick. It is a question of how a manager sees their own role: whether the job is to be the best problem-solver in the building, or to build a team that does not need one.

That shift is uncomfortable, because the old way is where the manager feels competent. Letting go means tolerating a slower first attempt, a different method, and a few mistakes that you could have prevented. It asks for exactly the self-awareness that technical training never covered.

A question for this week: if your most committed manager took two weeks off tomorrow, what would stop? Whatever the answer is, that is the part of the business that is built on one person rather than on structure.

If you would like to talk through what that looks like in your operation, book a call.

References Covey, S. R. The 7 Habits of Highly Effective People. Free Press, 1989.