Skip to content
Broad watercolor washes in blue, ochre, sage and violet overlap across textured paper.

Guide

How to help people adopt AI at work

A practical AI change management guide to understand employee concerns, make room for practice, and choose support that fits the actual obstacle.

Jump to a section

AI change management helps people make a useful, supported change in how they work. For an adoption lead or team manager, that starts with understanding a recent attempt: what someone tried, what happened, and what would make the next attempt worthwhile.

A person who cannot judge an AI-generated answer needs different support from someone who can judge it but has no time to practise. Someone who has tried the tool and found the result worse deserves a conversation about the task itself. If an earlier rollout broke a promise, rebuild trust with commitments employees can inspect.

If you already have a technology change plan, review which practices carry over and what needs adapting for AI. Keep useful support arrangements while revisiting output checks and ownership after launch.

This guide focuses on those conversations and the decisions that follow. If your organization is still choosing which work AI should support, start with the enterprise AI adoption strategy guide.

Start with the last attempt

“Why aren't people using AI?” invites a broad opinion. “Show me the last time you tried it for this task” gives you something to investigate together.

Let the last attempt determine the next support decision

Start with the employee’s actual task and what happened, including the approved workaround they chose.

Skill or checking gap

Try a supported task and explain the source check

Keep the employee in control and observe where help becomes necessary.

Work-condition gap

Resolve access, time, instructions or ownership

Name the person who can change the missing condition.

Unsuitable use

Change or stop the proposed method

The existing process may be more dependable or require less complete effort.

Try the affected task again only when there is a worthwhile change to examine.

Ask the employee to walk through the work, using an approved example that can be shared safely. Follow the attempt far enough to see the checking and handoff, then ask:

  1. What were you trying to finish? Establish the task and what a good result would have looked like.
  2. Where did the attempt become difficult? Look for missing access, confusing instructions, poor output, extra checking, or an interrupted practice session.
  3. What did you do next? Returning to the old process may reveal a reasonable workaround.
  4. What would need to change before you tried again? Separate something the employee can learn from something another person must resolve.

If they have never tried, ask what has prevented a first attempt. Do not invent a skills gap from a missing login.

In a public discussion in Reddit's r/Training, one participant gave a direct reason for holding back.

Reddit

I haven't seen anything faster/better than I can do myself at the moment.

A Reddit userPosting in r/Training
Read on Reddit

The commenter reported having access to Copilot and other tools. Their role, employer and company size were not stated; this is their experience, not a product-performance comparison.

That response leaves several possibilities open. The task might be unsuitable. The person might need a better example or a way to check the result. The existing process might already be efficient. Ask to examine the work before deciding which explanation fits.

Choose support that fits the obstacle

The COM-B framework offers a useful lens for this conversation: behavior depends on capability, opportunity, and motivation. Capability includes knowledge and skills; opportunity concerns the conditions around someone; motivation includes habits and feelings as well as deliberate intentions. Susan Michie and colleagues developed the framework by synthesizing behavior-change frameworks. It was not a trial of enterprise AI adoption. The original COM-B paper.

Use those categories to broaden your questions. They are not labels for employees, and several conditions can matter at once. Someone may understand a task well, lack approved access to the necessary information, and worry about being judged for asking for help.

Consider a furniture retailer's customer-service team drafting replies about delayed deliveries. These illustrative comments connect a recognizable obstacle to an investigation. Confirm the explanation with the employee before choosing an action.

What someone reportsWhat to investigateWho can act
“The draft promises delivery on Friday, but I can't find that date in the order record.”
Practise checking the delivery date against the order and carrier records; leave an unconfirmed date unresolved.
A subject expert and the team manager
“I can see the order, but I can't access the carrier's latest delivery note.”
Check approved access and data-use rules before another attempt.
The relevant IT, data or policy owner
“The customer queue fills the shift, so I return to the reply template I know.”
Agree what work will move to make room for practice.
The manager who sets priorities
“I spend longer correcting the promised dates than writing the reply myself.”
Compare the complete task and consider changing or stopping the use.
The workflow owner and employee
“If replies become faster, will our daily customer target increase?”
Identify the decision or uncertainty behind the concern and who can answer it.
The manager and responsible leadership

When the explanation is unclear, compare the evidence for a skills gap, reluctance or missing opportunity before choosing support. A successful coached attempt and low routine usage can tell different stories.

When the obstacle sits upstream of employee practice, use COM-B to examine the person arranging training, advice or approvals. Follow the enabling action through to what colleagues receive.

Use ADKAR to identify individual support needs and assign rollout decisions when the conversation reveals an access, workflow or review obstacle. Give that decision to someone who can act.

