What to do when employees resist new systems? A communication and training guide for small and medium-sized enterprises implementing change

Why is it that every time a new system is implemented, the boss feels "This is clearly to help everyone," but the employees look indifferent, and after going live, they go back to using the old methods? Is it that the employees aren't cooperating, or was no one told "why the change is necessary"?

Most small and medium-sized business owners meticulously plan their budget, selection, and feature lists when implementing a new system, but they overlook one crucial element: people. A new system doesn't go live by itself; it's adopted by employees who are already swamped with work and need to learn, use, and change their work habits. If these employees feel forced, questioned, or burdened with increased workload, even the best system will be slowly undermined as they revert to "old ways."

This article will organize the most common resistance phenomena and causes faced by SMEs when implementing new systems. It will break down three different types of coping mechanisms: "don't know how to use," "don't want to use," and "don't dare to use." It will provide a preparation checklist before change communication, a four-step process for the implementation period, and observation points for managers to self-check. At the end of the article, there are 8 frequently asked questions to help owners and managers avoid the most common pitfalls.

What is employee resistance?

In the context of change management, resistance to change refers to the psychological and behavioral reactions of organizational members to new ways of working, tools, or systems. It is not necessarily a sign of "bad employees," but more often a natural reaction of "I feel insecure about the unknown."

Resistance usually doesn't appear in an openly stated way, but rather through several common behaviors:

• Silence: No one at the meeting objected or asked questions.
• Procrastination: I attended the training and learned the operations, but I just "haven't started using it yet."
• Rollback: After a brief attempt with a new system, sneakily returning to Excel or paper
• Finding fault with minor shortcomings of the amplification system as a reason not to use it
• Resignation alert: Senior employee hints at resignation with "can't do this anymore"

Understanding resistance as a "signal" rather than "hostility" is the first step in managing change.

Two. Differences between "will not use," "do not want to use," and "dare not use."

Treating all resistance as an "attitude problem" is the most common misjudgment among small and medium-sized enterprises. In practice, resistance can be classified into at least three completely different types, each requiring a different solution.

Type	Core cause	Common expressions	Handle direction
I don't know how to use it.	Skills and information gap	The operation is stuck, repeating the same question.	Strengthen training and operations manual
Don't want to use it	Misaligned motivations and interests	Surface treatment, not actually used.	Re-communicate benefits and incentives
Don't dare to use it	Lack of psychological safety	Afraid of making mistakes, afraid of being criticized	Establish a space for trial and error and a support window.

Sending employees who "don't dare to use" something for extra training, and calling employees who "don't want to use" something "can't use," usually only deepens resistance. First identify the type, then decide on the approach.

III. Five Common Types of Resistance

In addition to the three categories mentioned earlier, several more specific forms of resistance are commonly observed in practice:

Senior veteran employee type Employees with over ten years at the company are familiar with existing processes and find new systems "excessive." These employees have significant influence; if they successfully adapt, they will lead the entire team. However, if they continue to resist, they will become a negative benchmark for the team.

Performance anxiety type Performance and KPI pressure is high, and there are concerns that the new system's learning curve will affect short-term performance. These employees are not opposed to change, but rather do not have the bandwidth to bear the risks of the transition period.

Passive-aggressive Superficial agreement, nodding heads in meetings, but persistently using old methods in private, even influencing other colleagues' willingness. This type of resistance is the most difficult to detect and handle.

Skill-anxious type Employees who are unfamiliar with digital tools and worried about not being able to learn them or being ridiculed by younger colleagues need patience and psychological support, rather than more training documents.

Exclusionary Not being consulted at all during the planning phase and only finding out on launch day, "we're going to use this from now on," tends to provoke the strongest resistance because the feeling is one of "disrespect."

IV. Pre-implementation Checklist

Before the new system is officially implemented, it is recommended that supervisors complete the following inventory:

