Overcoming Resistance to Change in Organizations: 10 Practical Tips

Resistance to change is one of the most predictable challenges in any digital transformation. It often surfaces when there is a misalignment between the executive team’s vision and the on-the-ground reality perceived by the rest of the organization. The good news is that resistance is manageable when you approach it with structure, transparency, and the right level of stakeholder involvement. Here are ten practical tips for overcoming resistance to change during your transformation.

Understanding the Root Cause of Resistance

Before applying tactics, it is important to understand why resistance exists in the first place. In most cases, it is not because people are opposed to progress. It stems from uncertainty about how the change will affect their daily work, a lack of clarity about the vision, or a feeling that decisions are being made without their input.

In our experience, the organizations that manage resistance most effectively are those that invest time upfront to diagnose the specific sources of resistance rather than assuming a one-size-fits-all approach will work.

10 Tips for Overcoming Resistance to Change

1. Clarify the Vision

Start by engaging with the executive team to clearly understand their goals and objectives. What do they hope to achieve with the transformation? Document these goals and communicate them to the rest of the organization so that everyone understands the “why” behind the change and how it aligns with the company’s future direction. When the vision is unclear, people fill the gap with assumptions, and those assumptions are almost always negative.

2. Develop a Functional Architecture

Before evaluating specific solutions, create a functional architecture based on the organization’s requirements. This architecture should outline the essential modules and functionalities needed to achieve the desired outcomes. Think of it as a prioritized shopping list of what the organization actually needs from the new system.

This document becomes the objective benchmark against which potential solutions are evaluated, which removes personal preferences and vendor hype from the decision-making process.

3. Use the Functional Architecture as a Guide

With the functional architecture in place, use it to facilitate objective comparisons of different systems. This ensures that any technology under consideration is evaluated against documented business requirements rather than marketing materials. When employees see that decisions are grounded in a structured, transparent process, they are more likely to trust the outcome.

4. Involve Key Stakeholders Early

Engage key stakeholders from various departments in the creation of the functional architecture and the evaluation process. Their input ensures that the architecture reflects the real needs and concerns of the organization, not just the executive perspective.

Involving stakeholders early also fosters ownership and buy-in. People who feel they had a voice in shaping the direction are far more likely to support the change and advocate for it within their teams. When we advise clients on building their organizational change management strategy, stakeholder involvement from the start is always the first recommendation.

5. Evaluate Solutions Collaboratively

Form cross-functional evaluation teams to assess how well each potential system aligns with the functional architecture. This creates a shared understanding and consensus on the best-fit solution rather than a top-down mandate.

Ensure that the decision-making process is transparent. Document the evaluation criteria and share the findings with the organization. Transparency builds trust and credibility, both of which are essential for reducing resistance.

6. Communicate Clearly and Frequently

Transparency is key throughout the transformation. Regularly update the organization on progress, the reasons behind decisions, and the expected benefits. Clear, consistent communication alleviates fear and builds trust.

Communication must also be two-way. Create channels where employees can voice concerns, ask questions, and receive honest answers. In our experience, organizations that rely on one-way communication (emails, town halls with no Q&A) consistently underestimate the level of resistance building beneath the surface.

7. Provide Training and Support

Resistance often stems from fear of the unknown or a lack of confidence in handling new technology. Comprehensive, role-specific training is essential, but timing matters. Training delivered too far in advance of go-live is often forgotten by the time employees need to use the system.

When we advise clients on this, we recommend a just-in-time training approach: build foundational awareness early, but deliver hands-on, role-specific training as close to go-live as possible. Ongoing support through help desks, user guides, and regular Q&A sessions should continue well after the transition.

8. Run Pilot Programs

Implement pilot programs to test the new system in a controlled environment before a full rollout. Pilots provide real-world feedback, allow for adjustments, and give early adopters a chance to become advocates for the change.

Use feedback from the pilot to make iterative improvements. Demonstrating responsiveness to employee input builds confidence in the process and reduces resistance when it is time for broader deployment.

9. Address Concerns Directly

Do not wait for resistance to escalate. Create forums, whether town halls, surveys, or one-on-one discussions, where employees can raise concerns and receive direct, honest responses. Showing that you value their input and are willing to act on it significantly reduces resistance.

Develop actionable solutions to the concerns raised and communicate what you are doing about them. Follow-through is what builds credibility. Acknowledging concerns without acting on them makes resistance worse, not better.

10. Celebrate Small Wins

Acknowledge and celebrate progress throughout the implementation. Small wins build momentum and demonstrate that the transformation is delivering results. Share success stories from early adopters to show tangible benefits, not just theoretical ones.

Visible progress is one of the most effective tools for converting skeptics. When people see their peers succeeding with the new system, it shifts the conversation from fear to curiosity.

Bringing It All Together

Navigating resistance to change requires a structured approach that aligns the executive vision with the practical realities of the organization. By developing a clear functional architecture, involving stakeholders early, maintaining transparent communication, and supporting employees through the transition, organizations can overcome resistance and position their transformation for success.

The goal is not to eliminate resistance entirely. That is unrealistic. The goal is to anticipate it, design for it, and manage it so that it does not derail your digital transformation initiative. Getting these foundations right during Phase 0 planning makes everything that follows significantly easier.

Questions We Hear Most

What Is the Difference Between Change Resistance and Poor Change Management?

Resistance is a natural human response to disruption. Poor change management is a failure to anticipate, plan for, and address that response. The two are related but distinct. Resistance will always exist to some degree, even in well-managed transformations. The difference is whether the organization has the structures in place to channel that resistance productively.

Organizations with strong change management programs experience resistance too, but they identify it earlier, address it faster, and prevent it from becoming a project-level risk.

How Do You Get Executive Buy-In for Change Management?

The most effective approach is to frame change management in terms executives already care about: risk, cost, and timeline. Show them the data on how transformations without structured change management are significantly more likely to exceed budget, miss deadlines, and fail to deliver expected ROI.

In our experience, connecting change management to specific business outcomes (adoption rates, cycle time improvements, error reduction) is far more persuasive than framing it as a “people initiative.” Executives respond to measurable impact.

How Early Should Change Management Start in a Transformation?

As early as possible, ideally during the planning phase before a system integrator is even selected. The decisions made in ERP selection and implementation planning directly affect the scope and intensity of the change your people will need to absorb. Waiting until the design or build phase to start change management means you are already behind.

If you are preparing for a transformation and want guidance on building a change management strategy that starts at the right time, contact us at eric.kimberling@thirdstage-consulting.com.