The Transformation Fatigue Problem: Why Organizations Struggle to Change

Gartner published two numbers this autumn that every leadership team should put on the first slide of its 2023 plan. In 2016, the average employee experienced around two planned enterprise changes per year. In 2022, about ten. Over the same period, the share of employees willing to support organizational change collapsed from 74 percent to well below half.
Five times more change. Half the willingness to carry it.
Too much, at the same time
By the end of this year, many organizations are running digital transformation, agile adoption, a restructuring, a hybrid work model, a cost program and a new ERP, often in parallel and often owned by different executives.
Each initiative has a business case. Each sponsor believes theirs is the priority. Each one demands time from the same middle managers and the same experts. Nobody sees the cumulative load, because nobody owns it.
The problem is not the quality of individual initiatives. It is their sum.
What fatigue looks like from the inside
Transformation fatigue rarely shows up as open resistance. It is quieter than that.
Employees attend the training and change nothing. Managers report green status on programs that are drifting. Good people stop volunteering for new initiatives because they know the next reorganization will make their effort irrelevant. Cynicism replaces enthusiasm, and cynicism is far harder to reverse.
I have seen organizations where the third transformation program in five years was greeted not with opposition but with a shrug. A shrug is more dangerous. Opposition can be addressed. Indifference simply waits for the program to end.
The leadership lesson: subtraction
We train leaders to launch. Strategy offsites produce new initiatives. Boards reward visible action. Very few incentives exist for stopping things.
Yet the ability to stop, prioritize and sequence may be the most underrated leadership skill of this period. Jim Collins suggested years ago that great companies keep a “stop doing” list as carefully as a to do list. It has rarely been more relevant.
In practice this means three disciplines.
Make the portfolio visible. One list of every change initiative, its owner, its demand on people and its expected value. Most leadership teams are shocked when they see it for the first time.
Set a capacity limit. Decide how much change the organization can absorb in a given period and do not exceed it, the same way a CFO would not exceed a budget.
Sequence, do not stack. Some changes depend on others. A new operating model built on top of a half implemented ERP will fail twice.
The board’s role
Boards contribute to the problem more than they admit. Every strategic review adds priorities. Very few remove any. A useful question for the next board meeting: what has this company deliberately stopped doing in the last twelve months?
Leadership question: Is the biggest obstacle to transformation resistance to change, or simply too much change happening at the same time?


