How to Handle an Employee Who Refuses to Learn New Technology

How to handle an employee who refuses to learn new technology

Figuring out how to handle an employee who refuses to learn new technology starts with understanding why the resistance is happening at all. A review of 63 studies on workplace digital transformation, published in 2024, found that resistance is predominantly linked to workers' perceived job vulnerability, which may stem from a lack of the skills needed to use the tool or fear of being replaced by it (Cieslak & Valor, 2024). That's a different starting point than assuming an employee is simply being difficult.

This guide walks managers through a practical sequence for handling an employee who is resisting required technology: confirming whether the tool is actually a job requirement, diagnosing what's blocking adoption, building a training and communication plan, and recognizing when continued refusal shifts from a training gap into a documented performance issue. One thing this guide does not do is provide legal, disability-accommodation, or union-contract advice. If a situation touches any of those areas, that's a conversation for HR, legal counsel, or the organization's ADA/EEO officer, not something to work through alone.

Why an employee refuses to learn new technology

Digital tools now show up at every level of most organizations, which means employees are being asked to build new skills regardless of tenure, title, or past performance (Cieslak & Valor, 2024). That framing matters because it reclassifies a lot of what looks like defiance as, more accurately, a training or confidence gap.

Researchers describe resistance as a mix of cognitive, emotional, and behavioral responses rather than a single reaction (Cieslak & Valor, 2024). It can look like open pushback, or it can look quieter: an employee reverting to spreadsheets instead of the new system, or simply not logging in. That distinction matters later, when the goal is to document what actually happened versus what it felt like from across the room.

The same review sorted the 63 studies into three broad ways researchers have framed resistance: 38% centered on fear of job displacement, 33% framed it as a mismatch between an employee's skills and the tool's usability, and 29% focused on how the technology disrupts identity or workplace relationships (Cieslak & Valor, 2024). Those percentages describe how the research literature has categorized resistance, not the share of any one team's employees affected by each cause. Still, the three categories work well as a diagnostic checklist when trying to figure out what's actually going on with one specific person.

Step 1: Confirm the technology is an actual job requirement

Before addressing anything as a performance issue, check whether using this technology was communicated as part of the role, either in the job description, during onboarding, or in a policy the employee acknowledged. This isn't the same as determining whether the task legally qualifies as an "essential job function," a specific term with disability-law implications that HR or legal counsel is better positioned to evaluate. The job at this stage is simpler: confirm the expectation exists and that the employee knew about it.

Pull together what's already on file: training materials provided so far, dates and specifics of noncompliance, and any prior conversations about the tool. Without a clear expectation and some record of training, treating this as a performance problem is premature, no matter how frustrating the situation feels.

This is also the point to check in with HR about the organization's accommodation process, before landing in the middle of a tense conversation. If the resistance turns out to connect to a disability, medical condition, or another circumstance requiring a formal process, it helps to already know who to loop in rather than figuring it out mid-conversation.

Step 2: Hold a fact-finding conversation with the employee

Once the requirement is confirmed, talk to the employee directly, one-on-one, and lead with the specific behavior rather than a general complaint. "I noticed the last three orders were entered by hand instead of through the new system, walk me through what happened" gives the employee something concrete to respond to, instead of putting them on the defensive with something like "you're not trying."

A short list of diagnostic questions keeps the conversation focused on facts rather than assumptions:

• Which part of this task can you complete without help, and where do you get stuck?
• What happens when you try to use the system?
• Did the training you received actually cover this specific task?
• Is there anything about how this changes your day-to-day work that concerns you?

Write down the employee's answer in their own words, with the date. That record becomes the foundation for the training plan in the next step, and it's also the kind of documentation needed if the situation doesn't improve and escalation becomes necessary.

Step 3: Identify the specific barrier

Listen for which of the three research-backed patterns the employee's answer fits: concern that the tool signals reduced value or job security, a genuine skills gap that makes the tool feel unusable, or a disruption to how they work with coworkers or understand their own role (Cieslak & Valor, 2024). These aren't mutually exclusive, and an employee may not name the real issue directly, especially if it's tied to fear about job security.

