Introduction
Key Highlights
- Increasing staff competency prior to launch can greatly lower resistance by boosting users' self-assurance in their capacity to operate the new system.
- Employes can better grasp how the new technology will impact their daily tasks with role-based training that focuses on actual workflows.
- Employes can maintain new behaviors after go-live with ongoing reinforcement thru peer support, refresher training, and in-app advice.
- Organizations can detect resistance early and offer focused assistance before minor issues grow into more significant adoption barriers by monitoring areas where consumers struggle.
The greatest strategy to lessen resistance to change when implementing new digital transformation technologies is to increase employe competency prior to the rollout rather than just communicating the change more frequently. When people have experience with a new system, are aware of how it impacts their function, and are confident in their ability to do their duties in the new setting, they are much less inclined to oppose it.
This is important since employes’ unwillingness to participate is rarely the only reason for resistance to change. Workflows, performance standards, duties, and even people’s sense of job security can all be altered by a new enterprise system.
The scope of challenge is substantial. More than 700 organizations participated in Prosci’s research, which developed the ADKAR model as a framework centered on the individual outcomes necessary for successful change: Awareness, Desire, Knowledge, Ability, and Reinforcement. Prosci adds that companies that prioritize technology over the behavioral and psychological aspects of adoption frequently struggle with digital transformation.
Therefore, holding another town hall is not always the solution if employees are opposing a new ERP, CRM, HR platform, clinical system, collaboration tool, or other enterprise program. The most pertinent issue is: What makes the new method of working challenging or unclear? After you respond to that, dealing with resistance is lot simpler.
The Real Cause of Change Resistance
It is easy to categorise employees who oppose new technology as challenging, unfavorable, or change-resistant. That label doesn’t help. Think about what happens if an employee has been using the same system for five years. They are aware of every location. They are aware of the shortcuts. They are aware of what occurs when anything goes wrong. A large portion of the work is done by their muscle memory. Then a brand-new system shows up.
A task that used to take three minutes now takes ten. There is no longer a familiar screen. The process has evolved. Performance is measured differently by a manager. While still accomplishing their regular goals, the employe is required to study. Resistance might just be a logical reaction to conflict from the employee’s point of view. It may also be driven by real anxiety. According to Mercer’s 2026 Global Talent Trends study, worries about AI-related job losses rose from 28% in 2024 to 40% in 2026. It is unlikely that asking individuals to “embrace the transformation” will allay their concerns about how technology can impact their jobs.
Spikes in Resistance at Predictable Pressure Points
Resistance tends to rise at particular times. One is when the outdated system is eliminated. Employes can rely on known procedures in the interim. Another is when the new system starts to measure performance. A person who used to feel at ease experimenting now feels as tho every error is obvious.
Operational pressure is a third. Giving workers time to practice a new workflow beforehand results in a very different experience than asking them to learn it during the busiest time of the year. Instead of being viewed as unforeseen issues, these pressure points must to be included in the change management procedure. You can develop capability and support before friction increases if you know when it will occur.
Understanding the Change Curve
Every employe experiences change at a different pace. The emotional path connected to significant change is frequently shown using the Kübler-Ross Change Curve, which progresses from shock and resistance to acceptance and investigation.
It shouldn’t be viewed as a strict scientific procedure that all employes must adhere to in precisely the same order. Rather, it serves as a helpful reminder that people require time to adapt. A person who experiences difficulties in the initial weeks of a rollout is not always a long-term “resister.” They might just be at an earlier stage of the change. Giving individuals the useful assistance they need to move forward is the responsibility of change leaders.
A person who struggles in the initial weeks of a rollout is not always a long-term “resister.” They might just be in an earlier stage of the change. Giving individuals the practical assistance they need to move forward is the responsibility of change leaders.
The Failures of Communication-Only Change Management
In organizational change, communication is crucial. Workers must comprehend why the company is changing, what is changing, how it will affect them, and when it will take place. However, communication is limited. You can describe the benefits of a new CRM. You can justify the need for an ERP upgrade. Town hall invitations, bulletins, FAQs, emails, and leadership films can all be sent.
None of that instructs someone on how to execute a patient workflow, close a sales opportunity, finish a buy order, or generate a report on the new system. This is where well-established frameworks for change management come in handy.
What Kotter, Lewin, and ADKAR Really Tell Us
Five distinct outcomes are necessary for effective change, according to Prosci’s ADKAR model:
Knowledge → Ability → Awareness → Desire → Reinforcement
The fact that these cannot be substituted is crucial. To ensure that the new behavior sticks, employes must first comprehend the change, have a reason to support it, learn how to do it, become capable of performing it, and receive reward.
Kotter’s 8-Step Change Model adopts a more comprehensive organizational perspective, focusing on aspects like achieving short-term wins, expressing a vision, establishing urgency, forming a steering coalition, and anchoring new ways.
People’s awareness of change does not complete it. When individuals can genuinely collaborate in different ways, change occurs.
The Gap in Investment That Leads to Resistance
This is where a lot of efforts for digital transformation fail. Businesses frequently make significant investments on Desire and Awareness. They convey the business case. They describe the vision. Leaders discuss the advantages. Employees understand that the outdated system is being updated. Then, just before go-live, training starts. The issue is that understanding the why is not the same as being able to perform the how.
Even if an employe completely supports a change, they may still find it difficult to use the new technology. Resistance develops in the space between capacity and willingness. Therefore, rather than being viewed as a communications workstream that functions independently of training, workflow preparation, support, and reinforcement, an effective change management framework should be tightly linked to these areas.
Six Strategies to Lessen Change Resistance
1. Develop Skills Prior to the Rollout
The highest-leverage step is this one. Before requiring employes to adopt the new method for actual work, give them a chance to practice it. Showing them the interface is not the only objective. It is to enable them to carry out the tasks that they will genuinely need to carry out.
Rather than giving two-hour demonstration of a new ERP to a finance team, for instance, allow users to practice creating invoices, reviewing records, fixing frequent problems, and finishing the workflows pertinent to their jobs. Because employes can practice without the stress of a real-world production setting, simulation-based training is very helpful in this situation.
2. Target Specific Workflows Instead of General Behavior
“Embrace the change” isn’t a goal for training. “Become comfortable with the new system” is not the same. Workers must understand what is expected of them. Mapping the important workflows for each role is the first step.
Opportunities may need to be created and updated by a salesperson. Purchase orders may need to be raised by a procurement employe. Requests and dashboard reviews might need to be approved by a management. It can be necessary for a customer care agent to handle instances using a new interface.
These distinctions should be reflected in their training. The gap between training and real work is lessened via role-based learning. It also facilitates the diagnosis of resistance.
3. Make Plans for Predictable Resistance Increases
When resistance is most likely to rise should be identified in a rollout plan. If the legacy system is shut down on Monday. Employes should have finished significant practice prior to Monday rather than beginning learning on Monday morning.
Managers should be aware of the metrics and workflows in advance if new performance measurements start right after go-live.
Additionally, wherever possible, steer clear of centering the learning curve on a department’s expected peak period. Measurable organizational gains are linked to structured change management. According to a Relay assessment from 2026, firms who use organized change management can see a 10% reduction in resistance and a 21% gain in revenues when compared to spontaneous techniques.
4. Strengthen Learning in the Workflow
There is a limit to even the best pre-launch training. People tend to forget. Three weeks after completing a workflow correctly during training, a user may find it difficult to recall it when faced with an actual client request. Because of this, reinforcement must continue within the workplace.
When someone needs assistance, in-app guidance can deliver it. Users can receive guidance while completing the workflow rather than exiting the program to look thru a manual or call the help desk. For instance, Assima’s In-App Search can assist users in locating workflow instructions within the program.
5. Take Support from Champions
Workers’ reactions to leadership communication are not necessarily the same as their reactions to a coworker who does their duties. Peer champions are therefore useful during a rollout.
Select reputable staff members from various departments or teams and grant them early access to the new system. Before asking them to assist others, make sure they are truly capable. They should do more than just reiterate corporate messaging. Additionally, champions can offer the transition team an early warning system. Feedback from several employes who are having trouble with the same workflow can be used to enhance in-app instructions or training before the issue spreads.
6. Assess Competence and Resistance then Take Action
If you can’t perceive where resistance is occurring, you can’t effectively reduce it. However, exercise caution when measuring. Login credentials are insufficient on their own. Even if someone logs into a system on a daily basis, they may still utilize it improperly, avoid key features, come up with workarounds, or rely too much on coworkers. Instead, integrate competency assessments with adoption measurements. Finding the areas where friction is concentrated is the goal.
A company-wide retraining program might not be essential if 80% of users successfully finish a workflow but one crucial team continuously has trouble with it. Focus on the intervention. Analytics from in-app usage and simulation training can be used to pinpoint the precise workflows where workers require more assistance.
Conclusion
Organizations cannot eradicate resistance to change with a better slogan. Communication is essential. It matters to be a leader. Having a clear vision is important. However, more communication does not address the root of the issue when employees reject a new digital tool because they don’t think they can utilize it. Expertise does. In this way, change management goes from discussing transformation to making it feasible.
Examine how a systems training platform can assist staff members in developing practical competence prior to their expected performance in a live setting if you’re preparing to implement new enterprise software. Furthermore, getting individuals to accept the change should not be the only objective if your firm is already getting ready for a significant transformation.
Ready to close the last mile gap?
Frequently Asked Questions
Let’s Answer Some of Your Questions.
Prior to launch, increase employee proficiency through practical experience, role-based training, in-app assistance, and continuous reinforcement. Employe reluctance naturally lessens when they believe they can use the new instrument.
Employees frequently oppose new technology due to unfamiliar processes, a fear of making mistakes, or doubts about their capacity to do their tasks well. This friction can be lessened by gaining confidence during hands-on training.
Although communication is crucial, prolonged resistance frequently indicates a competency issue. Workers may comprehend the need for a change yet lack the expertise to operate the new system with assurance.
Employes who receive training gain the skills and information necessary to function well in the new system. Before going live, simulation-based practice and in-app reinforcement help transform awareness into confident adoption.
After launch, keep reinforcing new behaviors via adoption analytics, peer support, in-app instruction, and refresher training. Continuous reinforcement keeps employees from going back to their old methods of operation.
