For decades, change at work had a shape. You rolled out a new system, everyone climbed the learning curve, and then you leveled off. There was a before, a during, and an after. The “after” is what let people breathe.
AI erased the “after.”
To lead a team through constant AI change, stop trying to slow the change down and start managing how it is delivered. Use three disciplines: Cadence, delivering change on a predictable rhythm; Curation, filtering the flood so teams only adopt what matters; and Capacity, protecting the team’s ongoing reserve to absorb what remains.
Key Takeaways
- AI change fatigue is a load problem, not a motivation or “fear of change” problem. The brain treats constant, unpredictable change as a threat and conserves energy by resisting.
- The generative AI wave is unprecedented in pace: adoption jumped from 33% of organizations in 2024 to 72% in 2025, so the learning curve genuinely never ends.
- The fix is not pushing more change. It is delivering the same change differently through Cadence, Curation, and Capacity.
- Adoption is where most rollouts break, with only 32% of business leaders reporting healthy change adoption by their employees.
The model you trained your team on last quarter updated twice since then. The workflow you finally standardized has a new feature that changes the whole approach. The tool that did one thing now does five. There is no leveling off, because the ground keeps moving.
This is not a fringe experience anymore: McKinsey finds that 72% of organizations now report using generative AI, up from 33% the year before, and 88% regularly use AI in at least one business function. The pace itself is the new condition of work.
Here is the friction leaders are feeling right now. Traditional technology updates were one-time events. AI models change, update, and alter workflows continuously. And the reality is brutal: teams already running at high volume have close to zero tolerance for a perpetual learning curve. When every week brings another “new way to do it,” people stop climbing. Implementation momentum does not slow down gradually. It stalls.
This is also not new in kind, only in degree. Even before AI, change had already outrun people’s patience. Gartner research reported in the Harvard Business Review shows that the share of employees willing to support enterprise change collapsed to just 38% in 2022, compared with 74% in 2016, while over the same period the average employee experienced 10 planned enterprise changes, up from two in 2016. AI did not create change fatigue. It poured fuel on a fire that was already burning.
As a behavioral scientist, I can tell you this is not a motivation problem or a “your people fear change” problem. It is a load problem. The human brain treats constant, unpredictable change as a threat, and a threatened brain conserves energy by resisting. So the harder you push nonstop change, the harder people freeze. The solution is not to push more. It is to change how change itself is delivered. That is where the three Cs come in.
Why Does AI Break the Traditional Model of Workplace Change?
Traditional technology updates had a clear shape: a beginning, a learning period, and a stable “after.” Teams could absorb the change, practice it, and move into competence before the next one arrived.
AI broke that shape. Updates do not wait for your team to be ready. Features shift before workflows are standardized. The learning curve has no top because the tool keeps moving underneath the climber. And teams that are already operating at full capacity have almost zero tolerance for a permanent learning curve.
The result is what I see in organization after organization: not resistance to AI specifically, but resistance to the experience of never being allowed to be competent before the next change arrives. That is a fundamentally different problem, and it requires a fundamentally different response. If you want a deeper playbook for getting people to actually embrace new tools, my work on AI adoption and the psychology of change unpacks it in more detail.
How Do You Deliver Change on a Predictable Rhythm? (Cadence)
C #1: Cadence
Cadence is the discipline of delivering change on a predictable rhythm instead of a constant stream. Same amount of change, radically different experience, because the team knows when it is coming.
The problem with continuous AI change is not only the volume. It is the unpredictability. When a new update or workflow tweak can land any day, your team lives in a low-grade state of readiness that never switches off. That is exhausting in a way the actual changes are not. This is not a soft observation. Neuroscience shows that aversive events that are not fully predictable have a greater negative impact on mood, state anxiety, and physiological indices of reactivity than those that are fully predictable. It is also why “Certainty” sits at the center of David Rock’s SCARF model of what the brain protects. In plain terms: an unpredictable threat costs your team more than a predictable one, even when the threat is identical. Cadence attacks the unpredictability directly.
Cadence fixes this by batching. Instead of pushing every AI update the moment it drops, you collect them and release them on a set rhythm the team can count on.
How to build cadence:
• Create change windows. Pick a predictable interval, for example the first Monday of the month, when new AI tools and workflow updates get introduced. Outside that window, the workflow is stable on purpose.
• Batch small updates together. Ten minor changes delivered as one thoughtful update feel manageable. The same ten dripped out randomly feel like chaos.
• Name the stable periods out loud. Tell your team “between these windows, nothing changes. You can just work.” That promise is what lets people stop bracing and start performing.
How Do You Decide Which AI Updates to Adopt? (Curation)
C #2: Curation
Curation is the discipline of deciding which AI changes your team actually adopts, and which ones you deliberately skip. Not every update is an improvement, and treating them as if they are is how you drown a team.
Here is the trap leaders fall into: they feel they have to keep up with everything. Every new feature, every model update, every “best practice” that trended this week. So they pass all of it down to their teams, and the result is a firehose that no one can drink from.
Your job is not to adopt every change. It is to protect your team from most of them so the few that matter actually land.
How to curate AI updates:
• Filter every update through one question: does this meaningfully improve an outcome we care about, or is it just new? “New” is not a reason to adopt. Impact is.
• Say no on your team’s behalf. Most AI updates can be ignored without any cost. Being the leader who absorbs that noise so your team never has to is a gift, not a failure to keep up.
• Adopt deep, not wide. One tool used well beats five tools used shallowly. Curation means committing to the changes that matter and consciously letting the rest go.
How Do You Protect Your Team’s Ability to Absorb Change? (Capacity)
C #3: Capacity
Capacity is the discipline of protecting and expanding your team’s ability to keep absorbing change over time. It is the reserve tank. Cadence and Curation reduce the load, and Capacity makes sure there is fuel left to carry what remains.
Teams have a finite budget for change, the same way they have a finite budget for hours. When you spend all of it, adoption stops, no matter how good the next tool is. Leaders who ignore this run their people to empty and then wonder why the rollout failed. The data backs this up: Gartner reports that only 32% of business leaders say they are achieving healthy change adoption by their employees. Adoption, not strategy, is where most change quietly dies.
Building capacity is not about doing more. It is about creating the conditions where change stays absorbable.
How to build capacity:
• Anchor what stays the same. In a period of constant change, stability is a resource. Tell your team clearly which parts of their work and role are not changing. Certainty in some areas creates the capacity to handle change in others.
• Build in recovery, not just rollout. After a significant change, protect a stretch of stable time before the next one. People consolidate a new skill during calm, not during the next scramble.
• Grow change as a muscle, on purpose. Teams that practice small, low-stakes changes get better at absorbing big ones. Confidence with change is built rep by rep, and it is the single best defense against fatigue.
The Bottom Line: Manage the Pace, Not Just the Change
Continuous AI change is not going to slow down. Waiting for the dust to settle is no longer a strategy, because the dust is never settling again.
But that does not mean your team has to live in permanent overwhelm. The problem was never that people cannot handle change. It is that no one can handle unpredictable, unfiltered, unlimited change. Cadence gives it a rhythm. Curation gives it a filter. Capacity gives it a reserve to draw from. This is the same behavioral logic I bring to every change management keynote and to the leadership teams inside my enterprise programs.
Your competitive edge in the age of AI will not come from adopting every update the fastest. It will come from being the leader whose team can keep absorbing change while everyone else’s team has quietly stalled. Manage the pace, protect the people, and the adoption takes care of itself.
Frequently Asked Questions About Leading Through Continuous AI Change
Why do teams resist constant AI change? Teams resist constant AI change mostly because of load, not fear. The brain treats unpredictable, nonstop change as a threat and conserves energy by resisting it. When people are never allowed to reach competence before the next update lands, they stop climbing the learning curve altogether, and adoption stalls.
How do you prevent change fatigue? You prevent change fatigue by managing the pace of change, not just the change itself. Batch updates onto a predictable rhythm so people stop bracing, curate ruthlessly so only high-impact changes reach the team, and protect recovery time and stable anchors so your team keeps a reserve of energy to absorb what actually matters.
What is change cadence? Change cadence is the discipline of delivering change on a predictable, repeating rhythm instead of a constant, random stream. You batch updates and release them in set windows, for example the first Monday of each month, and keep the workflow stable in between. The volume of change can be identical, but a predictable rhythm feels dramatically more manageable.
If your organization is wrestling with nonstop AI change, bring Dr. Michelle Rozen in to help your leaders turn the pace of change into a competitive advantage.
Sources
•Gartner via Harvard Business Review (2023), Employees Are Losing Patience with Change Initiatives. https://hbr.org/2023/05/employees-are-losing-patience-with-change-initiatives
• McKinsey (2025), The State of AI. https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai
•Grupe and Nitschke, Nature Reviews Neuroscience (2013), Uncertainty and Anticipation in Anxiety. https://pmc.ncbi.nlm.nih.gov/articles/PMC4276319/
•David Rock (2008), SCARF: A Brain-Based Model for Collaborating with and Influencing Others (applied framing for “Certainty”).
• Gartner (2025), Gartner HR Research Finds Just 32% of Business Leaders Report Achieving Healthy Change Adoption by Employees. https://www.gartner.com/en/newsroom/press-releases/2025-07-08-gartner-hr-research-finds-just-32-percent-of-business-leaders-report-achieving-healthy-change-adoption-by-employees
