Employee resistance to new software: causes and what to do

In short: Employees resist new software mostly because for the first few weeks they work slower and have to learn, while the benefits seem to go to someone else. The fix is to listen and separate valid feedback from old habits, quickly remove the friction that is real, coach people at their desks and set a fixed date to retire the old way. Punishing or forcing people early usually just teaches them to enter data for show.

Why do employees resist new software?

New software asks people to pay first and benefit later. A salesperson who logs orders in Excel takes seconds per order. In the new system they search for the customer code, pick product codes and fill in required fields, so each order is slower for the first weeks. Meanwhile the payoff, such as automatic reports and accurate balances, goes to accounting and the director.

Beyond speed there are fears people rarely voice: being monitored, being replaced by automation, or losing status as the keeper of the master file. Our guide to change management in digital transformation covers each of these in a full table. This article deals with a narrower situation: the software is live, staff are pushing back, and managers need to know what to do in the next few weeks.

First, separate feedback from resistance

Not every complaint is resistance. Some point to a real flaw in the software or the new process, and ignoring them throws away the most useful information from the rollout.

The simple test is to ask for a concrete example. "This software is a pain" can't be fixed. "Every order makes me choose a warehouse, but we only have one" can be fixed the same day. People with genuine feedback can usually give an example like that. People resisting change tend to stay vague while keeping their old spreadsheet going.

Five common objections and how to answer them

What staff say	What it often means	Answer with action
"Excel is faster"	The software has extra steps, or they don't know the shortcuts	Watch them enter one order, remove unneeded fields, show shortcuts
"The old way works fine"	They see nothing in it for them	Show which of their own tasks disappears, such as month-end compiling
"I'm too busy to learn"	No time to learn during work hours	Put learning time in the schedule and ease targets in week one
"So the boss can watch me?"	Fear the data will be used to punish	Say who sees which figures and why; don't penalise based on month-one data
"It keeps crashing"	Could be real bugs, could be missing guidance	Log every issue, send it to the vendor, report back to whoever raised it

What the last column has in common: the answer is something you do, not something you say. A meeting about the benefits of digital transformation achieves less than deleting three pointless fields from the order screen.

Steps to handle resistance to new software

Step 1: Listen in week one

The team lead sits with each main user at least once and watches them do a real task in the system. Note every point where they stop, ask a colleague or reopen Excel. That list is more reliable than any survey.

Step 2: Fix the real friction fast

Split the list into what configuration can fix (remove fields, set defaults, change print templates) and what needs the vendor. Close the first group within a week or two and tell the person who raised each item. Users who see their input acted on keep giving feedback instead of drifting back to Excel.

Step 3: Coach at the desk instead of one big training

A long session before go-live is mostly forgotten within days. It works better to pick one power user per team who learns first and sits near colleagues during the early weeks. Write guides by task ("quote for an existing customer"), not by software menu.

Step 4: Set a date to retire the old way

As long as the old spreadsheet is accepted, people will keep using it. Leadership picks a specific date, announces it in advance, and after that day figures outside the system don't count, including reports sent to the director. Directors and managers have to follow the rule first.

Step 5: Talk privately with persistent holdouts

If a few people still aren't using the system after all this, the manager should talk to them one to one rather than calling them out in front of the team. An unspoken reason often comes out: fear of losing their job, friction with the power user, or a type of work the software genuinely doesn't handle. If nothing changes after all of the above, it becomes a matter of following company rules and is handled like any other HR issue.

When is resistance right?

Resistance is a signal to stop when people across several teams raise the same concrete problem and it survives configuration fixes and training. For example, sales software that can't handle dealer-specific price lists forces staff to calculate prices in Excel and retype them. That is the wrong tool or a badly designed process, not lazy staff.

To avoid it, have main users test the software on real data before you sign. Our article on small business digitization describes a 30-day trial, and business management software lists selection criteria.

Measuring real adoption

Measure behaviour, not training hours:

• Share of orders and quotes entered in the system out of the real total.
• Number of old spreadsheets still being updated after the cut-off date.
• Support questions per week, and which ones repeat.

A team using the system much less than others is a reason to look at the process with them, not a reason to punish.

FAQ

What if our best employee resists the most? Top performers often have their own fast way of working and lose the most by switching. Invite them to help configure the new process or act as power user; they will find the wasted steps faster than anyone.

Should we penalise staff who don't use the new software? Not in the first weeks, because early penalties teach people to enter data for show. After the cut-off date, and once enough support has been given, not using the system is handled like any other breach of company rules.

How long until staff get used to it? It depends on complexity and support. Track the share of transactions in the system weekly rather than guessing, and retire the old way only once that share is stable.

What about older employees who learn more slowly? One-to-one coaching on the exact tasks they do daily works better than a group class. Short guides with step-by-step screenshots also help them look things up on their own.

---

HAT Solutions rolls out automation and software for SMEs together with the change management that makes it stick: choosing power users, task-based training and measuring real use. Get in touch to talk through a rollout that is stuck. Read the pillar guide: Change management in digital transformation.