Resistance To Change: How To Turn Resistance Into Participation

Resistance to change is one of the most misunderstood signals in transformation.

When people resist change, leaders often interpret it as negativity, fear, politics, stubbornness, or lack of commitment. Sometimes that may be partly true. But more often, resistance is not simply a people problem. It is information.

Resistance tells leaders that something in the transformation has not yet been understood, trusted, accepted, designed well enough, or made practical enough for adoption.

That does not mean every objection is valid. It does not mean leaders should wait until everyone is comfortable before moving forward. Transformation always involves uncertainty, trade-offs and discomfort. But resistance should not be dismissed too quickly. It should be diagnosed.

The best transformation leaders do not ask, “How do we remove resistance?”

They ask, “What is this resistance telling us, and how can we turn it into participation?”

This shift matters because adoption is not created through announcements alone. People adopt change when they understand the purpose, trust the direction, can see how the new way will work, believe their concerns have been heard, and feel that they have some role in shaping the outcome.

In AI-enabled transformation, this becomes even more important. AI does not only introduce new tools. It changes workflows, decisions, trust, accountability, risk, skills and sometimes professional identity. If people resist AI, they may not be rejecting innovation. They may be raising important questions about reliability, governance, workload, data quality, customer impact, or what the technology means for their role.

Handled poorly, resistance becomes a blocker.

Handled well, resistance becomes a design input, a risk signal and a pathway to better adoption.

Resistance Is Often Resistance To Loss

Many people do not resist change simply because they dislike the future. They resist because they are being asked to let go of something that currently gives them confidence, control, competence or identity.

That loss may be practical.

A familiar process is being replaced.

A trusted spreadsheet is being removed.

A decision right is being centralised.

A manual workaround is no longer allowed.

A system that people know well is being replaced by one they do not yet understand.

The loss may also be emotional.

People may lose status, certainty, autonomy, influence, relationships, expertise, or a sense of being good at their job. They may worry that the new way exposes skills gaps. They may fear being judged for not adapting quickly enough. They may remember previous transformation programs that created extra work but failed to deliver promised benefits.

This is why resistance often appears irrational from the outside but rational from the inside.

From a leadership perspective, the change may be logical. It may reduce cost, improve customer experience, strengthen compliance, or increase productivity.

From an employee perspective, the same change may feel like disruption, risk, loss of control, or another initiative that adds complexity to already busy work.

Both perspectives can be true.

The leadership challenge is not to avoid loss altogether. Most meaningful transformation involves some form of loss. The challenge is to acknowledge what people are being asked to let go of and help them move through the transition with clarity, support and participation.

Do Not Confuse Compliance With Commitment

One of the risks in transformation is that people may appear to accept the change while quietly continuing with old behaviours.

They attend the training.

They nod in the meeting.

They say they understand.

They use the new system when being observed.

But under pressure, they return to the old process.

This is not always deliberate resistance. Often, it is a sign that the new way has not yet become easier, safer, more useful or more reinforced than the old way.

Compliance is not the same as commitment.

Compliance means people follow the change because they have been told to.

Commitment means people understand the change, believe it is worth doing, know how to apply it, and are willing to make it work even when the transition is uncomfortable.

Participation sits between compliance and commitment. It is where people stop being passive recipients of change and start helping shape, test, improve and embed it.

The goal is not to turn every stakeholder into an enthusiastic champion. That is unrealistic. The goal is to move people from passive resistance or surface-level compliance into meaningful participation.

That is where adoption becomes possible.

Start With Stakeholder Mapping, Not Broadcast Communication

Many organisations respond to resistance with more communication.

More emails.

More town halls.

Diagnose The Source Of Resistance

Not all resistance is the same.

A stakeholder may resist because they do not understand the purpose of the change.

Another may understand the purpose but disagree with the design.

Another may support the idea but lack confidence in execution.

Another may believe the change is necessary but fear the impact on their team.

Another may be protecting customers from a poorly tested process.

Another may be defending a legacy way of working because it gives them influence.

Each type of resistance requires a different response.

If the issue is lack of awareness, leaders need to explain the reason for change more clearly.

