Most AI rollouts strain people in the same way: the tool arrives, the old work stays, and the learning happens in the evenings. The risk to wellbeing is less the technology than the extra load and the uncertainty that travel with it. Leaders who subtract work before they add tools, budget real learning time and talk plainly about what is changing can adopt AI without exhausting the people who have to use it.
The hidden load of new tools
A new tool brings three kinds of work that rarely appear on the project plan. There is the learning curve itself. There are the weeks of running the old method and the new one side by side. And there is the background worry about what the tool means for each person’s job.
That load lands on teams that already feel stretched. A 2026 Henley Business School survey of about 2,900 UK workers found 61% felt unable to keep up with the pace of change at work. Headspace’s 2026 Workforce State of Mind report found 70% of employees said their organization had introduced new AI tools in the past year.
When change arrives that often, every rollout competes with the last one for attention and energy. The useful question for leaders is rarely whether to adopt. It is how to sequence the change, how fast to go, and what to take away to make room.
The gap between managers and teams
The same Headspace report found that 44% of people managers believe they are adequately preparing employees with resilience skills, compared with 23% of individual contributors. Managers and their teams are describing two different experiences of the same change.
That gap matters because managers set the daily pace. A manager who believes the team is coping adds the next tool, the next pilot and the next target. Closing the gap starts with asking often and specifically, rather than assuming, and with managers who are supported themselves.
A 45-minute manager briefing
Before any team hears about the tool, brief the managers who will carry it. A simple agenda:
- 10 minutes: why and what. The business reason, what the tool does, and what it will not be used for.
- 10 minutes: what stops. The stop-doing list, so managers can answer “what do I drop?” on day one.
- 15 minutes: the hard questions. Managers practice answering “Is my job safe?” and “What if I can’t learn it?” in pairs.
- 10 minutes: their own load. Each manager names one thing they need taken off their plate to lead the rollout well.
Managers who have rehearsed the hard questions answer them calmly. Managers who hear the plan at the same time as their teams cannot.
Five moves before the next rollout
These five moves cost little, and a leadership team can agree all of them in a single meeting.
- Subtract before you add. For every new tool, name one report, meeting or manual step that stops. Write it down and announce it with the launch, not afterward.
- Budget learning time. Put protected practice on the calendar, for example 90 minutes a week for the first six weeks, inside working hours. If learning only happens after hours, it is unpaid overtime.
- Say what is not changing. People absorb change better when they know what stays the same: their team, their manager, how they are reviewed, the customers they serve.
- Set the pace out loud. A pilot group first, then waves of teams, with a pause between waves to fix what broke. Publish the dates so nobody has to guess.
- Make “this is slower” a safe sentence. Many tools make work slower before they make it faster. When a leader says so first, everyone else can report problems without sounding resistant.
A 90-day plan for one rollout
Use this as a starting template for any tool that changes how a team works day to day.
| Phase | Leaders do | Teams get | Watch for |
|---|---|---|---|
| Days 1 to 15 | Choose the pilot team, write the stop-doing list, brief managers | A plain explanation of why, what changes and what does not | Rumors filling the silence |
| Days 16 to 45 | Run the pilot, hold a weekly 20-minute check-in | 90 minutes of protected practice a week and a named helper | Work drifting into evenings |
| Days 46 to 60 | Review the pilot honestly, fix the workflow, adjust targets | A say in what changes before the next wave | Pressure to skip the review |
| Days 61 to 90 | Roll out in waves, retire the old process on a set date | Training from pilot colleagues, not only from the vendor | Two systems running for months |
The most common failure point sits in the last phase, when the old process never actually retires. Set a date for switching it off, tell people the date, and keep it.
Scripts for the hard conversations
People can cope with uncertainty. What wears them down is silence, spin and promises that later break.
Announcing the tool
“We’re introducing a new drafting tool for proposals, starting with the Lexington team in March. We expect it to save time on first drafts within a couple of months, and to slow some things down at first. To make room, we’re dropping the weekly status report. You’ll have 90 minutes a week of practice time on your calendar. Your role, your manager and how you’re reviewed are not changing.”
When someone asks “Is my job safe?”
Do not promise what you cannot know, and do not dodge the question either.
“I can tell you what I know today. The plan is to change how the work is done, not to cut this team, and nobody’s role is changing this quarter. I don’t know every decision that will be made over the next year. When I know more, you’ll hear it from me first, and I’ll tell you when I expect to know.”
If you do not know what the plan is, say that, and find out before the next conversation.
The weekly check-in question
“On a scale of one to five, how manageable is your workload this week, with the new tool in it? What would move it up one point?”
Write the answers down. Patterns across a team tell you more about adoption than any usage dashboard, and they tell you where to slow down.
Example: an engineering firm’s first AI rollout
Example engagement. A 160-person engineering firm plans to introduce an AI tool for drafting specifications. The weigh-in finds project managers already work most evenings in the two weeks before each submission. The game plan pilots the tool with one team outside a submission window, drops a duplicate weekly report to make room, and trains 18 managers in the scripts above. The scorecard tracks the weekly workload question, after-hours messages per team in aggregate, and how many projects still run both the old and new methods at day 90.
Signs the pace is too fast
Watch for these signals during the first 90 days, and slow down when two or more appear together.
- Evening work rising. People mention practicing at night, or messages start arriving after hours.
- Shadow workflows. People quietly keep the old spreadsheet because they do not trust the new tool yet.
- Cynicism about change. “Another tool” becomes the standard reaction in meetings.
- More small errors. Rework and corrections climb as people switch between systems.
- Quiet managers. Team leads stop raising problems because they assume nobody wants to hear them.
Slowing down rarely means stopping. Extend the pilot by two weeks, move the next wave back a month, or add a second practice block. Then tell people why: “We’re seeing late nights, so the next wave moves to May.” That sentence costs nothing, and it builds trust for the next change.
Our free team burnout risk check is a quick way to open that conversation with a team. It asks about workload, control and recovery, scores the results in your browser and stores nothing.
Where to start
This week, take your next planned rollout and write its stop-doing list before anything else. Then book the protected practice time on the pilot team’s calendars, so it exists before the tool does.
If you want your managers ready before the next wave, our Leading Through AI Change workshop gives them the scripts, the pacing plan and practice on real scenarios, from $4,200 (indicative). It sits within our leadership workshops for managers, and pairs well with The Corner, our manager enablement program, for managers who want support between rounds of change. To plan it around your own rollout, book a discovery call.