• List of affected departments and personnel
• Each character's current workflow and pain points
• Expected changes after each character is introduced
• Which employees are considered "key influencers" (opinion leaders or long-tenured employees)?
• Possible types of resistance and their corresponding targets
• Should performance evaluations during the introductory period be temporarily adjusted?
• Who serves as the support window, and what is the response time?
• Key Performance Indicators (KPIs) for tracking effectiveness within the first three months after implementation

The focus of this list isn't "who will object," but rather to provide executives with a comprehensive view of the entire organization before taking action.

V. Four-Step Process for Change Communication and Training

The following process is suitable for small and medium-sized enterprises (SMEs) when implementing a new system, with a cycle of 1 to 3 months:

STEP 1 Preliminary Consultation and Consensus Building During the system selection or planning phase, invite key stakeholders to participate in interviews or trials. The goal is not to have everyone agree on every detail, but to make them feel that "their voices have been heard." The output will be a record of the needs interview and a memorandum of understanding.

STEP 2 Public Announcement and Explanation of Benefits Executive leadership will personally explain to all relevant personnel "Why we need to change, what will happen if we don't, and what each role will gain after the change." The message should be brief, specific, and verifiable, avoiding slogans. The output will be a change communication presentation and a Q&A document.

STEP 3 Phased Training and Trial Design training content based on roles, avoiding a "one-size-fits-all" approach for the entire company. After training, implement a trial period that allows for mistakes and provides immediate support. Outputs will include training materials, operational manuals, and support records.

STEP 4 Feedback and Adjustment Regularly gather frontline feedback, fine-tune systems or processes, and publicly state "We made this change based on whose suggestion." This action greatly enhances employee engagement. Output feedback logs and adjustment logs.

Four-step role division

Stairs	Person in charge	Time required
STEP 1 Preliminary Consultation	Project Manager, Supervisor	1 to 2 weeks
STEP 2 Public Announcement	Senior executive	Within a week
STEP 3 Training and Trial	HR, Supervisor, Vendor	2 to 8 weeks
STEP 4 Feedback and Adjustment	Project Manager, Supervisor	Continue

VI. Scenarios Suitable for Active Promotion

The pace of change can be accelerated in the following situations:

• Senior management has reached a consensus and is willing to step forward and explain personally.
• The budget includes costs for training and the transition period.
• There are already opinion leaders in the organization willing to be early adopters.
• The introduction goals clearly correspond to the employees' actual work pain points.
• The introductory period does not overlap with peak business periods.

VII. Situations requiring a pause

In this situation, rushing to accelerate will only increase resistance.

• The company recently underwent significant layoffs or organizational restructuring.
• Key department heads lack consensus on transformation goals.
• The busiest business season of the year is approaching.
• The existing system just had a major failure, and employee morale is low.
• There are no support windows, and employees can't find anyone to ask when they encounter problems.

In these situations, address organizational and trust issues first, then discuss system implementation.

VIII. Common Traps and Risks

Here are some common pitfalls small businesses fall into when dealing with employee resistance:

Equating resistance with non-cooperation Using only the four characters "bad attitude" to cover up all problems results in missing the real causes. The correct approach is to first identify the type, then decide on the method.

Training without communication Thought "the church's operation would be fine," but didn't explain why it should be used or what benefits it would bring to employees personally. As a result, employees can operate it but don't know how to use it.

Senior executive invisibility If all the change is delegated to HR or the project manager, and senior executives don't get involved, employees will feel that "the boss themselves doesn't even value this," and resistance will naturally deepen.

No support window. After the system goes live, no one is responsible for answering questions, and employees get stuck and have to give up. The first week is the golden period for resisting transformation; if missed, it will take ten times the effort to remedy.

Ignore first-line feedback Employee questions are dismissed as "complaints" instead of signals, leading to missed opportunities for adjustments. Over time, employees will stop providing feedback.

IX. Case Studies

During the planning phase of implementing a new customer relationship management system, a certain small to medium-sized service company did not involve their frontline sales staff. In the first month after launch, sales staff continued to report their progress using Excel, and supervisors always saw empty data in the system's backend.

