Change saturation

In plain terms

Change saturation is a capacity problem. Each change on its own may be sensible. Together they ask the same people to learn, attend, report and adjust more than their working week allows.

The useful shift is from asking "is this change a good idea?" to asking "what else are these people carrying while we do it?" The first question is about the change. The second is about the people, and it is the one that saturation is about.

Where the term is used

Change saturation is a practitioner term. Prosci, the firm behind the ADKAR model, says change saturation occurs when many change initiatives are being implemented within an organization and leadership fails to consider all of them. Its model treats saturation as two forces meeting: change capacity, which it says is influenced by an organization's culture and history, and change disruption, which it describes as the collective impact of multiple simultaneous changes (Prosci, n.d.). That is creator material from a firm that sells change management services, not an independent finding.

Researchers have studied the same territory under other names. Stensaker, Meyer, Falkenberg and Haueng (2002) wrote about excessive change in Organizational Dynamics. Rafferty and Griffin (2006) measured the perceived frequency of change. Herold, Fedor and Caldwell (2007) measured the amount of other change going on around a given change. None of their titles or abstracts use the word saturation, which may be why searching the research literature for it finds little.

What the research says

The research supports a narrower claim than the popular one. Frequent and overlapping change is linked to how people experience a change, but not always in the simple direction of "more change, worse results."

Frequency is its own experience. Rafferty and Griffin (2006) separated three perceptions: how frequent change is, how much it affects a person, and how well it is planned. In their repeated cross-sectional study, which measured change perceptions a month before employee attitudes in consecutive years, the three were moderately to strongly intercorrelated yet showed different relationships with outcomes; their model ran through uncertainty to job satisfaction and turnover intentions. Because frequency and planning were separate perceptions, a change can be well planned and still be one of many.

Where change overlaps, confidence and commitment are more closely linked. Herold, Fedor and Caldwell (2007, abstract read) studied 25 different changes with a multilevel design. After controlling for aspects of the change itself, the positive relationship between people's self-efficacy and their commitment to a given change was stronger as the amount of simultaneous and overlapping change around them increased. Read plainly: where more change was going on around people, how confident they were mattered more to how committed they were to a given change.

Many changes, many strains. Bernerth, Walker and Harris (2011) framed change fatigue as a problem of multiple organizational changes, using data from a manufacturing organization that had undertaken a number of changes over three years, and found change fatigue linked to exhaustion. Kiefer (2005) found ongoing change associated with negative emotions, which in turn predicted lower trust and more withdrawal one month later. See change fatigue for those studies.

Turbulent settings. Morin and colleagues (2016) followed 819 employees over three waves in a setting they describe as marked by multiple and ongoing changes. Beliefs about whether changes were necessary and legitimate were more strongly tied to commitment to change, and beliefs about support to psychological empowerment. In a setting marked by repeated change, beliefs about why changes were needed and whether they would be supported were each tied to how people reacted.

Where the evidence is thin

There is no validated saturation threshold. No study reviewed here tells a leader that a team can carry three changes but not four. Practitioner tools that score saturation are useful for conversation but have not been tested against outcomes in the research reviewed for this page.

There is also no trial of the obvious remedy. Pausing or sequencing changes to reduce load has not been tested in a controlled study reviewed here. The Unfrozen Loop says the same about its own pause rule.

How it maps to the Unfrozen Loop

Change saturation is the problem the second half of Part 4 of the Unfrozen Loop, review on a rhythm, then hold the pace, is written for: hold the pace. The Loop asks leaders to hold off adding new work while a change settles. In the studies graded for the Loop so far (October 2026), that pause rule has no trial yet, and it stays labeled as judgment. For how long a change might need to settle, see the Atlas answer on how long a change should settle.

The Herold finding also points at the middle's own weather, Part 5. Managers can end up carrying their own changes and their team's at once. If confidence matters more as load rises, supporting the people who doubt they can cope is part of the work, not an extra.

Common misreadings

"Saturation is a research finding." It is a practitioner model. Research on related topics uses different names and does not set a limit.

"Fewer changes always means better results." Herold and colleagues (2007) found that the link between confidence and commitment depended on how much other change was going on. One study does not settle how much load is too much.

"If each change is well managed, the total is fine." Rafferty and Griffin (2006) found that perceived frequency and perceived planning had different relationships with outcomes, so planning each change well is not the same as keeping the count down.

Using it well

Make the load visible. Before approving the next change, list what the affected team is already carrying and when each item will be finished. Leaders may see changes one at a time, through separate sponsors. The team sees all of them at once.

Sequence, don't stack. If two changes need the same people in the same month, move one. If neither can move, take something else off the team's plate.

Back the people who doubt they can cope. Herold's finding hints at where to look: ask in one-to-ones who feels least able to take on what is coming, and consider giving them practical support first. This is practice advice, not a tested remedy.

The worksheet below helps you run that count with a team. It saves nothing outside this browser.

CHANGE LOAD WORKSHEET

Change
Time it takes each week (Little or none / Some / A lot)
Settles by

1.
   Change: ______________________
   Time it takes each week: ______________________
   Settles by: ______________________

2.
   Change: ______________________
   Time it takes each week: ______________________
   Settles by: ______________________

3.
   Change: ______________________
   Time it takes each week: ______________________
   Settles by: ______________________

4.
   Change: ______________________
   Time it takes each week: ______________________
   Settles by: ______________________

5.
   Change: ______________________
   Time it takes each week: ______________________
   Settles by: ______________________