You've introduced a change you genuinely believe will make things better. You gave the decision a lot of thought. You explained why it matters, shared the plan with everyone, and talked with managers about how they can help their teams through the transition.
But the change isn't taking hold the way you pictured. Some employees are still using the old processes. Others are slow to pick up on the new ones. Managers are telling you their teams aren't fully on board. Progress is uneven, and you're starting to wonder what else you can do.
You've put time and resources into this and, to some degree, your own credibility. You believe it's the right direction for the organization, and you need it to work. So what's getting in the way?
Sooner or later, someone calls it employee resistance. On the surface, that fits. People aren't going along with the change, after all. But that label might be hiding something important. What if employees aren't resisting the change itself, but struggling with what it takes to make the change work? Understanding that difference can help you figure out what to do next.
What Are You Calling Resistance?
When a change isn't gaining traction, it makes sense to look for an explanation, and resistance can seem like a reasonable one. Employees aren't following the new processes. They're asking questions you thought leadership had already answered. They're still using the old systems. From where leaders sit, that can look a lot like reluctance.
But behaviors don't tell you why these things are happening. An employee who keeps using the old process might simply prefer it, or they might not be sure how the new process applies to their work. They might not have time to learn it properly, or they might have run into a problem with it that no one anticipated. A manager who isn't reinforcing a new initiative might disagree with it or they might be trying to fit the new expectations into a team that's already stretched. Those are different situations, and they call for different responses.
Research on resistance to organizational change suggests that resistance isn’t always something individual employees bring to a change. Sometimes it grows out of how the change is introduced and handled in the organization. So what looks like resistance may actually be telling you something useful about what’s going on during implementation. Instead of settling on “resistance” as the explanation, it’s worth asking what people’s reactions can tell you about what’s really happening.
When you call something “resistance,” you're describing how it looks from where you're standing. You're not explaining what's behind it.
This matters because the way you explain a problem shapes how you try to solve it. If you assume people just don't want to change, you'll probably respond with more reminders, more talk about the benefits, or even pressure to comply. But if something else is making adoption hard, those efforts won't do much to fix it. And when you’ve already invested significant time and resources in an organizational change, you want your next steps to make a difference.
You Explained Why the Change Matters. But What Does It Mean for Their Work?
Leaders put a lot of effort into communicating a change. They explain why it's necessary, what it will accomplish, and how it supports the organization's goals. That matters, because people need to understand where the organization is headed. But there's another part of the conversation that's easy to overlook.
Explaining why a change is good for the organization isn't the same as understanding what it means for the people who have to carry it out.
Take an employee named Cheyenne, whose work is directly affected by the change. Leadership has introduced a new process meant to improve coordination across departments. The reasoning is sound, and leaders have explained the benefits clearly. But what does the change mean for Cheyenne's actual work?
Will she have to complete extra steps before she can finish a task? Will she have to learn a new system while keeping up with everything else she's responsible for? Will it change how she works with colleagues in other departments? Will it add delays or dependencies that weren't part of her job before?
Has anyone looked at those questions from her point of view? Has anyone asked her? Cheyenne may understand why the organization wants the change, and even agree with the goal, and still find it hard to make the new process work in practice. If leadership hasn't looked at what the change asks of employees like Cheyenne, they may read her slow adoption as reluctance when it could actually be a sign that something needs attention.
Research on how employees respond to organizational change shows that their reactions aren’t just a matter of whether they’re willing to change. How the change is handled, the environment they work in, and what they believe it will mean for them all play a part. So to understand how people are responding, you have to look past whether they simply agree with the organization’s goals and consider the change from their perspective.
This isn't only a communication problem. It's an understanding problem, too. Leaders can know exactly what they want a change to accomplish without fully understanding what they're asking people to do to make it happen.
Managers Are Expected to Make the Organizational Change Work, Too
Managers are another group whose experience deserves attention. They're usually the ones expected to turn a change into everyday work. Senior leaders set the direction and say what the organization needs to accomplish. Managers then have to figure out what that means for their teams. They might need to adjust workflows, explain new expectations, help people learn unfamiliar processes, and respond to concerns, all while keeping daily operations running through the transition. And they're doing it on top of their usual workloads and performance targets. That's a lot to ask.
So have managers been given what they need? They might understand why the change is happening without having a clear sense of how it should work in their own departments. They may be expected to support employees through difficulties they aren't really equipped to handle.
Some may have noticed problems with how the change is being implemented but aren't sure how to raise them, or whether they have the authority to adjust anything. From leadership's side, a manager who isn't reinforcing the change can look like part of the resistance. From the manager's side, they may be trying to make a new approach work without enough guidance, time, or resources.
Neither view tells the whole story. And if managers are struggling to turn the change into everyday work, their teams will probably feel it. Before assuming managers need to push harder on adoption, it might be worth finding out what they need to support it well.
The Same Change Can Create Different Challenges in Different Areas of an Organization
Part of what makes this hard is that a change rarely affects everyone the same way. A new process that simplifies work for one department might add steps for another. A new technology platform might be easy for employees who use similar systems every day and a big adjustment for those who don't. A change in how teams coordinate might make sense to senior leaders but create new responsibilities for middle managers who are already juggling competing priorities. Even within one department, people can experience the change differently depending on their roles, workloads, and responsibilities.
Still, organizations often roll out change as though everyone needs the same things: the same explanation, the same training, the same timeline, the same reminders. And sometimes that's enough. But a review of the literature on organizational change suggest that people’s different experiences and circumstances (as individuals and as members of specific teams) shape how ready they are to take on a change. So even when everyone is working toward the same goal, different teams can run into different challenges while putting the change into practice.
When adoption is uneven, those differences are worth looking into. Where is the change working well? Where is it proving difficult? What's different about the work, expectations, resources, or support in those places? Asking these questions can reveal patterns that get lost when the problem is described broadly as employee resistance. And they can help you focus your attention and resources where they'll do the most good.
You may discover that one department needs more training, another needs clearer expectations, and a third needs help resolving competing priorities. Or you may discover something you hadn't considered at all. The point is that you don't have to assume every team is facing the same obstacle—or that one organization-wide response will solve it.
Before You Offer More Support, Find Out What Support Employees Actually Need
When a change isn't going as planned, offering more support sounds like a sensible next step. But more support can mean a lot of things: more training, clearer expectations, more time to adjust, better tools, or more involvement from managers.
The hard part is knowing which of those will actually help. Research on organizational readiness for change draws a useful line between how committed people are to a change and how confident they are that they can work together to pull it off. That confidence often comes down to very practical matters: how demanding the work is, what resources people have, and what conditions they’re implementing the change in.
In other words, employees and managers can believe in a change and still struggle to make it work. If employees are struggling because the new process conflicts with their other responsibilities, another training session probably won't fix it. If managers aren't sure how to support their teams through the change, another company-wide email might not give them what they need. And if different teams are running into different problems, a single response can leave some of the biggest obstacles untouched.
You don't want to keep trying solutions and hoping one sticks. You want to make informed decisions about where to focus. That starts with understanding how the change is being experienced across your organization. The point isn't just to ask whether people support it. It's to learn what implementing it looks like in their everyday work.
What has gotten easier? What has gotten harder? Which parts of the new process are working the way they were meant to? Where are people improvising workarounds? What do managers need to better support their teams? These questions can help you move beyond general impressions of resistance and build a more specific picture of what's happening. They can also show you where the organization is already getting implementation right, and what you can learn from it.
Of course, asking questions is only the beginning. Employees' and managers' accounts need to be considered alongside everything else you know about how the change is unfolding. Different people might experience the same situation differently, and their explanations may not always align. The goal isn't to collect feedback for its own sake. It's to gather what you need to make better decisions about how to support the change you're making.
You Don't Have to Choose Between Moving Forward and Understanding What's Happening
When you've made a change because you believe it's right for the organization, you want it to succeed. And when adoption isn't going the way you planned, you need a way forward.
You don't necessarily have to revisit the decision itself. But you may need a clearer picture of what it takes for employees and managers to make the change work. Understanding their experiences can show you where expectations need clarifying, where more resources would help, or where the approach to implementation needs adjusting.
You may also find that some employees really do disagree with the change or are reluctant about it. That's worth knowing, too. The important thing is not to assume every unexpected response has the same explanation.
Before you decide how to overcome employee resistance to change, find out what employees and managers need to make the change work.
Because the question isn't only whether employees are willing to change. It's whether you understand enough to help them succeed.
When Your Change Isn't Gaining Traction, You Need to Know Why
You've already invested in an important change. If the change isn’t catching on the way you expected, another round of reminders based on a general sense that employees are resisting won't get you far. And the longer you go without understanding what's getting in the way, the more time and resources you risk spending on support that doesn't address the problems employees and managers are actually facing. Meanwhile, the longer adoption stays uneven, the longer you wait for the results you were counting on. You need to understand what's happening across your organization so you can decide where to focus your support.
Inquiry Practice helps leaders find out what’s really going on for employees as they try to adopt a change, and what in the organization is making it easier or harder. Through thoughtful inquiry and qualitative research, we help you move past assumptions and get a clearer picture of what employees and managers need. So you can make informed decisions about how to move your change forward.