Your agency isn't resisting change, but is is likely running out of capacity to implement it. Here's what the 2026 workforce data reveals about where execution breaks down when it comes to public safety change management.
Article Highlights
Most public safety leaders can tell you what their agency needs to do differently. Between staffing, technology, operations, and AI governance, the priorities are well understood. What's less clear is how to execute those priorities effectively.
According to the 2026 Public Safety Workforce Trends Report, only 23% of agencies are fully prepared to manage significant change. The remaining 77% describe their readiness as inconsistent or nonexistent. The awareness is there. The execution infrastructure isn't.
This is an operational gap. Many agencies have strategies but lack the structure, resources, and processes to implement change under real-world staffing and workload conditions. Recognizing the need for change and executing it are two different capabilities. Most agencies have only developed one.
That distinction matters because every challenge your agency faces depends on change management. Reducing hiring friction, adopting new technology, and improving retention all require process changes. But if your agency can't execute change effectively, none of these priorities move forward.
Change management is a capability—one that needs to be repeatable. Keep reading to examine where change stalls at your agency and how to build an execution infrastructure that makes it stick.
When change initiatives stall, the instinct is to blame the people who “didn't get on board.” The data points elsewhere.
In the trends report, 44% of respondents identified communication gaps or misalignment as their top change management challenge. It’s followed by workload burnout (36%), motivation and buy-in (33%), resource gaps (32%), adoption resistance (28%), and lack of leadership support (25%). Communication isn't just the leading concern. It leads by a significant margin.
The qualitative data is even more revealing than the numbers. In the write-in responses, respondents highlighted breakdowns in how change reaches them, not resistance to change itself. They described messaging being inconsistent across leadership levels; changes announced without context or rationale; frontline staff learning about new initiatives informally, or after implementation already started. And when problems arise, leadership is the last to know because there’s no feedback loop.
Through these responses, a pattern emerges. Staff aren't opposed to change. They're opposed to change that arrives without explanation, without consistency, and without any mechanism for them to respond. When asked what needs to improve, communication and transparency ranked first (17%), followed by leadership alignment (13%) and employee involvement and feedback (10%).
The importance of transparency in change management goes beyond good communication practice. Agencies that execute change with clear rationale, aligned messaging, and genuine feedback channels are more likely to succeed.
Leadership and frontline workers experience change differently. Leaders are focused on strategy, planning, and organizational alignment. They're thinking about the plan—what change looks like on paper. In practice, frontline staff are experiencing communication breakdowns, workload pressure, and lack of support during implementation. They're living with the execution.
The consequences show up at the operational level. When leadership rolls out a new initiative without accounting for staffing realities, supervisor capacity, or the operational burden of implementation, change stalls at the shift level. One respondent described it as "no time to lead, just react."
There are usually several points of failure, not just one. Leaders aren't always aligned with each other. Strategy doesn't always get translated into a clear or realistic rollout. The "why" behind a change may never reach the people responsible for carrying it out. And the implementation workload is often underestimated, especially in agencies with staffing shortages.
Organizational size also impacts change. Larger agencies face more approval layers and slower coordination across divisions. Smaller agencies face resource constraints. The challenge scales differently, but the result is the same: strategic intent isn’t executed effectively.
Leadership alignment has to come first. If command staff aren't aligned on the rationale, the timeline, and ownership, the change will stall before it ever reaches the frontline.
Start by establishing a single, consistent message before anything is shared across the agency. When different commanders communicate different priorities, staff default to inaction.
Realistically assess the implementation workload. If supervisors are already absorbing extra duties due to understaffing, adding a new initiative only sets them up to fail.
Assign clear ownership for each phase of the rollout. Without it, change becomes everyone's responsibility and no one's priority.
Build in regular checkpoints where leadership can review progress, address obstacles, and adjust the plan based on what's actually happening on the ground.
When it comes to change management challenges, motivation and buy-in ranks third in the report, cited by 33% of respondents. Adoption resistance follows at 28%. On the surface, both look like people problems. The qualitative data tells a different story.
"When employees understand why a change is being made and how it supports operational effectiveness or officer safety, they are generally more willing to support and adopt the change."
— Lieutenant, 2026 Workforce Trends Survey Respondent
Officers and staff aren't resisting change. They're resisting change they don't understand or weren't consulted on. When asked what would improve change management, employee involvement and feedback ranked third highest—behind only communication and leadership alignment.
Buy-in isn't a single moment of communication. Employee engagement in government agencies is built through involving the right people at the right stages over time. Without that involvement, well-planned change initiatives stall regardless of the strategy.
The best practices below won't guarantee buy-in, but skipping them almost always guarantees you won't get it.
Involve frontline supervisors in planning, not just rollout. Sergeants and shift supervisors will have to enforce the change daily. So their input on feasibility will reduce friction before implementation begins.
Connect the "why" to officer safety, operational effectiveness, or community impact. Policy compliance alone isn't a motivator. Officers respond to reasons that match the work they actually do.
Create an active and responsive feedback mechanism. When officers see their input shape a rollout, future feedback gets more specific and actionable. When they see it ignored, they stop offering it.
Identify frontline staff who can champion your initiatives. If supervisors buy in early, they can translate leadership intent into language that answers the questions you didn't anticipate.
Clearly communicate what will and won't change. Constant change is exhausting, especially for first responders who already operate in high-pressure environments. Knowing what stays the same gives them a foundation to continue to work from.
Most change initiatives don't fail because of poor strategy. They fail because there's limited capacity to implement them.
According to the trends report, workload burnout is the second highest change management challenge (36%). Resource and knowledge gaps rank fourth at 32%. Together, they point to the same problem: your agency doesn't have enough capacity to absorb new initiatives on top of existing ones.
The workforce data explains why. Sixty percent of agencies report staffing shortages, 43% report overtime above 10 hours per week, and 43% report early-career exits above 10%. Preventing burnout in public safety is difficult enough under normal conditions. Under sustained workforce strain, every new initiative competes directly with the capacity your team needs just to maintain daily operations.
The result is a constraint loop. Your agency needs to make changes because it's understaffed, but it can't execute change because it's understaffed.
“Workers are resistant to change when it is too frequent and they do not feel fairly compensated and/or supported due to the staff shortage.”
— Professional Staff, 2026 Workforce Trends Survey Respondent
Public safety agencies can't reduce service delivery while implementing change. They operate 24/7, often below authorized staffing levels. Most change management frameworks don't account for that. Given those constraints, here's how to approach change management realistically.
Limit the number of concurrent initiatives. When capacity is already strained, running multiple efforts simultaneously almost guarantees that none of them get the attention they deserve.
Sequence changes so each one builds on the last. Start with the change that reduces the most operational friction, then use that extra capacity to implement the next one.
Build implementation workload into your staffing plan before the rollout begins. Training hours, system migrations, and workflow changes all have a real cost in staff time. If that cost isn't planned for, it gets absorbed by supervisors who are already stretched thin.
Use technology to reduce the burden of change. Policy management software like PowerPolicy handles distribution and acknowledgment tracking digitally, so supervisors aren't managing paperwork on top of everything else. Policy microlearning through PowerRecall reinforces new content through AI-generated flashcards, keeping officers current without pulling them off the street for additional classroom time.
Most agencies approach change as a series of individual initiatives. By treating it as a capability instead, your agency can execute change effectively. And it will improve with every iteration.
Building that capability requires a few consistent practices.
Develop a standard communication framework before every rollout—one that answers what's changing, why, who owns it, and how feedback will be collected. Assess capacity honestly before committing to a new initiative. Involve frontline staff in planning, not just execution.
Finally, measure whether the change actually improved operations, not just whether it was implemented. Did the new policy reduce incidents? Did the scheduling change reduce overtime? Did the training approach improve comprehension? With repeatable change management, your agency can answer these questions confidently.
PowerDMS offers law enforcement solutions that make change easier to execute—so your agency can move faster, reduce friction, and build an execution infrastructure that compounds over time. Schedule a consultation to see how your agency can build that capability.