Transformations lose momentum when the load of change outgrows the organisation's capacity to absorb it. Transformation fatigue is the measurable result: research links it to exhaustion, lower commitment and intentions to leave, and the number of changes people have lived through predicts it. The second year stalls on capacity, not on belief in the case.
Where does a transformation's momentum actually go?
Into the same people. Most transformations run as a portfolio of initiatives, each with a sponsor, and each drawing on the same middle managers, finance partners and IT teams. McKinsey's research found value lost at every phase, from target-setting to after implementation. The loss is rarely one failed initiative. It is accumulated overload across all of them.
The arithmetic is simple and usually unexamined. A transformation office tracks initiatives. Nobody tracks the total demand those initiatives place on a given team in a given quarter. When the enterprise system cut-over, the new operating model and the cost programme all land on the same regional finance team in the same month, each initiative is on plan and the team is not. Momentum is lost in the gap between the plan's view, which is per initiative, and the organisation's experience, which is per person.
What is transformation fatigue, and is it real?
It is a measurable state, not a mood. Bernerth, Walker and Harris developed a six-item scale for change fatigue and found it positively associated with exhaustion, which in turn predicted lower commitment and higher intentions to leave. The people who carry a transformation can be worn down by it before any single initiative fails.
The study drew on change consultants and a manufacturing organisation in the United States that had been through a number of changes over three years, and treated fatigue as a perception that too much change is taking place rather than as resistance to any one change. That distinction matters for diagnosis. A team that resists a specific initiative has an argument with it. A team that is fatigued has no argument left, and will under-deliver on good initiatives and bad ones alike.
Does the number of changes matter more than their quality?
The count carries more weight than leaders expect. De Vries and colleagues studied an organisation that had been reorganised repeatedly and found a strong relationship between the number of reorganisations employees had experienced and their degree of change fatigue. Successful earlier changes did not soften the effect. Each change spends capacity, however well it went.
The authors' conclusion is that the costs of a reorganisation are usually booked as temporary transition costs when they behave like structural costs, because the effect on how people receive the next change persists. For a multi-year transformation this is the central planning error. Wave three is costed as if the organisation that receives it is the one that received wave one. It is not. It is an organisation that has already spent some of its capacity to absorb change, and the plan should be built for that organisation.
Why is the usual explanation for a stall wrong?
Because it names resistance when the mechanism is competition for attention. When a transformation slows, the standard reading is that people resist change and need more communication. More often several strategic shifts are competing for the same attention and capacity, and no amount of messaging adds capacity. The fix is in the plan's sequencing, not in its narrative.
The two diagnoses lead to opposite actions. If people resist, leaders communicate harder, run more town halls and add change champions, which adds load. If capacity is the constraint, leaders remove or delay initiatives, protect the teams that carry several at once and accept a slower timetable in exchange for one that holds. McKinsey's research found that embedding transformation disciplines into business-as-usual structures was more common among successful transformations, which is another way of saying that the work was given a place in the organisation's capacity rather than layered on top of it.
What are the early signals that momentum is going?
Milestones that slip across several initiatives at once, decisions that queue for the same few people, workstream leads who stop raising risks, and good managers leaving teams that sit at the crossing point of initiatives. None of these appears on an initiative dashboard. All of them appear in the calendars of the people the plan relies on.
A practical test is to pick the five teams that appear in the most initiative plans and ask each of them what they will not do this quarter. If the answer is nothing, the plan is relying on hours that do not exist. The transformation office can then do what it is well placed to do: sequence the initiatives against the capacity of the teams that carry them, rather than against the calendar of the sponsors who own them.
Where this stops
This note is about the capacity of the organisation that carries a transformation. It does not say whether the transformation's targets are right, how to design the initiatives or how to run a transformation office. The studies cited measured fatigue in specific settings, including public sector and manufacturing organisations, and describe tendencies rather than thresholds. They cannot say how much change a particular team can absorb.
How Atlas reads it
Atlas treats a transformation that has started to slow as new pressure on the same organisation: the arrangement has not changed, but what it is being asked to carry has. The common reading, that people resist change, is one of the diagnostic errors Atlas tests for. The alternative reading is that several strategic shifts are competing for the same attention and capacity, and the two call for different interventions.
The recommendation follows the intervention ladder: clarify priorities and drop or delay work first, resequence where the organisation is overloaded, reassign decisions that queue for the same people, and reach questions about individual roles last. Each judgement carries the evidence for it and what argues against it, and is bounded to this plan, this arrangement and a defined horizon.
Sources
- Jeremy B. Bernerth, H. Jack Walker and Stanley G. Harris, Change fatigue: Development and initial validation of a new measure, Work & Stress (2011)
- Machteld S. E. de Vries and colleagues, Repetitive reorganizations, uncertainty and change fatigue, Public Money & Management (2021)
- McKinsey & Company, Losing from day one: Why even successful transformations fall short (2021)
Questions
A state in which people perceive that too much change is taking place. Bernerth, Walker and Harris measured it with a six-item scale and found it associated with exhaustion, lower commitment and intentions to leave. It differs from resistance: a fatigued team is not arguing with a particular change, it has run out of capacity to absorb any change well.
Because the load accumulates while capacity does not. Early waves spend the attention and goodwill of the teams that carry several initiatives at once, and research finds that the number of changes people have been through predicts their fatigue regardless of how well those changes went. Later waves land on an organisation that is already partly spent.
Only if the problem is understanding. If the problem is capacity, more communication adds load without adding hours. The useful test is whether the teams at the centre of the slowdown can say what the transformation means for their work. If they can, and are still behind, the plan is asking more of them than they can carry.
Directly, with validated scales such as the six-item measure developed by Bernerth, Walker and Harris, and indirectly, by mapping how many initiatives draw on each team in each quarter. The second method is available to any transformation office from its own plans and usually shows the overload before the first method would.
Rarely all of it. The better move is to resequence: delay or merge the initiatives that land on the same overloaded teams, protect the people who sit at the crossing points, and keep the initiatives those teams are not involved in on schedule. A blanket pause loses momentum everywhere to fix a problem that is local.