What can you do when your team becomes tired of change?

An objection about the work may concern a specific process: a newly required piece of information is not yet available at the intended point. Change fatigue here is more about the experience of continually receiving further demands without the means to implement them. Both situations can occur at the same time.

In its explanation, Prosci distinguishes between the volume or burden of incoming changes and the ability to absorb them. It describes change fatigue as a possible consequence of being overwhelmed by change. You can find the original perspective at Overcome and Prevent Change Fatigue. This does not provide a diagnosis for your team.

Ask about the specific experience: Which new task is being added? Which existing task remains? Where do deadlines or expectations collide? The article Resistance to change addresses how to examine individual objections. Here, the focus is how several demands interact.

Perhaps new initiatives are met with scepticism from the outset. Perhaps feedback stops coming, or trials are repeatedly postponed. Such observations are a reason to ask questions. They prove neither a lack of motivation nor a particular psychological strain. Avoid a list that marks people as affected without context.

Describe what happens factually: “The trial was postponed twice in favour of urgent customer cases.” Available time is then an obvious question. By contrast, “The team has no appetite for change” is an interpretation that can conceal the conflict between objectives.

Pay attention to your own decisions too. Are deadlines moved without adjusting scope? Are new tasks added while earlier promises of relief remain unfulfilled? Looking at the team should not distract from examining leadership and programme decisions. These may offer more effective ways to make a difference.

Start with an affected team's day-to-day work. List current initiatives and the actions they require. A new tool may mean setting up access, attending training and practising a process. A new structure may bring additional coordination and changed responsibilities. The project name alone does not reveal this effort.

In a fictional service department, a new ticketing system, changed shift planning and a new handover rule run in parallel. Each initiative has a reasonable plan. Taken together, however, they call on the same experienced people for questions and trials. This overlap is not readily visible in the separate project plans.

Record which teams are particularly affected and when, what preparation is needed and which dependencies exist. For handling change saturation, Prosci recommends considering the change portfolio and its effects. The original article is 6 Strategies for Reducing Change Saturation. Here, the team overview serves as a small, practical aid to decision-making.

Distinguish whether an initiative can start later, start on a smaller scale or receive additional support. Each option has different consequences. Postponement provides relief now, but may create a bottleneck later. A smaller start reduces the scope of the trial. Additional support only helps if it is actually available for the specific task.

You must also name what will be removed from day-to-day work. A practice session is not free time if the same amount of customer work is still expected. The responsible manager should make the trade-off and disclose its possible consequences. Otherwise, the promise of relief becomes another demand the team cannot meet.

A concise decision might look like this: an existing internal report is suspended for the ticketing system trial; a designated contact handles questions; the new handover rule starts only after the first trial. This is a fictional example, rather than a universally applicable sequence. Your actual dependencies determine the right approach.

Ask about specific conditions: “I am clear about which of the current initiatives takes priority in my work” or “Enough time is available to learn the new process”. These statements are our own suggestions, rather than a validated scale for change fatigue. A value describes feedback on the individual statement.

Do not ask which colleagues can no longer cope with a change. That would generate speculation about people. For an organisational decision, you instead need indications of capacity, priorities and support. Sensitive individual cases belong in suitable confidential channels.

Consider the limits of confidential team surveys. The context in free-text responses can make people identifiable. The team should know who receives results and what may follow from them. A feedback channel also provides no relief if no responsible decision about the conditions raised follows.

First check whether your own commitment was implemented. Has the suspended report really been dropped? Is the contact person available? Has the start date of another initiative been firmly changed? An announcement of relief is not yet a changed working condition.

Then consider relevant feedback and work cases. Does the team know what takes priority? Can the trial take place? Can customer operations continue sustainably? Repeated statements should retain the same wording. If new priorities are added, include that context in the interpretation.

Do not expect one action to remove all scepticism. Several commitments may need to be fulfilled reliably. For the measurement approach and its limits, Measuring change management explains separate information sources. Putting transformation into practice explores how multiple initiatives work together.

A team survey is not a health instrument and does not replace any individual support that is needed. Personal health concerns or acute situations of strain require the appropriate professional contacts. Declining feedback on mood does not allow a medical explanation to be inferred.

Even a well-prioritised plan can contain changes that people reject. Interests, effects and the reasons for decisions then need open discussion. Limiting how much happens in parallel does not resolve every conflict; it creates a better basis for actually addressing the remaining tasks.

Finally, record who will maintain the overview in future. If several departments can launch further initiatives, there needs to be a shared place to resolve conflicting objectives. Otherwise, the same overlap will recur with the next initiative. This responsibility belongs to management and cannot be handed over to a questionnaire.

State explicitly which initiative now takes priority and which expectation is being withdrawn to make room for it. If only the sequence on a slide changes while all deadlines stay in place, you have not provided usable direction. Explain the trade-off through the affected tasks.

Then ask whether the new rule can be carried out in day-to-day work. A team lead might confirm which internal meeting will be dropped and how urgent customer cases will still be handled. Keep unresolved conflicts between objectives visible. Reliability here comes from decisions being honoured repeatedly, rather than another promise with no consequences for planning.

With EngageBeat Fokus, you can ask the team about clarity and support in short weekly surveys. Questions rotate, so a selected question will not automatically appear the following week. The results provide pointers for decisions about action. The Supporting transformation page shows the application. The app does not diagnose change fatigue or plan resources.