Change fatigue: why it happens and the early signs

Change fatigue happens when the changes landing on a team outrun its capacity to absorb them. The usual causes are overlapping initiatives, constant disruption to day-to-day work, low trust left over from earlier changes, and nothing being stopped to make room. You can see it early in behaviour (questions drying up, problems no longer reported, old spreadsheets coming back) well before an engagement or readiness score moves, and you can ask about it directly with a few open questions.

What is change fatigue?

Prosci’s guide to change fatigue quotes its advisor Evelyn Williams, who says it sets in when a person or team is “at least one change project past their capacity”. Gartner describes it in terms of what it does: apathy and frustration that hurt results, with change-fatigued employees less inclined to stay, lower in trust and less willing to go beyond their role.

This post is about a pattern in teams. It is not a way to diagnose burnout or any individual’s health. If someone is struggling, that is a conversation for their manager, HR or occupational health, not a survey.

Why does change fatigue happen?

Change saturation

Most organisations run more change than their people can take in. In Prosci’s Best Practices research, more than 73% of respondents said their organisation was near, at or beyond the point of saturation, according to its article on reducing change saturation. Gartner told its 2024 ReimagineHR conference that the average employee now goes through four times as many organisational changes as eight years earlier.

Overlapping changes that disrupt daily work

Volume matters less than disruption. In a 2024 briefing for finance leaders, Gartner said small, day-to-day changes such as a new direct manager, a reshuffled team or different responsibilities are more fatiguing than large organisation-wide transformations, because they hit people personally and one arrives before the last has settled. Gartner also named exertion: people cancelling personal plans or working out of hours to keep up.

Picture a ward that gets e-rostering, a new handover form and a restructure of its senior nursing posts in the same quarter. Each was planned by a different team, and each looked reasonable on its own. Nobody on the programme side saw all three landing on the same nurses.

Low trust from earlier changes

People judge this change by the last one. Prosci’s guide traces scepticism to past changes where promises were made and not kept, and apathy to a belief that feedback makes no difference. If the last system “would save two hours a week” and didn’t, expect the next promise to be discounted.

Nothing was stopped to make room

New work is added and old work stays. Prosci recommends keeping an inventory of every significant current and planned change, then postponing or cutting the projects you cannot support. Few organisations do the second half. A depot that gets new telematics while the old paper checks remain mandatory is doing both jobs.

What are the early signs of change fatigue?

Scores move late. People keep going until they stop, and an annual or quarterly survey catches the stop. These signs usually show up first:

• Briefings get fewer questions. Early on, a change creates noise; when people stop asking, it often means they have stopped expecting answers.
• Problems stop being reported. The help channel goes quiet while the workarounds grow.
• Old spreadsheets, paper forms and private lists come back next to the new system.
• People ask to move training to “next month”, or attend and don’t practise.
• Cynical shorthand appears: a nickname for the programme, or “this one will go away too”.
• Managers pass changes on as “just do the minimum for now”.
• The same few super-users carry every rollout, and then quietly stop volunteering.
• Overtime and moved leave cluster around go-live dates.

None of these proves fatigue on its own. Two or three in the same team, at the same time, is worth a conversation.

How do I detect change fatigue early?

Start with a list of what is landing on each team over the next six months. Most change portfolios are tracked by project. Tracking them by team is what shows you that the same 40 people in accounts payable are in five of them.

Then ask the people doing the work. Prosci’s advice is to stay alert to saturation by checking in regularly with managers, front-line employees and sponsors. Short, regular check-ins beat one big survey, which is itself another demand on tired people.

Questions to ask about change fatigue

1. What is changing in your work at the moment?
2. Which of those changes takes the most out of you, and why?
3. What has had to give to make room for them?
4. What are you still doing the old way, alongside the new way?
5. When did you last raise a problem with a change? What happened?
6. What would you stop or pause, if it were up to you?
7. What would help your team most over the next month?

Keep the questions on the work itself. “What has had to give?” gets concrete answers (the weekly one-to-ones stopped, the stock check moved to Saturdays) that you can act on. A rating of how exhausted someone is gets a number you can do little with and drifts towards a wellbeing assessment, which needs a different process.

The team climate matters too. Gartner found that when managers create a psychologically safe environment it can mean up to a 46% reduction in change fatigue, partly because people feel able to say when a plan does not fit the work. Our guide on how to measure psychological safety covers how to ask about it.

How do you ask about change fatigue without adding to it?

Keep it short and say why you are asking. Tell people what you will do with the answers and when they will hear back. Then do something visible: pause a project, move a go-live, drop the duplicate paper check. One visible change does more for trust than a long report.

Read results by team, never by person. Fatigue is uneven, and an organisation-wide average hides the warehouse shift or the finance team where it is building. Set a minimum group size so nobody can be picked out.

Spradley asks these questions in interviews. Each person gets a one-on-one AI interview, by text or voice, invited by email or Slack and answered on their own phone or computer in their own time. The interviewer follows up on each answer, so “it’s a lot” becomes the three changes that collided and the one that could wait. The report groups answers into themes with the quotes behind them, by department, and never shows numbers or ratings for fewer than five people. See our change management page, or start earlier with change readiness survey questions. Once a change is live, a post go-live pulse shows whether fatigue is slowing adoption.

Frequently asked questions

Key terms

change fatigue

The apathy and frustration that set in when the changes landing on a person or team outrun their capacity to absorb them.

change saturation

The point at which an organisation is running more change than its people can take in at once.

workaround

An unofficial way of getting a task done when the standard process or system falls short. Workarounds show exactly where a process breaks.

psychological safety

A team’s shared belief that it is safe to take interpersonal risks, such as admitting a mistake, asking for help or disagreeing. Amy Edmondson defined and measured it in 1999.

minimum group size

The smallest number of responses a group needs before its results are shown. Five is a common default; smaller groups are hidden or combined with a larger one.