Stop taking resistance to change personally

Last month, I was coaching a school leader who had shared a well-researched change proposal with her team. The response was hesitation and quiet pushback. She said to me, “I don’t understand. This would have a real impact. Do they not trust my judgement?”

Here’s what I told her: this might not be about you at all.

The pattern is more common than we like to admit. You bring a thoughtful idea. You’ve done the reading. You can see the upside clearly. And the response you get is slower, cooler, more cautious than you expected.

It’s easy to read that as doubt, resistance, or a lack of trust. Often, it’s something much simpler.

The Idea: Resistance to change is often status quo bias at work. Once you understand it, you stop taking pushback personally and start responding more skilfully.

30-Second Version

• Status quo bias is our brain’s natural preference for the familiar, even when change would likely improve things.
• It’s universal. You’ll see it in your team, and if you’re honest, in yourself.
• Most resistance isn’t stubbornness or a verdict on your leadership. It’s people’s brains protecting what feels safe.
• When you understand that, you can stop defending your idea and start working with how people actually change.

The Full Read

One of the most useful things I took from studying psychology is how predictably our brains resist the unfamiliar. The current state feels safer. The familiar feels less risky. Even when change would genuinely improve things, our default is to stick with what we know. You can see it in everyday school life. Teams continue with planning approaches that no longer serve them because everyone understands how they work. Staff meeting formats that leave people drained persist because changing them feels harder than tolerating them.

When you recognise this, the pushback shifts meaning. It might not be about whether your idea is good. It might simply be that it asks people to move away from what feels comfortable. That reframe gives you empathy without backing down.

It also helps you avoid a common trap. When leaders interpret hesitation as a personal challenge, they tend to respond by pushing harder or defending the idea more strongly. That usually increases resistance rather than reducing it.

Not all resistance is status quo bias. Sometimes people are naming real risks. Sometimes the current approach genuinely is better. But even when concerns are valid, this bias shapes how strongly people hold on to what already exists.

Once you see it, you can start to work with it. Ask your team plainly: “Are we sticking with this because it’s working, or because it’s familiar?” That question alone shifts the conversation. It invites people to examine the status quo rather than instinctively defend it.

Then design the change in a way that lowers the perceived risk. Small, reversible experiments help more than big permanent shifts. Trial it with one team, gather evidence, and let people see that change doesn’t mean chaos. And frame it as building on what already works, not replacing it. When people feel their past work is being dismissed, resistance hardens. When they feel it’s being honoured, they can move forward.

The goal isn’t to eliminate status quo bias. It’s hardwired. The goal is to recognise it early, name it without blame, and help your team move past it.

Small step → This week, identify one area where you’re proposing a change to existing practice and ask your team: “Are we staying with this because it’s genuinely effective, or because it’s familiar?” If it feels right, name the bias directly.

When you encounter resistance, try the reframe: this might not be about me. Once you’re there, the real question becomes how you work with it.