You're facing pushback on introducing new processes. How will you navigate resistance to change effectively?
Confronting pushback on change? Here's how to ease the transition:
How do you tackle resistance when implementing change?
You're facing pushback on introducing new processes. How will you navigate resistance to change effectively?
Confronting pushback on change? Here's how to ease the transition:
How do you tackle resistance when implementing change?
-
Change is hard, and it’s often met with fear of the unknown. 1. Make sure they understand the "why" behind the change 2. Invite your team's feedback 3. Involve them in the change process 4. and show tangible results to build trust in the process
-
"Turn Resistance Into Resilience!" Pushback is a sign that people need clarity, not control. Start by listening to their concerns and showing how the new process benefits them. Involve the team in the transition by gathering feedback and addressing fears. Break changes into manageable steps and celebrate small wins along the way. When people feel heard and see progress, resistance transforms into ownership. Change isn’t forced—it’s embraced when trust and understanding lead the way.
-
To navigate resistance to change, start by listening to team concerns to understand their perspectives. Clearly communicate the benefits of the new processes and how they align with team goals. Involve key stakeholders in planning and decision-making to foster ownership. Provide training and resources to ease the transition, addressing specific challenges. Celebrate small wins to build momentum, and remain flexible, adjusting plans based on feedback. Building trust and demonstrating value will encourage collaboration and reduce resistance over time.
-
Navigating resistance to change starts with understanding the concerns of those impacted. Openly communicate the benefits of the new processes and how they align with team or organizational goals. Involve key stakeholders early, allowing them to contribute their ideas and address potential challenges. Provide training and support to ease the transition and highlight early successes to build momentum.
-
Help your team understand the purpose and value of the changes, "The WHY." Link it to their Goals: Explain how the new processes, like improving efficiency, support them and organizational success. Show Benefits: Highlight how the changes reduce pain points or create opportunities for them and the team, making them more relevant and appealing. Use Real Examples: Share success stories or data from similar situations to build confidence and trust.
-
Break the process into manageable phases to reduce overwhelm. Show small wins to build confidence in the change Have one-on-one discussions with key resistors to understand and mitigate their concerns. Reinforce accountability while showing flexibility when justified.
-
What most people get wrong is that you need to have some level of pushback. You dont want everyone to say "OK" right from the start. If your team goes with "OK" they dont care enough about the new processes, which is an indicator of low motivation to commit to it longterm. You want small resistance at the beginning, and then you turn it into positive energy. And you know what to do: 1) Explain your motivation and the objective of the new process. Why is it needed? How does your team or customers benefit from it. --> If your team still doesnt buy, you should evaluate again if the process is really needed. 2) Once people understand the fundamental why, continue by involving them into the creation process. 3) And create some kind of learning
-
- Clearly explain the benefits of the change, linking it to team goals and individual advantages. - Seek input during the planning phase to ensure buy-in and address concerns early. - Pilot the process with a subset of the team to demonstrate its value before scaling. - Offer resources and hands-on guidance to build confidence in using the new process. - Highlight early successes to showcase tangible improvements and build momentum. - Be open to feedback and adapt the process to suit the team’s needs better. Empathy and collaboration turn resistance into an opportunity for growth and innovation.
-
When there’s pushback on new processes, it helps to first listen and understand where the resistance is coming from. People want to feel heard. Once you know their concerns, explain the bigger picture—how the changes will make things better for the team. Involve them in the process, offer support, and make the transition feel manageable. This way, you’re working with them, not against them.
-
Never be surprised by resistance—expect it. Pushback is a natural part of change. Look forward to it as a sign that people care enough to engage. Start by focusing on why we can’t stay here. Dive deep into understanding the consequences of not changing. Only once that’s clear should you begin exploring what “there” could look like.
Rate this article
More relevant reading
-
Value Stream MappingHow do you handle resistance and conflict in your value stream and how do you overcome them?
-
Servant LeadershipWhat are some decision-making strategies for high-pressure situations?
-
Creative Problem SolvingHow would you address conflicting feedback from different stakeholder groups in problem-solving processes?
-
Servant LeadershipHow can you involve stakeholders in decision-making as a Servant Leader?