When employees can't yet judge whether a tool is genuinely useful or easy to use, that uncertainty itself fuels resistance, which is why a one-time demo rarely resolves the problem the way structured, hands-on repetition does (Cieslak & Valor, 2024). If the employee's answer points to "I don't understand how to do this," that's a training problem. If it points to "I don't see why we need this" or "this makes me feel replaceable," that's a communication and trust problem, and it needs a different response than more practice sessions.

Step 4: Build a training plan with written milestones

Once the barrier is identified, write down a short training plan with specific, dated milestones rather than a vague expectation to "get up to speed." A separate study on digital transformation, published in early 2025, identified learning as one of three components organizations used successfully as part of a mitigation strategy for reducing resistance (Cieslak & Valor's peers, ITP, 2025). Structured, repeated practice does more work than a single training session.

A workable plan might look like this:

• Milestone 1, by Friday: complete two supervised practice sessions in the system with a trainer or mentor present.
• Milestone 2, by the following week: independently process one routine task in the system, with a peer mentor available if questions come up.
• Milestone 3, two weeks out: complete a full week using the system as the primary method for this task, with no reversion to the old process.

Pair the employee with a peer mentor if the team has one, and set an actual follow-up check-in date on the calendar. Leaving training open-ended makes it harder later to say clearly whether the plan worked.

Step 5: Explain the why, and ask what would help

Training alone doesn't cover the whole problem. The same 2025 study found that communication and participation, alongside learning, were core components of the mitigation strategy the research supported, and its findings, along with related literature, propose that this combined approach reduces resistance and supports employee well-being during technology changes (ITP, 2025). Nearly a third of the studies in the earlier review linked resistance to how technology affects identity and workplace relationships, which suggests employees respond better when they understand specifically why a tool was chosen for their role, not just for the company in general (Cieslak & Valor, 2024).

Explain in plain terms why this technology is required for this specific job, not as a company-wide mandate handed down from somewhere else. Then ask the employee directly what would make it easier to adopt. If they raise a legitimate usability problem, a form that won't save correctly, a workflow that duplicates steps, document it and escalate it to IT. Sometimes resistance is pointing at a real flaw in the system, not a gap in the employee's effort.

Step 6: Check progress against observable standards

Set a clear definition of what successful use of the technology actually looks like, tied to a date. "Getting better with the system" isn't measurable; "processing five client files through the system with zero manual workarounds over a two-week period" is. Vague standards make it nearly impossible to tell whether the issue is still a training problem or has moved into a performance problem.

Check in on the date set in Step 4. If the employee hit the milestones, document that and close out the training period. If they didn't, note specifically what was expected, what training and support were provided, and what actually happened, dated and factual. Something like: "Employee completed supervised training on the scheduling system Jan. 15. As of Jan. 29, continued to schedule appointments manually for three consecutive days despite the agreed milestone." That kind of record matters regardless of what happens next.

When technology resistance becomes a performance issue

If the technology is a documented job expectation and the employee has received adequate training, time, and support, continued nonuse can reasonably move toward being treated as a performance matter. Confirm that read with HR before proceeding, since how organizations classify and handle this varies by employer, industry, and internal policy. What counts as sufficient training or a reasonable timeline at one company may not match another's standards.

If informal coaching hasn't resolved the issue after the defined training period, work with an HR partner to put a formal written expectation in place, specifying the required proficiency, a timeline, and what happens if nonuse continues. This is also the moment to pause entirely if the employee discloses a disability, medical condition, or other circumstance that may explain the resistance, or raises a union or contract-related concern. Route that conversation to HR or the organization's formal accommodation process rather than continuing to handle it as a standard performance issue.

What to do next

Before the next conversation with this employee, pull the job description and any onboarding records to confirm the technology requirement was actually communicated, not assumed. Draft a short written training plan with specific milestones and dates rather than an open-ended expectation, and check with HR on the organization's documentation process now, in case the situation doesn't resolve on its own. If a medical, disability, or accommodation concern comes up at any point in the process, stop and hand that conversation to HR or the designated ADA coordinator rather than continuing to manage it as a straightforward performance issue.