Leading a Firehouse That Doesn't Want to Change

I have introduced new equipment, new procedures, new technology and new policy into firehouses more times than I can count, across nearly four decades in this business. I can tell you exactly how it fails. It fails when it shows up as an announcement.

A memo goes up on the board. An email goes out. A new officer stands in front of the crew at a meeting and explains that, starting next month, things will be done differently. And the room goes quiet in a way that has nothing to do with agreement.

Firehouses do not resist change because members are stubborn or backward. They resist it because a firehouse runs on trust and shared experience, and a memo respects neither one.

Why the Crew Doesn't Trust the New Thing

Every experienced member has a story about a change that was supposed to fix something and instead created new problems, because whoever introduced it never asked the people doing the job what the job actually required. That history does not disappear because a new leader shows up with good intentions. It gets applied to you by default, before you have said a word.

There is also the matter of respect. Members who have spent years, sometimes decades, doing something a certain way are not being asked whether the new approach might be better. They are being told it will be different. Even when the new approach genuinely is better, being told instead of asked reads as a judgment on everything they have done up to that point.

And frankly, some resistance is simply earned skepticism. Firehouses have seen plenty of new initiatives arrive with enthusiasm and disappear a year later once the person who pushed it moved on. Members who have been around long enough have learned not to invest themselves in something that might not last.

None of that means the resistance should win. It means the resistance deserves to be understood before it can be addressed.

Change Management Is Culture Work, Not a Memo

The mistake is treating change as a communication problem, something you can solve by explaining the new policy clearly enough or often enough. Communication matters, but it is the last step, not the first one.

The real work happens in conversations that take place long before the announcement. Talk to the members who will be most affected, and do it early enough that their input can actually shape the outcome, not just be collected as a courtesy after the decision is already made. Ask what problem they think needs solving, and listen for whether it matches the problem you are trying to solve. Sometimes it does not, and that gap tells you something important.

Identify the members other people actually listen to. Every firehouse has them, and they are not always the ones with the highest rank. If those members understand why a change matters and believe it was built with real input, the rest of the room follows differently than if they hear about it from a memo at the same time as everyone else.

Be honest about what will get harder before it gets easier. Every real change has a cost somewhere, a new step, a new habit, a learning curve. Members trust a leader who names that cost upfront far more than one who promises the change is all upside. They have heard that promise before, and they remember how it turned out.

Bring People In Without Steamrolling Them

There is a difference between winning buy-in and running over objections until people stop raising them. The second one might get compliance. It will not get commitment, and it will make the next change even harder to introduce.

Give people a real chance to push back, and mean it. If someone raises a legitimate problem with how a new procedure will work on an actual call, that is not defiance, it is information. A leader who treats every objection as resistance to be overcome, rather than as a signal to evaluate, ends up steamrolling exactly the people whose experience should have improved the plan.

At the same time, do not let the loudest objection become a veto over something the department genuinely needs. There is a difference between a member raising a real operational concern and a member who opposes anything new on principle. Leaders need to be able to tell those apart, take the first one seriously, and not let the second one hold the whole department hostage.

Pilot before you mandate wherever you can. Let a small group try the new approach, work out the rough edges in public, and report back to the rest of the crew in their own words. Members trust a peer's honest account of what worked and what did not far more than a leader's promise that it will be fine.

Follow through visibly. If members raised a concern during the process and you adjusted the plan because of it, say so. That single act tells the room that input was not a formality, and it makes the next difficult conversation easier because people believe their voice actually moves something.

Change That Sticks

The changes that actually stick in a firehouse are rarely the ones announced with the most confidence. They are the ones introduced with enough patience that the people affected helped shape them, enough honesty that nobody was surprised by the cost, and enough follow-through that members believed the leadership meant what it said.

That takes longer than sending a memo. It also actually works, which a memo by itself never does.

Leading a firehouse that does not want to change is not about overpowering the resistance. It is about earning the trust that makes the resistance unnecessary in the first place.

For more on how volunteer leadership earns that trust day to day, read Leadership in a Volunteer Firehouse Is Different.