By Doug Thorpe
You’ve spent weeks thinking about this. Maybe months. You did the research, talked to a few trusted colleagues, sketched it out on a whiteboard at 10 PM. And when you finally bring it to the team — excited, prepared, ready — the room goes cold.
Someone clears their throat. “I’m not sure that’s going to work here.” Another person glances down at their notebook. A third starts asking questions that feel more like roadblocks than curiosity. By the time you walk out, you feel like you just tried to sell ice to penguins.
So what happened?
The easy answer is “people resist change.” But that’s not really an answer — it’s a shrug. Leaders who understand why resistance shows up can actually do something about it. The ones who just chalk it up to “that’s human nature” keep running into the same wall, over and over.
Here’s what’s actually going on.
This is probably the most overlooked reason for employee resistance to new leadership initiatives.
When you walked into that room, you were at mile ten of a marathon. You’d processed the problem, worked through the objections in your head, imagined the outcomes. The idea felt obvious to you — because you’d given it weeks of mental runway.
Your team? They just laced up their shoes.
Think about it like a movie you’ve already seen. If someone asks “was that ending surprising?” you genuinely can’t remember what it felt like not to know. You’re so far past the confusion phase that you’ve forgotten it existed. Leaders do this all the time. They present a fully-formed idea and then get frustrated when their team doesn’t immediately share their certainty.
The gap in context creates a gap in enthusiasm. It’s not resistance — it’s just a timeline mismatch. And the fix isn’t a better slide deck. It’s bringing people into the thinking before the announcement.
Here’s what nobody tells you about why teams resist change from leadership: the pushback is rarely about the idea itself.
When you propose a new system, a new process, or a new direction, you’re also implicitly sending a message: the old way wasn’t good enough. And who was doing things the old way? The people sitting in front of you.
If your new approach to customer follow-up is genuinely better, what does that say about the last two years of follow-up? If this new project management system is more efficient, what does that say about the person who built the current one?
Nobody thinks through this consciously. But the defensive posture shows up anyway, because identity is wired into our work. Accepting the new idea means writing off a piece of who they’ve been.
This is why some of your most resistant employees are often your longest-tenured ones. They have the most invested in the current way of doing things — not financially, but personally. Their expertise, their credibility, their sense of competence — all of it lives in the existing system.
Getting buy-in for new initiatives isn’t about making a better argument. It’s about helping people see that the new direction honors what they’ve built, rather than erasing it.
Psychologists have known for decades that losses feel about twice as painful as equivalent gains feel good. It’s called loss aversion, and it absolutely shows up in your conference room.
When someone on your team is evaluating a new idea, their brain is running a calculation — but it’s not a fair one. The potential benefits of your proposal are speculative. The costs are real: the learning curve, the disruption to their routine, the uncertainty of “what if this doesn’t work and I look bad for going along with it?”
That math almost always tilts toward “no” in the early stages.
Think about it like a house renovation. The builder can explain with beautiful renderings how amazing the new kitchen will be. But you still have to live through weeks of dust, no stove, and contractors showing up at 7 AM. The vision is appealing. The disruption is certain. People weigh the disruption more heavily — not because they’re irrational, but because their brain is protecting them.
The leaders who overcome this don’t dismiss it. They name it. “I know this is going to feel like more work before it feels like less. Here’s what I’m going to do to minimize that…” That kind of honesty disarms the fear before it calcifies into opposition.
There’s a principle worth tattooing on your forehead: involvement creates ownership.
When a change is done to people rather than with them, a defensive posture kicks in automatically — even if the idea is one they’d actually like. It’s not about the content of the idea. It’s about the process.
The question that’s silently running in the back of every person’s mind when a leader announces something new is: Why wasn’t I asked?
This isn’t ego. It’s a reasonable question. People who do the work every day have information that leaders often don’t. When they’re bypassed, it signals — intentionally or not — that their perspective doesn’t matter. And once someone feels dismissed, they stop evaluating your idea on the merits. They start evaluating whether to trust you.
If you want to reduce resistance to organizational change, the most practical thing you can do costs nothing: ask before you announce. Bring a few key people into the problem-solving phase, not just the rollout phase. Let their input genuinely shape the idea. You’ll get better thinking and built-in advocates when it’s time to move.
This one’s harder to hear, but it’s worth saying plainly.
Sometimes when people resist a leader’s new proposal, it’s not really about the proposal. It’s about unresolved trust issues with the leader — and the new idea just became the proxy for everything else.
Have you canceled plans without explanation? Taken credit without giving it? Said one thing and done another? Those things accumulate. And when you show up with a shiny new initiative, people aren’t just evaluating the idea — they’re evaluating you. If the trust account is low, even a genuinely good idea is going to fight headwinds.
There’s also a social dynamics layer in group settings. If a respected, influential colleague raises an eyebrow in the meeting, others read that signal and respond to it — not because they’ve thought it through, but because it’s the socially safe move. Skepticism becomes a form of tribal loyalty.
This is why the most experienced leaders do their pre-work before the group gathering. They have individual conversations. They address the quiet skeptics privately. By the time the idea hits the full group, the social current is already flowing in the right direction.
The real lesson here is that when your team pushes back on something new, it’s almost never actually about the idea. It’s a signal — about trust, about identity, about autonomy, about an information gap.
The instinct is to respond with more data, a better argument, a stronger case. But you can’t logic your way through an emotional or relational problem. Better data won’t close a trust gap. A clearer slide deck won’t make someone feel less bypassed.
Here’s the question worth sitting with: Before your next announcement, what would it look like to bring people into the thinking rather than just the decision?
Not as a formality. Not to manufacture buy-in. But because the people closest to the work usually know something you don’t — and because real collaboration is what separates a team that follows a leader from one that actually believes in what they’re building together.
The difference between those two things? That’s not a leadership strategy. That’s servant leadership in practice.
I’d Love to hear your take — what’s been your experience when you’ve introduced a new idea and hit unexpected resistance? Drop a comment below or reach out directly.
If this is a pattern you’re wrestling with on your team, it’s exactly the kind of challenge we work through in the Headway Huddle — a small group of leaders solving real problems together. And if you want to dig in one-on-one, book a free 20-minute discovery call and let’s talk.
The post Why Your Team Pushes Back on New Ideas (And It’s Not Because They Hate Change) first appeared on Servant Leadership Coaching | Practical Leadership Development | Doug Thorpe.
