How Public Sector Leaders Can Sustain Momentum Through Complexity.

Public sector leaders aren’t imagining it: the pace of change has accelerated. And the stacking of change is what’s wearing people down.

A new policy direction arrives before the last one is fully implemented. A process redesign collides with an audit cycle. A technology rollout launches while teams are still learning the previous system. In government, change rarely comes one initiative at a time. It comes in layers — policy, process, technology, funding, stakeholder expectations – and often your staff has limited capacity to absorb the cumulative impact.

That cumulative impact has a name: change fatigue. And if directors don’t address it directly, it quietly turns into resistance, disengagement, delays, and attrition — exactly when the mission can least afford it.

What Change Fatigue Looks Like in Government Teams

Change fatigue isn’t simply “people don’t like change.” It’s a capacity issue. Even highly committed public servants can hit a saturation point when they’re navigating constant shifts without time to stabilize.

You’ll see it as:

• Passive resistance which sounds like “We’ll wait this out”
• Workarounds and shadow processes because the new way doesn’t feel safe or clear yet
• Decision paralysis due to too many moving parts and unclear priorities
• Emotional flattening which shows up as less initiative, creativity, and discretionary effort
• Increased friction between teams, especially when changes cut across departments

In many government environments, fatigue is intensified by two realities leaders can’t ignore:

The work is mission-critical and public-facing. Mistakes can have real consequences for communities.

Teams often operate under constraints. Limited staffing, fixed timelines, compliance requirements, and competing mandates leave little slack for learning and adaptation.

Why Continuous Change Drains Capacity

Even if the public sector change is a good one, there are three common drivers of fatigue:

• Too many priorities; not enough focus. When everything is urgent, people stop believing any of it is important.
• Insufficient “meaning-making.” If leaders communicate the what without the why and why now, teams fill in the gaps, often with worst-case assumptions. By the way, negativity bias is real; during uncertainty, people default to threat-focused interpretations.
• Lack of stabilization time. Change requires learning. Learning requires psychological safety and time. When teams aren’t given time to become competent, the new way becomes associated with anxiety and failure.

The Director’s Job

At Emerson, we often adopt the mindset of an air traffic controller, where we help our prime teaming partner see the “flight map” of the organization. We identify the concurrent initiatives impacting the same stakeholders so we can anticipate conflicts, clarify messaging, and ensure smooth implementation of activities. This is particularly valuable in large-scale government projects with multiple stakeholders and initiatives.

The idea is to keep a structured but nimble approach, helping our partners meet project milestones, manage risks effectively, and deliver successful outcomes.

Sustaining momentum through complexity is less about “motivating harder” and more about leading with precision: designing the environment so people can execute without burning out.

Here are practical steps that work especially well for public sector teams navigating policy, process, and technology change.

Name the fatigue without blaming the team.

People often hesitate to say they’re overwhelmed in government settings because they think it sounds unprofessional. But, when leaders name change fatigue directly, it legitimizes their experience and opens the door to problem-solving.

Try language like:

• “We’ve had layered change for months. Fatigue is a normal response to sustained complexity.”
• “Our goal is not to push harder — it’s to work smarter and protect capacity while we deliver.”

This reduces stigma and creates shared reality: two ingredients that increase trust during uncertainty.

Create a “change portfolio,” not a change pile.

Most teams don’t struggle with change; they struggle with competing change. Directors can help by managing initiatives like a portfolio.

Here’s a simple approach:

1. List all active changes (policy updates, process changes, tech rollouts, reporting changes).
2. For each change project, clarify the impact level, required behavior shifts, who is affected, and
3. Then make explicit decisions:
   • The scope of change projects you’ll tackle: what to start, stop, or pause
   • The sequence of change projects: what to do first, second, and third

What matters here is not the perfect plan. What matters is the signal to your organization that leadership is actively helping to manage the changes, not just accepting them and insisting on more work.

Translate “change” into clear expectations.

Government teams often get change communications that are heavy on policy language and light on practical guidance. That’s where fatigue turns into confusion.