Nobody in your organisation stood up and said no.
There was the slight eye-roll in the all-hands when the slide came up. The colleague who said "yeah, I'll have a look at it" in March and has not. The licences assigned in week one and unopened in week twelve. The pilot that ran, produced a nice readout and quietly stopped.
If you are leading AI in the workplace right now you recognise all four, and none of them gave you anything to respond to.
Resistance is the normal condition of leading change, however good the plan is. The question is whether you have the right tool for the type in front of you, because the strategy that moves one type makes another worse.
Start by assuming good intent
There is almost always a real reason underneath: fear of loss, a different set of priorities, incomplete information, or simply being at capacity.
That assumption is not politeness. It is the thing that keeps the conversation open long enough for you to find out which one you are dealing with. Push before you know, and people do not stop protecting what they are protecting. They stop telling you about it, and you lose the only signal you had.
What the resistance is actually protecting
Competence and standing. Someone who has been the person who knows how to do this for twenty years is being asked to be a beginner in front of people who look up to them. The tool does not threaten their job. It threatens the thing they are known for, and their expertise, their relationships and their proven process are all bound up in the current way of working. That is a much larger ask than the training deck acknowledged.
Being watched. Every prompt is logged somewhere and people know it. Nobody has told them what is stored, who can read it, or whether low usage will appear on a slide about their team. In the absence of an answer, they assume the answer they can least afford.
Their future. The quiet one. If the tool can do it, what am I still here for? Leaders rarely name it because naming it feels like conceding it. So it stays unspoken, and unspoken fears do not decay. They stop showing up as questions and start showing up as calendar conflicts.
Their capacity. The most legitimate and the most ignored. The tool costs time before it saves time: learning it, checking its output, redoing what it got wrong. Someone already at capacity is being asked to spend hours they do not have against a promise of hours later. Declining that is arithmetic, not obstruction.
Why more mandates and more training do not move it
Both instruments treat the barrier as a knowledge gap. None of those four people has a knowledge gap. The manager protecting her standing understands exactly how the tool works, which is precisely why she is careful. The analyst at capacity understood the value the first time.
Mandates make it worse in a specific way. When a decision feels imposed rather than chosen, resistance becomes the way people reassert some control over their own week.
What to try instead
Work through these and mark what you have already attempted. Most leaders have tried two of them and concluded there was nothing left.
Stop being the messenger. Find someone they respect who was also once a skeptic, and let that person make the case. A peer who converted, and can speak to what surprised them, is worth more than anything you present directly.
Restore a sense of choice. Offer different entry points, different timescales, different ways of showing progress. The goal is not to weaken the ask. It is to make the path feel navigable rather than prescribed.
Lead with relief for the ones at capacity. Show how this removes something they are already carrying rather than adding to it. Then take something off their plate for a fortnight. If you cannot, you have answered the question about how much this matters.
Bring the loudest critic inside. Invite them to evaluate rather than comply. Give the most doubtful person a real task where being wrong costs nothing and ask them to report back on where it failed. Their persistence was always a signal of engagement.
Say the job question out loud, first. "People are wondering whether this eventually replaces roles. Here is what I actually know and here is what I do not." Honesty about uncertainty buys more trust than reassurance you cannot back.
Make a smaller ask. If the whole-team mandate got a firm no, follow it with one team, one workflow, one fortnight. Each small yes makes the next one easier.
Resistance is information
Every no is telling you the exact thing standing between you and adoption. The person arguing with you in the meeting is handing you a diagnosis for free. The team that looks compliant and changes nothing is the one to worry about.
More training will not move someone who is protecting something. Finding out what they are protecting will.
One question to sit with
Think about the person you have been stuck on since spring.
Which of the four are they protecting? And who do they need to hear this from, if it is not you?