Managing the Team Member Who Resists AI — The Conversation That Works

Almost every Auckland SME deploying AI has at least one team member who resists it. Sometimes they say so openly; sometimes they comply at a surface level while privately refusing to engage. The owner's response to this situation has surprising long-term consequences — both for the AI rollout and for the team member. Get the conversation wrong and you either lose a good employee or carry a passive resister who drags down adoption for others.

Here's the practical framework for handling the anti-AI team member.

First: understand which kind of resistance you have

Several different patterns get lumped together as "resistant to AI". They need different responses.

Type 1: ethical or philosophical concern. The team member has thought about AI and has principled concerns — about employment effects, environmental impact, intellectual property, or job dignity. These concerns are often legitimate and the team member is usually engaging in good faith. Worth listening to and incorporating into your approach.

Type 2: practical skepticism. The team member tried AI, found the output unreliable or the workflow disruptive, and concluded it doesn't help their work. Often the result of bad early implementation rather than bad technology. The right response is to investigate whether the concerns are correct.

Type 3: identity threat. The team member's professional identity is tied up in the work AI is changing. The senior bookkeeper who's been doing manual reconciliations for 25 years; the writer whose craft AI now imitates; the analyst whose research-heavy role is being compressed. The concern is real even if not always expressed clearly.

Type 4: fear of redundancy. The team member believes AI is going to replace them, and resistance is self-protective. Sometimes this fear is unfounded; sometimes it's rational given how the business is signalling. Worth being honest about.

Type 5: change aversion generally. The team member resists most workplace change, regardless of merit. AI is the current example; would resist anything new.

The conversation to have

Have it directly. Not in a group setting; not via email; in a one-on-one conversation initiated by the owner or manager. "I've noticed you don't seem to be using the AI tools the team has adopted, and I wanted to understand why." Open question, real listening.

Hear them out fully before responding. Type 1 and Type 2 concerns are often valuable input the business should take seriously. Type 3 and Type 4 concerns are about the team member's situation and need acknowledgement before any operational discussion. Type 5 concern is a broader pattern that needs a different conversation.

Don't try to convince in this first conversation. Listen. Understand. The convincing happens later, if at all, through evidence and experience rather than persuasion.

The response by type

Type 1 (ethical): "Tell me which specific concerns matter most to you. Some of those may be things we should be addressing in how we use AI — I want to understand whether our approach actually addresses them." Often the team member identifies legitimate weaknesses in the business's approach that need fixing.

Type 2 (practical skepticism): "Walk me through your experience. What did you try? What didn't work?" The answer often reveals implementation issues — bad prompts, wrong tool for the task, insufficient training. Fix the underlying issue and the skepticism often dissolves naturally.

Type 3 (identity threat): the longest and most important conversation. The team member's worry isn't really about AI; it's about their value and place in the business changing. Address it directly. "Your work is changing — that's true. Here's what I see as your continuing value. Here's how I see your role evolving." Honest, specific, future-oriented.

Type 4 (fear of redundancy): if the fear is unfounded, say so directly and back it with action — investment in their development, clear signals about their future role, behavioural consistency over months. If the fear is well-founded, that's a different conversation about timing, transition support, and treating the person fairly.

Type 5 (change aversion): this is a broader employment conversation that AI just happens to be the current example of. Performance management considerations may apply if the resistance is consistently affecting work performance. Handle it through your normal HR processes, not as an AI-specific issue.

What not to do

Don't pretend it isn't happening. The team member knows you've noticed; the team knows you've noticed. Avoiding the conversation makes both the resistance and your perceived weakness worse.

Don't make it about "AI is the future" rhetoric. The team member knows that line; it doesn't address their actual concerns. The conversation needs to engage with their specific situation, not generalities.

Don't punish the resistance directly. Don't restrict opportunities, don't make snide comments to others, don't let it become a recurring frustration that erodes the relationship. If the resistance is genuinely a problem, address it formally through performance management; don't let it fester.

Don't capitulate either. "Okay, you don't have to use AI" creates an inequitable workplace where the team member becomes a permanent exception. That's unfair to the rest of the team and unsustainable as AI use becomes more pervasive.

The longer arc

Most resistance fades over 6-18 months once specific concerns are addressed and the team member sees concrete benefits from AI in their work or the business. Some doesn't fade — and at some point the resistance becomes a performance issue that needs handling like any other performance issue.

The owners I see handling this well are direct, patient, and consistent. They engage with the substantive concerns honestly, support the team member through the change, and apply appropriate consequences when resistance is harming work without good reason. The owners I see struggling either avoid the conversation entirely or come on too aggressively too early.

The right answer for most situations is a long honest conversation, followed by patience, followed by clear expectations, followed by support for the team member's development. AI rollouts that handle the resistance well have better team outcomes than ones that try to push past it.

---

Anti-AI team members come in five patterns: ethical concern, practical skepticism, identity threat, fear of redundancy, general change aversion. Each needs a different conversation. Listen first, then address the specific concern. Don't pretend it isn't happening, don't punish it, don't capitulate. Most resistance fades; the persistent kind becomes a performance issue handled normally.