If the issue is lack of desire, leaders need to address value, relevance, trust and perceived loss.

If the issue is lack of knowledge, leaders need to provide practical guidance.

If the issue is lack of ability, leaders need to provide coaching, practice, tools and time.

If the issue is lack of reinforcement, leaders need to adjust measures, management routines, incentives and governance.

This is why treating resistance as a single problem is ineffective.

The better approach is to ask:

What type of resistance are we seeing?

What is causing it?

What would need to be true for this group to participate constructively?

What can we learn from their concerns?

When leaders diagnose resistance properly, they can respond with precision rather than pressure.

Turn Sceptics Into Risk Advisors

Sceptics are often treated as difficult stakeholders.

But sceptics can be extremely valuable if leaders engage them properly.

Sceptics often see risks that enthusiastic sponsors overlook. They may understand operational constraints, customer sensitivities, process exceptions, data problems, informal workarounds or historical failures. They may know why a similar initiative failed before. They may understand what will happen when the new process meets real-world pressure.

Instead of trying to convert sceptics immediately, leaders can invite them to play a more useful role.

Ask them:

What could go wrong?

Where will this process break?

What are we underestimating?

What would make this difficult for your team?

What customer or operational risks should we test early?

What evidence would increase your confidence?

This does not mean giving sceptics veto power. It means using their concerns to improve the transformation design.

In AI transformation, this is particularly valuable. A sceptical frontline manager may point out that the AI model will struggle with messy customer enquiries. A compliance stakeholder may highlight missing audit controls. A subject matter expert may identify cases where human judgement must remain central. A data owner may warn that the available data is inconsistent or incomplete.

These concerns are not obstacles to progress. They are signals that can prevent failure later.

When sceptics are invited to contribute as risk advisors, they are more likely to move from opposition to participation. They may not become champions, but they can become constructive contributors.

Turn Frontline Teams Into Process Testers

Frontline teams often experience transformation after many decisions have already been made.

By the time they see the new system, workflow, policy or AI tool, leaders may already be committed to the design. This creates a common adoption problem: the people who understand the work best are engaged too late.

Frontline employees know where processes break. They know which exceptions occur most often. They know which customer scenarios are not captured in the standard workflow. They know which fields are confusing, which handoffs create delays, which approvals are unrealistic and which workarounds keep the operation running.

If they are only treated as end users, the organisation misses their expertise.

A better approach is to involve frontline teams as process testers.

Ask them to test the future workflow against real scenarios.

Ask them to identify exceptions.

Ask them to compare the designed process with actual work.

Ask them to test AI outputs for relevance, accuracy and usability.

Ask them to explain what would make the new way easier or harder to adopt.

This turns participation into practical design work.

For example, if an organisation is introducing an AI agent to classify enquiries and route cases, frontline teams can test whether the categories match real customer language. They can identify ambiguous cases. They can validate escalation paths. They can show where human review is needed. They can help define what should happen when the AI is uncertain.

This improves the solution and increases ownership.

People are more likely to adopt a change they helped make workable.

Turn Middle Managers Into Translators

Middle managers are one of the most important groups in transformation.

They are also one of the most underestimated.

Executives may set the direction. Project teams may deliver the solution. But middle managers often determine whether the change becomes real in daily work.

They translate strategy into local priorities. They answer team questions. They decide how much attention the change receives. They manage workload pressure. They model whether the new way matters. They either reinforce the change or quietly allow old behaviours to continue.

If middle managers are not engaged, transformation can fail even when executive sponsorship is strong.

This is because employees often look to their direct manager for the real signal.

Is this change serious?

Will it last?

Is it safe to spend time learning it?

Will I be supported if I make mistakes?

Will performance expectations change?

Are we still allowed to use the old process?

If managers are uncertain, overloaded, unconvinced or poorly equipped, their teams will sense it.

To turn resistance into participation, leaders must treat middle managers as change translators, not just communication channels.

They need to understand the purpose of the change.

They need to know what it means for their teams.

They need practical talking points and decision guidance.

They need to know how to handle objections.

They need time to prepare before their teams are expected to change.

