Back to insights

Employee resistance to change: how to bring your teams along

Team in a meeting about employee resistance during a digital transformation

New software, a paperless process, a shared workspace: on paper, every digital project saves time. In practice, technology rarely holds a project back. The real obstacle is human, and it has a name: employee resistance to change. In an SME, where every person matters, it deserves a proper plan rather than a memo.

Where employee resistance comes from

Pushback usually reflects a legitimate worry. People fear losing their bearings, the expertise they built on the old system, or even their job. They are not against progress on principle; they want to protect what works for them. Understanding these root causes is therefore the first step towards reducing employee resistance. Objections also vary by profile. A long-serving accountant and a newly hired salesperson will not raise the same concerns, so listen to each group separately.

Four common sources of employee resistance

  • Fear of the unknown: new tools unsettle those who had fully mastered the old system.
  • Poor communication: when management imposes a project without explaining why, teams feel left out.
  • Perceived extra workload: learning new software on top of daily work feels overwhelming.
  • Bad past experiences: after a failed project, distrust makes sense.

Six ways to reduce employee resistance

1. Explain the why before the how

Show each department the concrete benefits: less re-keying, fewer repetitive tasks, information in one place. Then hold open sessions where everyone, sceptics included, can ask questions. In Brussels, plan these sessions and the training material in French and Dutch if your staff work in both languages.

2. Recruit champions early

Pick one or two volunteers in each department. These champions test the tools first, report friction points and become trusted go-to people for their colleagues. Their opinion often carries more weight than a note from management.

3. Train in short sessions

Avoid 8-hour marathon training days. Instead, schedule short, regular sessions of 1 to 2 hours, spread over time. Moreover, work on real cases from daily tasks: learning by doing builds habits far better than abstract theory.

4. Accept mistakes during the transition

Errors are part of learning any new tool. Punishing them at this stage creates a climate of fear and hardens employee resistance. Instead, set up a simple channel where people can flag a blocker and get help quickly.

5. Train managers first

Line managers carry the project day to day. If they have doubts, their teams will share them. So give them the arguments, early access to the tools and time to handle objections on the ground.

6. Involve staff representatives

In Belgium, Collective Labour Agreement No. 39 requires the companies it covers to inform and consult the works council, or failing that the union delegation, before introducing new technology with significant collective consequences. Even without a formal obligation, bringing these representatives in early defuses many tensions.

Measure adoption without monitoring individuals

Track a few concrete indicators: usage of the new tools, number of support tickets, user satisfaction. This data reveals bottlenecks and helps you adjust your support plan. However, favour figures aggregated by team over individual tracking: the GDPR restricts workplace monitoring, and a measure that feels like surveillance only fuels employee resistance.

Mistakes that make employee resistance worse

  • Announcing the project by email, with no discussion or questions.
  • Rolling out every tool at once, across every department.
  • Switching off the old system before new habits take hold.
  • Ignoring feedback from the field once the tool goes live.

Questions to ask before launch

  • What concrete problem does the new tool solve for each role?
  • Who will act as champions, and how much time can they give?
  • Which training schedule leaves room for everyday work?
  • How will you collect feedback once the tool goes live?

Turning pushback into useful feedback

When you listen carefully, pushback shows you what to fix: a screen that feels too complex, a forgotten step, a training gap. A successful digital transformation therefore depends as much on people as on technology. At Espero-Soft, we handle the technical side and also change management, from training your champions to tracking adoption. Explore our digital transformation support or tell us about your project to build a plan that fits your company culture.

Need help with your project?

Contact Espero-Soft to discuss your IT needs