A useful intervention changes the condition that is getting in the way. A workshop can help someone learn to check an answer. It cannot grant missing access or settle an unresolved staffing decision.

For junior recruitment decisions, compare entry-level employment evidence with the work and development a role will provide. Keep the hiring decision grounded in the actual role.

For people developing the enablement practice itself, compare career progression through responsibility and demonstrated work. Keep specialist growth and people management as explicit choices.

Make practice possible in the working week

Manager support is associated with more frequent AI use, although that does not establish that encouragement alone causes adoption.

78% vs 44%

reported frequent AI use with strong manager support versus others

Among US employees in organizations making AI available, 78% of those strongly agreeing their manager supports use reported using it a few times a week or more, compared with 44% of others. Gallup's February 2026 survey included 23,717 employees overall. This is a self-reported association.

GallupApril 12, 2026

Make support visible in decisions employees can recognize. Agree which task they will practise, which approved material they can use, who can help, and what can wait while they learn. An invitation to experiment is hard to act on when all existing deadlines remain equally urgent.

In the same r/Training discussion, another Reddit user described a team that spends a few weeks each year researching tools individually, then teaching each other what they learned. The team decides together whether to change its process. The commenter also described needing to remind colleagues about tools they had forgotten.

That is one team's self-report, with no stated employer or headcount. The useful detail is the shared decision after exploration, followed by reminders when the work calls for the tool. Your team may need a different cadence.

Use the employee AI literacy baseline to choose what people should be able to explain and demonstrate. For a next practice session, make these arrangements explicit:

  • A real task. Use something the participant expects to do again.
  • A checked example. Include the inputs, the output, and the corrections that mattered.
  • Available help. Name a person and a realistic way to reach them.
  • Time within the workload. Agree what is being postponed or reduced and who can approve the change.
  • A place to keep the learning. Save the useful example where colleagues can find it during the task.

Before assigning a course from a demographic label, separate age-group opportunity patterns from an individual's training need. Ask what the learner's work and current attempt reveal about the support to try next.

To connect everyday help with the learning program, route peer-learning questions to formal L&D or the responsible expert. Return the agreed answer to the people who teach and practise the task.

When AI changes junior work, redesign the assignments that supply practice and feedback. Keep the learning purpose and next responsibility visible alongside the finished output.

For experienced staff, preserve the decisions and outcome feedback that keep expert judgment current. Reconsider which practice the future role needs as routine preparation changes.

When a tool or procedure changes, refresh the affected training and replace obsolete instructions. Name the content owner, check the revised task and update the routes learners and coaches use to find it.

For a new employee, build AI onboarding around local sources, usable access and a supported first task. Prior tool experience does not supply the company's procedures or decision owners.

After a workshop, inspect the first independent task before choosing follow-up. Separate missing access or opportunity from a skill that needs further practice, then check whether the output can be accepted.

For support spanning several teams, define what an AI adoption manager should deliver. Keep the role's coordination work distinct from the decisions that remain with managers, technical owners and sponsors.

When a workflow needs integration, data or testing help, prepare a specific technical assignment before deciding whether to add a specialist role. Bring a permitted failure case and agree what the receiving expert will investigate and deliver.

To staff the wider program, compare estimated work with the hours each responsible person can actually provide. Check missing expertise and coverage before turning a total workload into a headcount request.

For a change or learning professional considering an AI role, choose a target duty and a supported development assignment. Compare the work you can already own with the capability you still need to develop.

For a recurring team review, use the weekly AI adoption routine for managers. It includes preparation, an agenda and follow-up around one real example.

If colleagues know more about AI than you do, agree a learning exchange and explicit delegation boundaries. Try one workflow yourself and identify which decisions still need your judgment or another expert.

For individual expectations, decide how AI use should count in performance reviews. Assess finished work, judgment and learning with the support conditions made explicit.

When approving an AI-assisted deliverable, review the work sample and the employee’s checking decisions. Establish what the output must do, verify consequential details and give unresolved requirements a decision owner before relying on it.

When a task becomes faster, agree what the available time will support. Include the person doing the work, service coverage and the receiving colleague before committing to more volume, better service or a more manageable day.

When protecting a window in the working day, distinguish thinking time from a genuine pause from work. Make clear what can wait and who handles incoming requests while the person is unavailable.

A champion can demonstrate a practice and help colleagues interpret an output. When choosing someone for that role, look for coaching and judgment alongside personal AI skill. Estimate protected time from the responsibilities involved and agree a route to specialist support. Problems requiring access, policy, or workload decisions still need the person with authority to resolve them.

