Leaders often describe their teams as tired of change. People sigh at the announcement of another initiative, attendance at kickoffs drops, and follow-through weakens. "Change fatigue" is a familiar label for this, and sometimes it is accurate. Often, though, something more specific is happening: the team has too many priorities and no agreed way to sequence them.
The distinction matters because the remedies differ. Telling an overloaded team to be more resilient does not reduce the load.
How to tell the difference
These questions help diagnose which problem you have. They are practical heuristics, not a formal test.
- Can people list all active initiatives? If the list differs by person, or no complete list exists, the team may be carrying work nobody has counted.
- Do initiatives compete for the same people? If the same five people sit on most efforts, capacity is the constraint.
- Are old initiatives formally ended? Teams often add new work without closing old work. The old work continues in the background.
- Is resistance about the change itself or the timing? People may support the idea and doubt that they can do it alongside everything else.
- Does the team understand why this change matters now? A change with a weak reason is harder to support when the team is stretched.
If the answers point mostly to capacity and sequencing, treat the problem as priority overload.
Step 1: Make all current work visible
List every active initiative, project, and recurring commitment that takes meaningful time from the leadership team's people. Include the unofficial ones. For each, note the owner, the people involved, the expected effort, and the date it matters. Most leaders are surprised by the total.
Step 2: Limit work in progress
Lean practice offers a useful idea: limit how much work is in progress at once, since finishing fewer things sooner usually beats starting many and finishing none. Decide how many major initiatives the team can carry at a time. A rough rule is to start with a number lower than the current count and adjust from there.
Step 3: Rank and decide what waits
Rank the list against the business outcomes that matter most this quarter. Choose the initiatives that proceed now, those that pause with a restart date, and those that stop. Tell the team directly. The act of stopping something is an important signal: it shows the leadership team is willing to make tradeoffs and not just add work.
Step 4: Close what is done or dead
Some initiatives are finished in practice but never marked complete, and some have lost their sponsor. Close them formally, say what was achieved or learned, and release the people. This frees capacity and credibility.
Step 5: Introduce new work through the same gate
Create a simple rule: a new initiative must name what it replaces or delays. The sponsor presents the outcome, the people needed, and the tradeoff to the leadership team. This turns "yes" into a decision with a visible cost.
When fatigue is still the issue
Sometimes the load is manageable, and people are tired because earlier changes were announced and abandoned. In that case, the remedy is credibility. Finish one change visibly, explain what was learned, and show that leaders will follow through. A team that has watched three launches fade will wait to see whether the fourth sticks.
What to say to the team
Name what you see: "We are carrying more than we can finish well. Here is what we are pausing and why." Acknowledging the load directly builds more trust than asking for enthusiasm. The Culture-to-Execution Sprint focuses an intact team on one live priority, which gives leaders a way to test this kind of focus over 12 weeks.