AI Playbook 2 of 5

How to Diagnose and Address AI Adoption Resistance

AI resistance is not one problem. Someone who fears being replaced needs a different response than someone who tried a tool once, got bad results, and wrote it off. This playbook gives you concrete methods for diagnosing which resistance pattern is operating in each team member and applying the intervention that actually addresses their specific concern.

This playbook covers the how. For the why and what, see the skill definition .
Developing Start here. Build the foundation.
  • Schedule a brief one-on-one conversation with each team member focused on their AI experience. Ask three questions: What AI tools have you tried? What has not worked well? What concerns do you have about AI in our work? Listen for the underlying pattern. Fear of replacement sounds like worrying about what happens when AI can do their job. Identity threat sounds like believing their expertise makes AI unnecessary. Skills deficit sounds like not knowing where to start. Dismissal sounds like having tried it once and found it useless. Document what you learn in a private note so you can track patterns over time.
  • For anyone who says they tried AI and it did not work, schedule a 30-minute co-working session. Sit with them, pick a task they do regularly, and work through it together using an AI tool. Let them drive while you guide. The goal is not to show them how the tool works but to help them experience genuine value on their own work. One successful hands-on session converts more dismissers than ten demonstrations.
Proficient Build consistency and rhythm.
  • Have a direct, specific conversation with your team about how AI will change roles. Replace vague reassurances like 'Your jobs are safe' with concrete statements: name the two or three tasks that will change, explain how responsibilities will evolve, and be honest about what you do not yet know. People can handle uncertainty far better than they can handle feeling lied to. Write down the key points and share them so the team can reference the commitments you made.
  • When you discover employees using unapproved AI tools, resist the urge to shut them down immediately. Instead, investigate what need the unapproved tool meets that your official tools do not. Ask: What were you trying to accomplish? Why did you choose this tool over the approved options? What would need to change for you to get the same value from our supported tools? Shadow AI usage is a demand signal, and cracking down without understanding the underlying need pushes the behavior underground rather than solving it.
  • Create a simple resistance map for your team: list each person, the resistance pattern you have diagnosed, the intervention you have applied, and the result. Review this monthly. Some patterns shift over time, especially as fear decreases with exposure and as poor early experiences get overwritten by guided successes. Update your approach when the pattern changes.
Mastered Operate at the highest level.
  • Build differentiated intervention plans for each resistance profile. For fear-based resistance, pair the person with a colleague who has successfully integrated AI into similar work and have them co-work on a real task. For identity-based rejection, frame AI as amplifying the expertise they are proud of rather than replacing it, and show them examples from peers at their level who use AI to do higher-quality work. For skills-based inability, provide structured learning with progressively challenging tasks rather than general training.
  • Track resistance pattern shifts across the team over time. After three months of targeted interventions, map how many people have moved from resistant to experimenting, from experimenting to consistent use, and from consistent use to advocating. If certain patterns are not shifting, it usually means the intervention is mismatched, not that the person is impossible to move. Reassess your diagnosis before concluding that someone cannot be reached.
  • Coach other managers in your organization on resistance diagnosis techniques. Most managers default to offering more training because they do not have a framework for distinguishing between resistance patterns. Share your resistance map template and walk them through the five patterns with examples from your experience. Scaling this diagnostic capability multiplies adoption impact beyond your own team.
Back to AI Adoption Playbook

Unlock Skill Progression

Coaching Personalized to your current level
Progress Tracking Across every skill area
Mastery Validation Evidence-based, not guesswork