top of page

Why Change Initiatives Fail (And What to Do About It)

Updated: 4 days ago

Every leader I have ever worked with has faced the same painful experience: a change initiative that made perfect sense on paper collapsed the moment it met the organization. The policy was sound, the data supported it, and leadership was aligned. But somewhere between the planning meeting and the front line, it died.


After more than two decades working in public sector leadership, and through work that recently earned the 2025 Senator Paul S. Sarbanes Fire Service Safety Leadership Award, I have seen this pattern repeat itself across fire departments and city halls alike. The problem is rarely the change itself. The problem is how we lead it.


The Three Reasons Change Fails


Public organizations are not inherently resistant to change. They are, however, built for stability, procedural accountability, and risk management. That is a feature, not a bug. But it means that leading change in a public sector environment requires a different playbook than what most leadership training offers.


The most common failures come from three places.


First, leaders skip the diagnosis. They identify a problem, design a solution, and launch an initiative without understanding the actual root cause of the behavior or system they are trying to change. The solution does not fit the problem because no one fully understood the problem.


Second, leaders underestimate the social dimension of change. Organizations do not change because data told them to. They change because people trust the leader enough to try something unfamiliar. Trust is the real currency of organizational change, and it cannot be manufactured in a PowerPoint deck.


Third, leaders declare success too early. A change that looks implemented after 90 days is often just compliance. Real change takes 12 to 24 months to embed into an organization's culture, and most leaders move on to the next priority before the new behavior has a chance to stick.



A Case Study in Getting It Right


In 2023, the Roswell Fire Department undertook a longitudinal sleep study in partnership with Dr. Joel Billings of Embry-Riddle Aeronautical University. The Sleep Improved study examined how shift scheduling, sleep quality, and occupational health intersected for our firefighters.


What might look like a research project from the outside was, in practice, a change management initiative. We were asking firefighters to voluntarily participate in a study that tracked their sleep, wore monitoring equipment, and surfaced data about their own health and performance. In a profession where toughness is currency and vulnerability is often seen as weakness, that is a significant ask.


It worked. And it worked because we approached it the right way.


We started with trust, not just data. Before we asked anyone to participate, we built relationships with the crews and their union leadership. We explained the why in plain language, not administrative language. We committed to sharing results transparently and acting on what we found.


We also accepted that change would be slow. The study ran over multiple shifts and seasons. We tracked, adjusted, and communicated along the way. And when the results were presented at Science to the Station: NERDSTOCK 2025, and the department received the Sarbanes Award, the firefighters who participated owned that outcome. That ownership matters more than any award.


What This Means for Your Organization


Whether you lead a fire department or a city manager's office, the principles are the same.


Change requires diagnosis before prescription. Take the time to understand what is actually driving the current state before designing the future one. Involve the people closest to the problem in that diagnosis.


Change requires trust before compliance. Build relationships with the people who will carry the change before you announce it. If they hear about a new initiative in a staff meeting for the first time, you have already lost ground.


Change requires patience over performance. Design your implementation timeline to last longer than you think you need. Build in checkpoints, feedback loops, and opportunities to adjust. Celebrate progress, not just outcomes.


The Bottom Line


Leading change in public organizations is hard. It is supposed to be. These institutions exist to serve communities, maintain equity, and operate with transparency and accountability. The same systems that make them resistant to bad change also make them resistant to good change.


Your job as a leader is not to eliminate that friction. It is to work with it, earn trust within it, and lead people through it with clarity and patience.


If you are working through a change challenge in your organization right now, I would be glad to think through it with you.



Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page