Before the first teaching assignment, prepare the champion to teach one workflow, coach its checks and refer unresolved questions. Rehearse the task with a learner and work owner, then agree what support remains.

Before expanding a peer-support role, compare AI champion reward options with the actual responsibilities. Agree paid time and recognition for a bounded assignment, and review the job and pay when ongoing responsibilities grow.

For a paid adoption leader, review a proposed bonus against useful contribution, quality and control. Activity counts can prompt an investigation, while payment needs evidence of the work the leader could reasonably influence.

To keep peer support sustainable, rehearse a champion absence and agree which obligations will move or pause. Confirm that a backup can accept the work and colleagues can reach decision owners directly.

To see whether that help travels beyond the champion, follow a practice into colleagues’ checked work and later reuse.

For staff without a personal desk or office hours, test AI access, practice and support on each shift. Include the device handover and off-hours help in that check.

When allocating approved tools, make AI access criteria visible and review blocked or refused requests. Match the capability to the work, explain constraints and check whether the changed arrangement is usable.

Before comparing participation, reconcile part-time schedules, contractor coverage and leave dates in the adoption measure. Keep missing opportunity and unknown coverage visible alongside activity.

For disabled and neurodivergent employees, test an employee-chosen task through checking and handoff. Keep effective support available and give accessibility barriers a fix owner.

Make concerns answerable

Some concerns involve the meaning of using AI at work. Will asking for help look like a lack of skill? Will time saved become a higher workload? What does the organization intend to do with usage data?

A field experiment by David Almog illustrates one reason to take evaluation concerns seriously. US freelancers completing an image-categorization task relied less on AI recommendations when their reliance was visible to an evaluator who could influence a contract extension. Their task accuracy also fell. The working paper recruited 450 workers; one withdrew their data. This was a short, specific task, not a study of sustained chatbot adoption inside a company. Almog's paper, version dated August 24, 2026.

The result does not tell you what your employees believe. It gives you a reason to ask how the surrounding incentives affect an attempt.

Managers should be able to explain:

  • What good work means. Describe the output standard and the checking that remains the employee's responsibility.
  • How use will be interpreted. Clarify what usage information is collected and how it actually informs decisions.
  • What remains undecided. Name an unresolved question, its decision owner, and when an answer will be revisited.
  • How concerns reach that owner. Offer a route that does not depend on raising a sensitive question in a public demonstration.

Avoid assurances you cannot make. If the future of a role is undecided, promising that nothing will change undermines the conversation. Record the uncertainty and get the responsible leader to address it.

When an employee explicitly declines an AI task, agree a permitted work arrangement and an accountable response to the objection. Clarify the actual requirement before deciding whether support, another method or an organizational decision is needed.

When AI help goes unmentioned, distinguish disclosure concerns from unapproved use before deciding how to respond. Agree what needs to be visible for one checked handoff.

For the contribution behind AI-assisted output, make professional identity and confidence a concrete work conversation. Identify the judgment the author can explain before relying on the result.

When colleagues depend on generated documents or notes, make the handoff reliable and give correction an owner. Resolve unsupported claims and discuss repeated checking with the people sharing the work.

When a new lead takes responsibility for this support, agree what the first 90 days should leave behind. Review the lead's outputs alongside the access, approvals and staff time the company supplies.

Leave with a small action record

A good conversation should end with a change someone can make and a way to find out whether it helped. Keep the record about the work and the unresolved condition. Personal concerns do not all belong in a shared team document.

Make the next attempt useful

One task. One condition to investigate.

  1. Examine a recent attempt

    What happened during the task?

  2. Identify the condition

    What prevented useful repetition?

  3. Agree a change and owner

    Who can make it happen, and when?

  4. Review the next attempt

    Did the change help the work?

Keep, adjust or stop

Use what happened to decide whether the practice should continue, change or end.

Use the next attempt to test whether the agreed change helped. A decision to stop an unsuitable use is a valid outcome.

Copy these fields into a note:

  • Task: What recurring work are we discussing?
  • Observed obstacle: What happened in the recent attempt?
  • Change: What will be different next time?
  • Owner: Who can make that change, and by when?
  • Next attempt: When will the task recur, and what support will be available?
  • Review: What will we inspect before deciding to keep, adjust, or stop?

Choose the review point around the next meaningful repetition. A daily task and a monthly task need different observation windows. Review the employee's account alongside the finished output and the effort needed to check it.

Look for a specific change: access now works, the person can identify errors independently, or the agreed practice time actually happened. Then consider whether the finished task improved. The strategy guide's measurement section explains how to include checking and rework.

Keep what helps, adjust what remains awkward, and stop a use that cannot meet the task's needs. Share the useful learning with the next person facing the same condition.

