The default response to resistance
When AI adoption meets resistance, the typical organizational response is to push harder on the same levers: more communication about the benefits, more visible leadership support, more training to address the skills gap, more emphasis on the why. Sometimes this works. More often it doesn't, because it treats all resistance as the same problem, and resistance almost never is.
Six different things resistance is telling you
In my experience, when people resist AI adoption they're usually signaling one of six things: they don't trust the outputs the system produces; they're worried about what adoption means for their role; they don't have the skills to use the technology in their actual day-to-day work; they can't see how it fits their workflow; they don't trust the people making decisions about how it will be used; or the rules around acceptable use feel unclear and unsafe. Each of these calls for a different response. Treating all six as a single problem called 'resistance' is why so many change management efforts produce survey improvements and no actual behavior change.
The diagnostic question that changes the conversation
For each source of resistance, the more useful question is what this is telling you about where your transformation design has gaps. Trust in system outputs points to missing explainability and validation protocols. Role anxiety usually means the augmentation story hasn't been made concrete enough for people to believe it. Skills gaps tell you the fluency program is missing the people who most need it. Poor workflow fit means the implementation team didn't spend enough time with actual users before deploying. Weak decision trust traces back to leadership behavior that hasn't been consistent enough to earn it. Safety concerns call for real attention to psychological safety, not a policy document.
What it takes to read resistance well
The leaders who do this well are the ones who can sit with resistance long enough to be curious about it rather than threatened by it. That's genuinely hard. Resistance usually surfaces at the worst possible moment, when timelines are slipping and the board is asking questions. The instinct is to push through it. The better move is to pause, diagnose it, and respond to what it's actually telling you. The transformations that hold over time are almost always ones where the leadership team treated resistance as information rather than as an obstacle.