In my experience, resistance to change rarely comes from unwillingness—it's usually a signal of something deeper. Beneath the surface, there are often unspoken concerns: fear of loss, uncertainty about one's place, or past experiences that haven't been fully processed. If those emotions go unacknowledged, they tend to show up as pushback or disengagement. One approach I've found consistently effective is to slow down and create space for those underlying dynamics to be seen and heard. Rather than jumping straight into strategy or persuasion, I invite individuals or teams into a deeper reflection process. I often draw on KEYS to your relationships, a method rooted in process-oriented psychology, which offers structured questions to explore emotional drivers, hidden motivations, and personal meaning. It's not about convincing—it's about understanding. This kind of process helps shift the atmosphere from tension to trust. When people feel genuinely seen, the need to resist often fades. Change starts to feel less like a threat, and more like a step toward something shared.
Change is inevitable in any organization, but successfully managing it is more art than science. I've found that resistance often stems from fear of the unknown—employees worry about how new procedures might impact their daily routines, job security, or performance metrics. One approach that's worked exceptionally well for us at Fulfill.com involves what I call "strategic transparency." When implementing our new matching algorithm for connecting eCommerce businesses with 3PLs, we anticipated pushback from our operations team who had developed their own methods over time. Instead of simply announcing the change, we created a phased rollout with integrated feedback loops. We started by involving key team members early in the development process, soliciting their expertise to improve the algorithm. We clearly communicated how the change would impact everyone's workload, the specific benefits it would bring (both to them and our clients), and most importantly—how it aligned with our mission of optimizing fulfillment operations. The game-changer was pairing each team member with someone who was enthusiastic about the change. These "change champions" provided peer support during the transition, which proved far more effective than top-down directives. We also established metrics to measure improvement, celebrating small wins along the way. When the data showed that our new process was reducing match time by 40% while improving client satisfaction scores, even the most resistant team members became advocates. In the logistics world, where efficiency drives everything, showing concrete results is essential. But the human element—acknowledging fears, involving teams early, and providing peer support—was what truly transformed resistance into enthusiasm. The lesson? Technical solutions require human-centered implementation to truly succeed.
How do you handle resistance to change? You don't. The idea that people are resistant to change has become so embedded in our thinking that it is rarely, if ever, questioned. As a result, many leaders spend too much time and energy trying to manage resistance to change. And it's not working. Resistance to change isn't a stage of the change process. It is also not a psychological state, a personality construct, nor is it inevitable. Too often, what leaders describe as resistance is a symptom - or worse - a label that's applied to an individual or group when they didn't enthusiastically respond to an announced change event. Or they question, criticize, or challenge the proposed change, or they fail to adopt the new activities and behaviours. So, if managing resistance doesn't work, what does? Building readiness with the Readiness Mindset(r). It's the only strategy to stop managing resistance when implementing any change. A lack of resistance doesn't equal readiness. Readiness requires more of the person or group. It is the willingness and ability of an individual or group to engage in the activities and behaviours needed to achieve the desired outcome. And it's readiness - not a lack of resistance - that determines whether those new activities become fully embedded, and you achieve the desired result of the change event. When your strategy is building readiness using the Readiness Mindset(r), you don't have to manage resistance because you: * ensure people are prepared, feel capable, and supported to adopt new activities and let go of current activities and behaviours * enable the time and create a plan with the activities needed to build readiness * acknowledge that as the leader who initiated the change, you started sooner, and your level of readiness will always be higher * don't misinterpret and label normal human reactions to change as resistance * ask different questions and approach change from a different perspective, reducing the fear and uncertainty that hold us back when faced with something new or different. One last caveat. Building readiness and preventing resistance doesn't mean that every person will adopt every change that is proposed. That would be foolish. But it does mean that your employees will engage with you, won't fear change and resistance to change won't exist. (c)2025 Dr. Dawn-Marie Turner. All rights reserved.
I frame change as an experiment, not a mandate. Instead of rolling out a new process top-down, I present the goal and invite feedback. I'll say, "Here's the problem we're solving. Here's a proposed solution. Let's test it for two weeks and review results together." That gets buy-in because the team feels involved and not blindsided. One time we introduced a new content workflow using ClickUp. There was initial pushback, so I asked the team to run it alongside their existing method and compare the efficiency. Once they saw how much time it saved, adoption became a no-brainer—framing it as a trial made all the difference.
To effectively I handle employee resistance to new policies through a thoughtful approach that includes clear communication, proper training, and active employee involvement. I make sure to explain the purpose and benefits of the change, which helps build understanding and reduce uncertainty. I also provide hands-on training to ensure everyone feels equipped to adapt. Inviting feedback and addressing concerns fosters a sense of inclusion and trust, which helps ease the transition and encourages cooperation. One successful approach I use is implementing a phased implementation strategy where new policies are introduced step by step. This allows employees to adjust gradually while also giving them the opportunity to provide feedback at each stage. It helps reduce resistance, minimises disruption to daily operations, and encourages greater acceptance and engagement.
Over the years running Ozzie Mowing & Gardening, I've learned that resistance to change often comes from a lack of clarity or a fear of losing control. One successful approach I've used is involving the team early in the decision making process. A few years ago, I introduced a new scheduling system to improve our efficiency and reduce miscommunication. At first, a few long time team members were hesitant. Rather than pushing it through, I sat down with them, explained why the change was needed, and asked for their feedback. I used my experience from over 700 completed projects to highlight how missed jobs or double bookings cost us time and hurt client satisfaction. By showing them real examples and encouraging input on how we could tailor the new system to work for them, they not only accepted the change but helped refine it. Being a certified horticulturist has taught me the value of adapting methods to suit the conditions, and that applies just as much to team management as it does to soil health. The transition ended up being smooth, and we actually increased our productivity by about 20 percent in the following quarter. More importantly, the team felt heard, which boosted morale and trust across the board. That approach, clear communication, real world examples, and a willingness to collaborate, has been key in making positive changes stick.
Handling resistance to change is always a delicate dance. I remember early on at spectup, when we helped a mid-sized company roll out a new investor reporting system, a lot of employees felt it was just more bureaucracy and extra work. What helped was involving them early—not just announcing the change from the top. We set up workshops where people could voice concerns and actually influence parts of the process. One of our team members shared stories from other clients who had made similar shifts, which helped ease anxieties by showing real-world benefits. Also, framing the change in terms of how it would make their day-to-day work easier, not just a box to tick, made a difference. It's about respect—showing you get the discomfort and are committed to support, not just enforcing new rules. In that case, the feedback loop we created turned skeptics into advocates, and the rollout went smoother than expected. At spectup, I always push for that balance between clear leadership and genuine employee engagement when navigating change. It's never just about the policy—it's about people adapting together.
When implementing new policies, I've found that addressing employee resistance starts with transparent communication. Early on, I experienced pushback during a major workflow change, so I scheduled open forums where team members could voice concerns and ask questions. Instead of pushing the policy top-down, I involved key employees in shaping the rollout, which helped them feel ownership. One successful approach was creating pilot groups that tested the new process and provided feedback before full implementation. This not only identified practical issues early but also turned some skeptics into advocates. By validating their input and adjusting based on real concerns, resistance decreased significantly. The key lesson I learned is that people resist what they don't understand or feel excluded from. Bringing employees into the conversation and making them part of the solution helped ease the transition and improved overall adoption.
Handling resistance to change requires understanding and empathy. When introducing new policies or procedures, I first ensure transparent communication about why the change is necessary and how it benefits both the company and the employees. One successful approach I've used is involving employees in the change process early on, asking for their input and addressing concerns before implementation. This fosters a sense of ownership and reduces pushback. For example, when we introduced a new project management tool, we conducted a series of workshops and feedback sessions where employees could share their thoughts and ask questions. We also provided training and support, ensuring that the transition was smooth. By actively listening to employees' concerns and providing clear, consistent information, we were able to gain buy-in and improve overall engagement with the new system. This approach not only minimized resistance but also helped to build trust between leadership and the team.
The best way I've handled resistance to change is by involving employees early in the process. When we rolled out a new CRM system, I didn't just announce it and expect buy-in. I invited a few team leads into the evaluation process, asked for their input, and showed them how it would make their work easier. Once they understood the benefits and felt their voice mattered, they naturally became advocates for the change. That peer support made a big difference. When the wider team saw their coworkers were already using the new system and benefiting from it, the resistance dropped fast. Change always brings friction, but if you show respect for the team's concerns and communicate clearly, you can get everyone moving in the same direction.