They need permission to raise concerns early.

They need to be measured and supported in reinforcing adoption.

Middle managers do not just pass messages down. They interpret the change. If they are not equipped to interpret it well, the transformation message fragments across the organisation.

Turn Supporters Into Change Champions

Change champions can help convert central strategy into local adoption.

But the role needs to be designed carefully.

A champion is not simply someone who is positive about the change. A champion is someone who has credibility with peers, understands the local context, can provide feedback, can support others, and can help the organisation learn during implementation.

Good champions perform several roles.

They explain the change in local language.

They surface concerns early.

They demonstrate new behaviours.

They help colleagues build confidence.

They provide feedback to the project team.

They identify adoption barriers.

They reinforce practical usage after go-live.

The best champions are not always the most senior people. They are often trusted peers who understand both the formal process and the informal reality of work.

In AI transformation, champions can be especially powerful. They can demonstrate practical use cases, show how to use AI responsibly, share prompts or workflow tips, explain governance rules, and help colleagues distinguish between appropriate and inappropriate AI use.

However, champions should not be used as unpaid project resources without support. They need role clarity, time, recognition, information, access to decision-makers and a clear feedback loop.

If the champion network is designed well, it becomes a bridge between transformation strategy and everyday adoption.

Participation Requires Psychological Safety

People are unlikely to participate honestly if they believe their concerns will be punished, dismissed or labelled as negativity.

This is why psychological safety matters in transformation.

Teams need space to say:

I do not understand this.

I am worried about the impact.

The process does not work in this scenario.

The data is not reliable.

The customer experience may suffer.

We do not have the capability yet.

This will create unintended consequences.

These statements can feel uncomfortable for leaders, especially when timelines are tight. But they are often exactly the signals needed to improve the change.

If people cannot raise concerns safely, they will raise them indirectly. They may disengage, delay, work around the system, comply superficially, or wait for the initiative to lose momentum.

Participation requires more than inviting feedback. Leaders must show that feedback changes something.

That does not mean accepting every request. It means closing the loop.

We heard this concern.

Here is what we are changing.

Here is what we are not changing, and why.

Here is how we will manage the risk.

Here is what we will test next.

When people see that their input is taken seriously, they are more likely to stay engaged even when they do not get everything they want.

Participation Must Be Designed Into The Change Process

Participation does not happen by accident.

It needs to be designed into the transformation process.

Leaders can create participation through:

stakeholder interviews
listening sessions
process walkthroughs
pilot groups
design workshops
risk reviews
user testing
champion networks
manager enablement sessions
after-action reviews
adoption dashboards
feedback loops after go-live

The key is to involve people at the right time for the right purpose.

Not everyone needs to co-design every decision. That would slow transformation and create confusion. But the right stakeholders should be involved where their insight improves adoption, risk management or operational fit.

Participation should be structured, not random.

For example, an AI transformation might use:

executives to define purpose, value and sponsorship
process owners to redesign workflow and decision rights
frontline users to test usability and exceptions
risk teams to define controls and audit requirements
data owners to assess data readiness
middle managers to translate adoption expectations
champions to support local usage
customers or client-facing teams to validate experience impacts

This turns participation into a disciplined transformation capability.

The Leadership Balance: Listen, Decide, Move

Turning resistance into participation does not mean endless consultation.

Leaders still need to make decisions. They still need to set direction, manage trade-offs and maintain momentum. Not every concern can be resolved. Not every stakeholder will agree. Not every loss can be avoided.

The leadership balance is to listen, decide and move.

Listen deeply enough to understand reality.

Decide clearly enough to maintain direction.

Move consistently enough to create progress.

Problems occur when leaders overuse one part of this balance.

If they move without listening, they create avoidable resistance.

If they listen without deciding, they create uncertainty and fatigue.

If they decide without explaining, they create distrust.

If they explain without reinforcing, they create temporary compliance.

Participation works best when people can see both openness and leadership discipline.

They need to know that their input matters.

They also need to know that the transformation has direction.

What This Looks Like In Practice

Imagine an organisation introducing an AI-enabled case management workflow.

