The AI dividend: what staff expect from the time AI saves, and how leaders should answer
· 5 min read
UK workers want a share of the time AI saves, and many fear more work instead. Why silence about saved time slows adoption, and five steps for leaders.
In brief
When AI makes work quicker, employees want to know what happens to the time it frees up. Research from Howden Employee Benefits, reported on 11 November 2026, found that a third of UK workers would expect higher pay if AI saved their employer significant time or money, while others would prefer shorter hours, more job security or a share of the savings. At the same time, about half fear they will simply be given more work, half worry AI will be used to judge their performance, and half say they get no protected time for learning.
This article looks at why that gap matters. When leaders stay silent about where saved time goes, staff tend to assume the worst, and many respond by using AI less or using it without telling anyone. Drawing on Ian Hughes's book What Stays the Same, it argues that slow adoption is often a question of incentives rather than training. It sets out five practical steps for leaders, including deciding where saved time goes, setting clear limits on using AI to assess people, protecting learning time and rewarding good use openly. It also explains where training helps, where HR and legal advice are needed, and the limits of the research, which comes from a benefits adviser and does not publish its sample size.
The question your team is already asking
Every AI rollout comes with a promise of time saved. Fewer minutes on the first draft, the summary, the report, the reply. Leaders hear that promise and see productivity. The people doing the work hear it and ask a different question. If this makes my job quicker, what happens to the time it saves?
New research from Howden Employee Benefits, reported on 11 November 2026, suggests many UK workers have already formed a view, and it is not always a hopeful one.
What the research found
A third of workers (33%) said they would expect higher pay if their employer saved significant time or money through AI. Others would want something different in return: shorter working hours (16%), greater job security (15%), or a bonus or share of the savings (13%). Howden calls this the "AI Dividend".
The worries run alongside the hopes. Half (50%) are concerned their employer will introduce AI faster than staff can understand or adapt to it. Almost as many (49%) fear they will be expected to take on more work as AI makes tasks quicker. Half (50%) are worried that AI could be used to assess their performance, and 47% worry their role will change faster than they can keep up.
Learning time is a gap. 53% are concerned about finding time to develop new skills alongside their workload, and 50% say their employer gives them no protected time each month for learning and development. More than two thirds (68%) do not expect their pay to keep pace with growing responsibilities over the next five years. 42% are worried their role could be replaced by AI, rising to 63% in financial services and falling to 29% in education.
A word on the source. Howden is an insurance broker and employee benefits adviser, so it has an interest in conversations about pay and benefits. The published coverage does not give the sample size, the polling company or the fieldwork dates. Treat the figures as a useful signal of how people feel, not a precise national measure.
Other research published this week points the same way. A Censuswide survey of 2,000 UK employees for Imperial Lifelong Learning, which sells courses to working adults, found 17% use AI at work without their employer knowing, rising to 29% of Gen Z, while 26% say using AI at work feels dishonest. A survey of more than 10,000 working adults by Use.AI, an AI tools company, found 56% feel that saying "I don't know" has become a risk since AI arrived. Both are commissioned studies, but together they describe workplaces where people are making private decisions about AI because nobody has made the public ones.
What it means for leaders
The saved hour is not neutral. If leaders say nothing about where it goes, people fill the silence with the most likely story, and the most likely story is "more work for the same pay". Once that story takes hold, sensible people behave sensibly. They use the tool less, or they use it and keep the time, or they use it quietly so nobody raises their targets.
That is not resistance to technology. It is a rational reading of the incentives. Ian Hughes describes exactly this in What Stays the Same. He watched thirty-five capable people leave a helpful tool unused, threw training at the problem, and saw no change. His conclusion: "It was an incentive problem wearing a training problem's clothes. The capability was already there. The reason to use it was not."
The same book offers the question to start with: "The better question is not "what can we now cut?" It is "what do we do with the capacity we have just freed?"" The Howden figures suggest staff are asking that question too, and want to hear the answer from you.
Practical steps
- Decide where saved time goes before you announce the tool. Some of it might go to better service, some to learning, some to work that has waited years for attention. Say which, and review it openly after a quarter.
- Draw a clear line on performance. Half of workers worry about AI being used to judge them. Tell people what AI will and will not be used to assess, and who makes the final call on anyone's performance. A person should always own that decision.
- Put learning time in the diary. Protected time each month, agreed with line managers, is a stronger signal than any number of online modules people are expected to fit in around the day job.
- Make good use visible and rewarded. Praise, progression, more interesting work, recognition in reviews. If the only visible result of using AI well is a heavier workload, expect people to stop.
- Be honest about what is undecided. If pay or hours have not been worked out, say so, and say when they will be. Silence is read as a decision.
Where training fits
Most of these steps are leadership work, not technical work. Leaders need the confidence to talk about AI without overpromising, the skill to listen to concerns that sound like resistance but are really about fairness, and a clear way to set and explain the rewards. Training helps managers hold those conversations well, and helps teams learn to use AI in ways that are checked, owned and visible rather than hidden.
Honest limits
Training will not settle pay. Changes to pay, hours or contracts need HR involvement and, where terms change, proper employment and legal advice. In unionised workplaces they may need consultation. How much time AI really saves needs measuring in your own work, including the time spent checking it.
The aim is simpler than it sounds. Give people a reason to use the tool that they can believe, and keep your word on it.
Tags: ai adoption, leadership, reward, future of work, learning and development, employee trust
Sources
Join the Exchange free
Join free to unlock the complete knowledge library.
Founder membership is free for life
More from Esm
How should the service desk handle a Microsoft 365 outage it cannot fix?
4 min read
Deploying AI is the easy part: who runs it once it goes live?
5 min read
How do I compare help desk tool pricing before rolling it out across several departments?
4 min read
Turning 'not helpful' into a fix
1 min read
When the author leaves, who owns the article?
2 min read
Test after every change, or find out from users
1 min read
Related articles
How should the service desk handle a Microsoft 365 outage it cannot fix?
Treat a supplier cloud outage as your own major incident: log it once, tell people early on a channel that still works, update on a rhythm and review your dependency afterwards.
Deploying AI is the easy part: who runs it once it goes live?
Only a third of large enterprises have met the business case for their main AI programme. New research points to a gap in who runs AI after launch, and what leaders can do.
How do I compare help desk tool pricing before rolling it out across several departments?
Compare help desk tools on a full year's cost for your real agents, approvers and requesters in every department, not on the headline monthly price.
Turning 'not helpful' into a fix
'Not helpful' is free, honest feedback, and most of it goes nowhere. Turn that click into a fix.
When the author leaves, who owns the article?
Articles keep being read after their authors move on. Make sure the care for them does not leave too.
Test after every change, or find out from users
Knowledge changes fail quietly. A short, repeatable test after every change finds the problem before your users do.