The Chief Who Can't Let Go

Every department has one, or has had one. The chief who knows where every key is, who has the only login to the training records, who signs every check, who takes every call from the county, who has quietly become the one person the entire organization depends on to keep functioning.

Members will tell you he is a great chief. He probably is. He is also the biggest risk sitting on the department's roster, and almost nobody wants to say that out loud while he is still standing in the room.

I have spent close to four decades in volunteer fire and EMS leadership, and I have started and led organizations in my professional life as well. I understand the instinct to hold on. What I have also seen, repeatedly, is what it costs the organization when a leader never lets go.

Why Chiefs and Founders Hoard Control

Nobody sets out to become a single point of failure. It happens gradually, and usually for reasons that look responsible in the moment.

Early on, the chief or the founder does everything because there is nobody else. That is normal in a small or new organization. The problem is that "nobody else yet" quietly turns into "nobody else, period," because doing it yourself is faster than teaching someone else to do it, and because handing off a piece of the job feels like giving up a piece of control.

There is also an identity problem. For a lot of us, the role becomes part of who we are. Letting go of a task can feel like letting go of relevance. If I am not the one who signs the checks or takes the county's call, who am I in this organization?

And there is a trust problem, sometimes fair and sometimes not. A chief has watched a member cut corners or a treasurer's number not add up, and concludes it is safer to keep the important things close. That instinct is understandable. It is also how one person ends up holding a job that should belong to three or four.

The Real Cost of Being the Only One Who Knows

The cost is not abstract. I have watched departments discover, the hard way, that critical processes existed only in one person's head. A treasurer retires and nobody can find the login for the department's accounts. A training officer moves away and years of certification records leave with him. A chief has a medical emergency and the department cannot answer a basic operational question because he was the only one who ever answered it.

None of that is a hypothetical. It is the predictable outcome of an organization that let one person become indispensable instead of building people who could carry the load together.

There is a quieter cost too. When one leader holds everything, the people around him stop growing into leadership themselves. Why would they build the skill to run a budget meeting if the chief has never let anyone else run one? Talented members leave, not because they were pushed out, but because there was never room made for them to grow into something bigger. The department loses its bench without ever noticing the bench was empty.

Succession Does Not Start at Retirement

The mistake most departments make is treating succession as an event that happens near the end, instead of a practice that runs the whole time a leader is in the role.

Succession starts the day a leader decides to teach someone else how the budget process actually works, not just hand them a summary. It starts when a chief lets an assistant chief run an incident from start to finish and lives with the fact that it will not go exactly the way he would have run it. It starts when a treasurer trains a backup on the login and the process, long before anyone expects to need it.

Years before a handoff, not months. A leader who waits until he has announced his retirement to start developing a successor has waited too long. The person who steps into that role needs real reps, under real stakes, with the current leader still there to catch mistakes before they become department-wide problems.

What Letting Go Actually Looks Like

Letting go does not mean disappearing. It means deliberately building capability in other people, even when it is slower and even when it means watching someone do it differently than you would have.

Share the passwords, the vendor contacts, the process documents, the county relationships. Not as a formality after the fact, but as the ordinary way the department operates. If information disappearing with you would hurt the department, that information should already live somewhere else too.

Give people real authority before they need it, not just a title. An assistant chief who has never actually run anything is not being developed. He is being given a rank and left to hope the job teaches itself when the moment comes.

Accept that the next person will lead differently than you did. That is not a threat to your legacy. It is what a healthy organization looks like after you.

Ask the uncomfortable question honestly: if I were gone tomorrow, what would this department not know how to do? Then go teach that thing to someone else, starting now.

The Legacy That Actually Lasts

I understand the pull to be needed. There is real satisfaction in being the person everyone turns to. But the leaders I respect most were not the ones who made themselves indispensable. They were the ones who made themselves replaceable, on purpose, years before anyone asked them to step aside.

The department that falls apart the moment its chief leaves was never as strong as it looked. The department that keeps running, keeps improving and keeps developing new leaders after the founder walks out the door is the one that was actually built to last.

Letting go is not losing control. It is the last and most important thing a real leader does with it.

For a practical framework on building that bench before you need it, read the Guide to Succession Planning for Volunteer Fire and EMS Leadership.