After the consulting team intervened, the first action was not to strengthen training, but to conduct individual interviews with the three salespeople. Two things were discovered during the interviews: First, the system's field design did not match the actual follow-up rhythm of the sales team. Second, the salespeople were concerned that data transparency would lead to "micromanagement" by their supervisors.

Based on these two causes, the team made two adjustments: First, they simplified the system fields, retaining only the few necessary for daily use. Second, senior executives personally explained to the business team that "this system is not a monitoring tool, but rather allows supervisors to see in real-time when business teams need support." They also promised that system data would not be used as a basis for performance evaluation during the trial period.

After the adjustment, the utilization rate of the business team significantly improved within two weeks. This case illustrates that the solution to resistance often lies not in the system itself, but in people and trust.

X. Conclusion

The introduction of a new system is ostensibly about replacing technology and tools, but in reality, it's a reorganization of organizational habits, trust, and interests. Small and medium-sized enterprises have limited resources and tight-knit organizations, so any poorly handled resistance can stall an entire project. However, precisely because organizations are tightly knit, if the direction is right, the speed of change can be much faster than in large enterprises.

Yanhui Co., Ltd. has been assisting small and medium-sized enterprises with digital transformation for many years and has witnessed too many cases where the system and process design were correct, but the project ultimately failed due to human factors. We assist companies from needs assessment, change communication, training design, to post-implementation maintenance and support, incorporating the human element into the overall solution planning. If your organization is currently facing resistance to adopting new systems, we invite you to schedule a consultation. Enterprise Digital Transformation Planning Consulting, or through ckc.tw/contact get in touch to separate the issues of people and tools.

Key points summarized

Q1: When introducing a new system, is employee resistance inevitable?

Some degree of resistance is normal for any organizational change. The difference lies in whether the resistance is seen and addressed. A complete lack of resistance should be a warning sign, as it may indicate that employees have chosen to "go through the motions while mentally checking out."

Q2: Senior employees are strongly resistant, should we replace them?

Replacing someone is a last resort. The influence of veteran employees can be a hindrance or a help. First, understand their concerns. Inviting them to participate in planning, or even to act as an internal trainer, can often turn a hindrance into a help.

Q3: How long should the training be to be sufficient?

There's no single definitive answer, but we recommend not holding training sessions just once. A more effective approach is "multiple short sessions": 30 minutes to 1 hour each, divided into 3 to 5 sessions, with employees returning to practice in between. A one-time long training session has limited memory retention.

Q4: Does a senior executive absolutely have to appear in person?

In the initial declaration phase of adoption, having senior management personally explain will greatly increase acceptance. The subsequent execution phase can be handed over to the project manager, but they should still make personal appearances at key nodes (e.g., launch, encountering significant resistance, one-month review).

Q5: What if an employee just doesn't want to learn?

First, clarify whether it's "unwilling to learn" or "afraid to learn." If it's the latter, what's needed is support, not pressure. If it's the former, then we need to go back to communication, understand their real concerns about the system, and discuss tangible benefits.

Q6: Can performance be used as an incentive during the introductory period?

Yes, but be careful. Performance incentives are effective for driving usage in the short term, but if you rely solely on external incentives long-term, employees will abandon them as soon as the incentives disappear. A better approach is to also build intrinsic motivation (e.g., by making employees truly feel that "the new system actually makes my job easier").

Q7: In small and medium-sized enterprises without a dedicated HR department, who should be responsible for change communication?

Typically, the project manager or department head takes on this role. If resources are limited, external consultants can assist in designing the communication framework and training materials. However, the actual communication with employees should still be handled by internal individuals who have a foundation of trust.

Q8: Can it be salvaged after an unsuccessful implementation?

Yes, but you need to stop first and not push forward forcefully. The common practice is to pause the promotion, go back to the site to understand why it failed, adjust the plan, and then restart with a small-scale pilot. Admitting failure and starting over is less costly than pushing forward to the very end.