The goal is to reduce response time, improve routing, summarise customer context and recommend next actions for service teams.

At first, resistance appears across the business.

Frontline staff worry that the AI will misclassify cases and create more rework.

Team leaders worry that service levels will drop during transition.

Compliance teams worry about accountability and audit trails.

Experienced employees worry that their judgement is being replaced.

Data owners warn that customer records are inconsistent.

Executives are frustrated that the project is not moving faster.

A weak transformation response would treat these concerns as barriers.

A stronger response would turn them into participation.

Frontline staff become process testers, using real cases to validate routing logic and identify exceptions.

Team leaders become adoption translators, helping define how work will be managed during transition.

Compliance becomes a design partner, shaping review points, audit logs and escalation rules.

Experienced employees become subject matter experts, helping define where human judgement must remain.

Data owners become readiness advisors, identifying which data fields must be improved before scaling.

Executives become reinforcement leaders, communicating the purpose and removing organisational barriers.

The resistance does not disappear immediately. But it becomes useful.

The transformation becomes better designed, better governed and more adoptable.

A Practical Participation Lens

Leaders can use a simple participation lens when resistance appears.

First, identify the concern.

What is the stakeholder worried about?

Second, identify the source.

Is this about purpose, trust, capability, workload, risk, process design, data quality, role impact or reinforcement?

Third, identify the role.

Can this stakeholder contribute as a risk advisor, process tester, change translator, champion, subject matter expert or governance partner?

Fourth, identify the action.

What specific activity will move them from passive resistance into constructive participation?

Fifth, close the loop.

What will we do with their input, and how will we communicate the decision?

This lens helps leaders avoid the common trap of trying to persuade everyone with the same message.

Different resistance requires different participation pathways.

Why Participation Makes Change Stick

Participation matters because transformation is not just a project plan. It is a shift in how people work.

People are more likely to adopt a change when they understand why it matters, can see how it works, trust the process, have had a chance to shape practical details, and experience reinforcement from leaders and managers.

Participation also improves the quality of the transformation itself.

It reveals hidden risks.

It improves process design.

It builds ownership.

It strengthens trust.

It prepares managers.

It creates local advocates.

It makes adoption visible before go-live.

It helps the organisation learn during the transition, not only after problems appear.

In AI transformation, participation is even more critical because trust cannot be mandated. People need to understand when to rely on AI, when to question it, when to escalate, and how accountability works. That requires involvement, practice, governance and reinforcement.

AI adoption is not just about whether the technology performs.

It is about whether people can confidently and responsibly integrate it into real work.

Final Thought

Resistance is not the enemy of transformation.

Unexamined resistance is.

When leaders dismiss resistance, they lose access to some of the most important information in the change process. They miss operational risks. They underestimate loss. They overlook process realities. They weaken trust. They create surface-level compliance instead of genuine adoption.

But when leaders diagnose resistance, they can turn it into participation.

Sceptics become risk advisors.

Frontline teams become process testers.

Middle managers become translators.

Supporters become champions.

Governance teams become design partners.

The transformation becomes stronger because the organisation has helped shape it.

The goal is not to eliminate resistance.

The goal is to understand it early enough, respect it enough, and structure it well enough that it becomes part of the path to adoption.

That is how transformation moves from something done to people into something built with people.

And that is how change begins to stick.

About Me

I am a senior business, transformation, and professional services leader with experience across commercial strategy, AI-enabled solution delivery, customer transformation, and organisational change. I hold an MBA (MGSM) and have led initiatives across Australia and international markets, including APAC and the United States. My writing focuses on AI transformation, business process improvement, professional services, change leadership, and how organisations turn technology initiatives into measurable commercial and operational value.

For more information about my background, areas of focus and professional direction, please visit my About Me page. You can also view my full career history, professional experience, education and training on LinkedIn.

Open to Conversations

I welcome conversations with organisations focused on AI transformation, professional services leadership, customer transformation, and operational innovation. If you are exploring how to move from AI ideas to practical adoption, improve process design, or make transformation stick, I would be pleased to connect.

How To Turn Resistance to Change Into Participation

Table of Contents