Change Fatigue Is Not Resistance: What Prosci’s Research Shows
Kinetiq Team
When teams push back on a new initiative, the default explanation in most organizations is resistance. People are resistant to change. They need better communication, more executive sponsorship, a more compelling “why.” But Prosci’s research on change management points to a different diagnosis entirely: 73% of organizations are near, at, or past their change saturation point. The problem is not that people are unwilling to change. It is that the volume of change has exceeded their capacity to absorb it.
This distinction matters because the interventions are completely different. If the problem is resistance, you push harder: more communication, more training, more urgency. If the problem is saturation, pushing harder makes it worse. The data says most organizations are dealing with the second problem while applying the first solution.
What the Research Shows
Prosci differentiates between two related but distinct concepts: change saturation and change fatigue. Saturation is the structural condition (more change is being demanded than the organization can process). Fatigue is the human symptom (exhaustion, disengagement, cynicism about new initiatives). Treating the symptom without addressing the structural cause is why most change management efforts underperform.
1. Change Saturation Is a Capacity Problem, Not a Willingness Problem
73% of organizations report being near, at, or past their change saturation point. Change saturation occurs when the volume, pace, and complexity of change exceeds the organization’s capacity to absorb it.
Prosci defines saturation as the point where the cumulative demand of all active changes exceeds the organization’s available capacity to implement them. This is not about any single initiative being poorly managed. It is about the total load. An organization might handle any one of its change initiatives well in isolation. But when five, ten, or fifteen initiatives are running simultaneously, each competing for the same people’s attention, energy, and compliance, the system breaks down. Saturation is an aggregate condition, and it can only be diagnosed and addressed at the aggregate level.
2. Fatigue Manifests as Behaviors That Look Like Resistance
When people are change-fatigued, they exhibit behaviors that are easy to misread: disengagement from new initiatives, skepticism about stated benefits, reluctance to attend training, failure to adopt new tools or processes. These behaviors look identical to resistance, and most organizations label them that way. But the root cause is different. A resistant person has not been persuaded that the change is worthwhile. A fatigued person may fully understand the rationale but simply does not have the bandwidth to engage with yet another initiative on top of everything else they are already absorbing.
3. The Volume of Change Has Accelerated Dramatically
The scale of the problem is growing. Deloitte’s 2026 Human Capital Trends research found that one-third of workers experienced 15 or more major organizational changes in the prior year. These include restructurings, technology rollouts, process redesigns, leadership transitions, policy updates, and strategic pivots. Each individual change may be well-justified. The cumulative effect is that employees spend an increasing share of their energy navigating transitions rather than executing their core work.
Deloitte reports that one-third of workers experienced 15 or more major changes in the prior year. When combined with Prosci’s finding that 73% of organizations are at or near saturation, the picture is clear: the change pipeline itself has become a primary source of organizational drag.
4. Saturation Reduces the Success Rate of Every Active Initiative
Prosci’s data shows that change saturation does not just make the newest initiative harder. It degrades the success rate of every change currently in flight. When people are saturated, their adoption of ongoing changes slows, their engagement with previously launched initiatives declines, and the benefits realization timeline for all active projects extends. This creates a compounding problem: the organization keeps launching new changes while the existing ones are not yet delivering value, further increasing the total load.
Why This Matters for Teams
The change fatigue problem is particularly acute at the team level because that is where the cumulative impact lands. Organizational leaders may see each initiative as a distinct, well-scoped project with its own timeline and resources. Team members experience the sum total of all those initiatives as a single, continuous stream of disruption to their daily work.
Consider a team that is simultaneously adapting to a new project management tool, implementing revised reporting procedures, participating in an organizational restructuring, adjusting to a new manager, and rolling out an updated compliance framework. Each of these changes has a sponsor, a communication plan, and a stated business rationale. None of them account for the fact that the team is also managing four other changes at the same time.
This is where the concept of sustainable pace becomes operationally critical. Pace is not just about workload. It includes change load. A team operating at a sustainable pace with respect to their task work can still be overwhelmed if the rate of change to their tools, processes, and operating context is too high. Most workload management frameworks ignore this dimension entirely.
The cost is real. When teams are saturated, they default to compliance over commitment. They do the minimum required to satisfy each initiative’s requirements without genuinely integrating the new behavior into their work. This explains why so many change initiatives “succeed” by project metrics (training completed, tool deployed, process documented) but fail by outcome metrics (adoption rates, behavior change, performance improvement).
The Gap the Data Reveals
Prosci establishes the diagnosis. What it addresses less fully is the operational question: how do teams and organizations manage their change pipeline the way they manage their work pipeline?
The first gap is visibility. Most organizations do not have a consolidated view of the total change load on any given team. Each function (IT, HR, Operations, Finance) launches its own initiatives independently. The aggregate impact is invisible until it manifests as fatigue, low adoption rates, or outright pushback. There is no “change portfolio management” equivalent of project portfolio management.
The second gap is sequencing. Even organizations that recognize saturation often lack the discipline to sequence changes rather than run them in parallel. This requires difficult prioritization decisions: which initiatives can be deferred, which can be combined, and which are genuinely time-sensitive. In practice, every initiative sponsor believes their change is the most important, and organizations default to running everything simultaneously rather than making the hard tradeoff.
The third gap is protection. Prosci identifies the need to protect people’s capacity to absorb change, but the mechanisms for doing so at the team level are underdeveloped. Most change management frameworks focus on the supply side (how to deliver change effectively) rather than the demand side (how to protect the capacity of the people absorbing it). The result is increasingly sophisticated change delivery methods applied to an increasingly exhausted workforce.
What This Looks Like in Practice
Managing change fatigue as a systems problem requires three operational shifts: making change load visible, protecting execution rhythms from constant disruption, and building the team’s capacity to absorb change over time.
Change Load Auditing
Teams need a simple, visible inventory of all active changes affecting their work. This is not a complex change management database. It is a list: what is changing, when, and what it requires from this team. When the list exceeds what the team can reasonably absorb (and most teams will be surprised by how long the list is), it creates the evidence needed to push back on additional changes or negotiate sequencing. The shift from jobs to capabilities that Deloitte identifies only works if teams have the capacity to actually develop those capabilities, which requires managing the change load that competes for their attention.
Protecting the Execution Rhythm
Every team has a core operating rhythm: the recurring meetings, reviews, and work cycles through which they produce their primary output. Change fatigue intensifies when this rhythm is constantly disrupted by change-related activities (training sessions, tool migrations, process workshops, reorganization meetings). Healthy teams protect designated execution time from change-related interruptions. They batch change activities into specific windows rather than allowing them to fragment every week.
Sequencing Over Stacking
The most practical intervention for change saturation is also the hardest: saying “not yet” to changes that would push the team past its absorption capacity. This does not mean blocking change. It means sequencing it. Rather than launching three new initiatives simultaneously, teams and their managers negotiate phased adoption: fully absorb one change before introducing the next. This requires managers who are willing to have difficult conversations with stakeholders about timing and capacity, but it produces dramatically better adoption and less fatigue.
Building Absorption Capacity
Over time, teams can increase their capacity to handle change by strengthening their operating fundamentals. Teams with clear priorities, strong communication norms, and established decision frameworks can absorb new changes more readily because they have less ambient friction. A team that already knows how it makes decisions, how it communicates about priorities, and how it handles disagreements can integrate a new tool or process with relatively low overhead. A team without those foundations experiences every change as a threat to an already fragile equilibrium. This is why investing in team infrastructure is also investing in change capacity.
Related Reading
Written by
Kinetiq Team
Contributing writer at Kinetiq, covering topics in cybersecurity, compliance, and professional development.