As a practice becomes familiar, distinguish repeated AI use from a useful habit. Give preparation a recognizable work cue while retaining the checking and changed conditions that should interrupt it.

When the responsibilities are clear, design a practical AI adoption interview with consistent conditions and evidence criteria. A small supplied task helps you examine checking and coaching before comparing panel impressions.

For a learning decision, assess AI proficiency through relevant work and changed task samples. Keep access, permitted support and important checking decisions visible before choosing the next practice.

Before requiring or funding a qualification, check what an AI credential actually assesses and record the remaining gap for the role.

To design recognition, name the useful contribution and share credit without turning AI adoption into a contest. Check who can participate, how people want to be thanked and whether the programme encourages helpful work.

Before commissioning an event, plan how hackathon or promptathon work will continue afterward. Name the receiving owner, inspect the next ordinary task and decide which work should continue, merge or stop.

When choosing a use case, let workers shape what useful assistance should mean. Return any translated criteria for correction before the proposal reaches a selection decision.

Before a deployment affects employee work, prepare the discussion with unions or works councils. Bring the actual workflow, data and monitoring, responsibilities and open decisions, and establish the applicable participation process.

When automation changes someone’s tasks, support the move into suitable work. Check real opportunities and their conditions, provide supported practice, and follow the handoff beyond course completion.

To coordinate a change across departments, decide where Kotter's guidance fits your AI rollout, then give continuing practice and maintenance a supported owner.

Before inviting staff to a new tool, sequence AI launch messages around each audience’s access and next action. Prepare the people answering questions, distinguish the pilot from colleagues waiting and follow up on instructions that caused confusion.

Questions about helping people adopt AI

What is AI change management?

AI change management is the work of helping people make and sustain a useful change in how they use AI at work. It includes explaining the purpose, understanding concerns, arranging time and support, and acting on what employees learn from real tasks. The change is only useful if the resulting work meets its required standard; completing training or buying licenses does not establish that.

Begin with a recurring task and a recent attempt. Agree what needs to change, who can make that change, and what you will inspect the next time the task occurs. Use the six-field action record to turn the conversation into a practical commitment.

Why do employees resist AI adoption?

Employees may hold back from AI because they lack approved access, time to practise, the skills to check an output, or confidence that it will help their work. They may also have reasonable concerns about performance evaluation or future workload. Nonuse alone does not tell you which explanation applies, and several conditions can matter at once.

Ask the employee to walk through their last attempt, including checking and any work passed to someone else. For example, a furniture retailer's service adviser who rejects a draft containing an unconfirmed delivery date may be protecting the customer from a false promise. Inspect that problem before prescribing encouragement or more training. The obstacle and support table helps identify who can act on what you find.

Is AI training enough?

AI training can address a knowledge or skill gap, such as learning how to check a generated reply against its source records. It cannot by itself grant missing permissions, make an unsuitable output useful, or change conflicting priorities. If employees understand the tool but cannot get the information or time they need, another class leaves those conditions unresolved.

Identify the specific obstacle, assign it to someone with authority to change it, and review the next attempt after that change. The retail purchasing example shows why an earlier handoff of warehouse notes can matter more than another training session. When workload is the obstacle, use the manager's guide to making time for AI learning to agree what moves or receives support.

How can managers support AI adoption?

Managers can support AI adoption by agreeing a useful task, making practice time available within the workload, and ensuring someone can help assess the result. Explain the quality standard and how AI use will be interpreted. Give employees a way to raise concerns, and be clear about which questions remain undecided rather than making promises you cannot keep.

At the next meaningful repetition of the task, review the output, checking effort and employee's experience together. Resolve the decisions you own and take access, policy or other dependencies to the responsible person. The weekly AI adoption routine for managers provides a practical agenda and follow-up structure; the practice arrangements in this guide explain what to set up beforehand.

How do you know the support worked?

Check both whether the original obstacle changed and whether the employee can repeat the task with an acceptable result. If the problem was missing delivery notes, establish that the notes arrived in time, then inspect the resulting summary and the effort needed to check it. Resolving access or making practice possible is progress, but it does not by itself prove that AI improved the finished work.

Compare similar tasks using the same quality standard, including checking, corrections and effort passed to other people. Use the complete-task measurement guidance to avoid counting only a faster draft. Higher usage alone is insufficient evidence, and stopping a use that cannot meet the task's needs can be a sound outcome. Record whether to keep, adjust or stop at the agreed review point.

Updated

aiready

A home for your company’s AI community.

Share what works and help each other put AI into practice.

  • Real use cases

  • Practical guides

  • Company policies

  • Shared experience

Explore aiready
Explore the blog