People don't hate change. They hate being changed.
The difference is ownership. When people get to contribute before the change lands, they enter the process instead of being subjected to it. Not everyone can decide — but everyone can be heard, and those are not the same thing.
What is resistance actually telling you?
That someone is missing influence, not information.
We tend to treat resistance as a communication problem: they haven't understood it yet, send the deck again. Usually they've understood it perfectly. What they haven't had is any point at which their view could have changed the outcome.
So don't speak dismissively about the people who react to change. Ask a better question instead: did they get a chance to have an opinion about it?
If the honest answer is no, the resistance isn't irrational. It's accurate.
The work happens before the workshop
This is the part that gets skipped, and it matters more than anything you do on the day.
Interview six to ten people first. Not a survey. Fifteen-minute conversations, across levels, including the people you expect to push back hardest. Especially those.
Four questions that do most of the work:
- What's working today that we would be stupid to lose?
- What's the part of this you think leadership hasn't understood?
- What would have to be true for this to work in your team?
- What's your honest prediction for how this goes?
That last question surfaces more than the other three combined. People will tell you the failure mode if you ask them to predict rather than to evaluate.
Then feed it back. Open the workshop with what you heard — anonymised, unedited, including the uncomfortable parts. Two things happen. The people you interviewed see their words in the room, so the process is visibly real. And everyone else learns that saying the difficult thing is safe here, because it just happened on a slide.
Be explicit about the decision space. Say what is genuinely open and what is already decided. A workshop that pretends everything is negotiable, when three things aren't, burns more trust than one that names the constraint honestly on the first slide.
Three exercises for the day
1. Keep, lose, invent
Three columns. Groups fill all three about the current way of working, then prioritise to one item per column.
Starting with "keep" is the point. It signals that change isn't a verdict on everything they've built, which lowers the defensiveness enough that "lose" becomes honest.
2. Pre-mortem
Move the group twelve months forward: the change has failed. Not "might fail" — has failed. Ask each group to write the story of how.
The framing does the work. "What are the risks?" gets you a cautious list. "It failed, tell me why" gets you what people actually believe, because they're describing rather than criticising. The strongest objections in the room arrive as analysis instead of resistance.
3. What does this mean for us on Monday?
Teams work in their real team, not mixed groups, and answer three questions: what changes for us, what do we need from others, what will we decide ourselves?
This is where ownership either forms or doesn't. It also converts a general change into specific work, which is the only form anyone can actually act on.
The measure
At the end, you're not looking for agreement. You're looking for people who can explain the change in their own words — including the parts they still don't like.
That's what ownership looks like. It isn't enthusiasm.