If your team is pushing back on AI rollout, you have two options: dismiss it as resistance to change, or treat it as feedback worth understanding. The first approach kills rollouts. The second often reveals legitimate concerns that, addressed, accelerate adoption.
Resistance usually means one of: (1) people fear job loss, (2) the tools aren't actually useful for their work yet, (3) leadership is pushing without modeling, (4) people don't have time to learn, or (5) past tech rollouts at your company have failed. Diagnose first; intervene specific.
Before responding to resistance, find out what it actually is. Five common patterns, each with different fixes:
Talk to 5 resistors privately. Ask: "what's making this hard?" Listen for which of the above patterns shows up.
What works: Be explicit, in writing, about what AI is and is not meant to do. "We're rolling out AI to make our existing team more productive, not to reduce headcount in the next 12 months. We expect to grow output per person without growing headcount as fast as we otherwise would have."
What doesn't work: Vague reassurances. Promises you can't keep. Silence.
What works: Take this seriously. Some workflows really aren't AI-ready yet. Park them. Pick a different workflow that does benefit. Don't force AI into workflows where it adds friction.
What doesn't work: Insisting they keep trying. People know when a tool is fighting them.
What works: Leadership personally uses the tools, visibly, in front of the team. CEO posts about a Claude workflow they ran this week. CEO uses AI in a meeting in front of others.
What doesn't work: Sponsoring the initiative without personally adopting the tool. Team always reads the signal.
What works: Protect calendar time explicitly. "For the next 2 weeks, every Tuesday/Thursday 9-10 AM is reserved for AI training and practice. No meetings." Sometimes this is the entire blocker.
What doesn't work: "Find time around your existing work." People don't have any.
What works: Address it explicitly. "I know we've started initiatives that fizzled before. Here's why this is different: [specific commitments]." Then ship something visible quickly so the pattern breaks.
What doesn't work: Pretending the past doesn't exist. People remember; their disengagement is rational based on past evidence.
Sometimes the resistance is right. Workflows where AI genuinely adds friction; cultures where the tool isn't ready; teams where the timing is wrong.
If three or more of your respected operators (not the chronic complainers) push back on a specific workflow, take it seriously. Pause it. Find a better first workflow. Their judgment is usually correct.
Rarely productive. Mandates produce surface compliance, not adoption. Invest in modeling and removing friction.
Have the direct conversation. "Using AI fluently is now a baseline skill for your role. What support do you need?" Make it a development conversation, not a discipline conversation.
Usually not. Resistance hardens with neglect. Address it specifically.
Sometimes — an outside facilitator can move conversations that internal politics blocks.
If diagnosed correctly and addressed specifically, 30-60 days. If misdiagnosed or ignored, never.