Six months after a warehouse system went live in Amman, staff were still keeping a parallel paper ledger. Management called it resistance to change. We asked why, and the answer was immediate: the system could not record a partial delivery, which happened twice a week. The paper was not stubbornness. It was a workaround for a real gap.
Staff resistance is almost always rational. The mistake is treating it as an attitude problem rather than as information.
Staff resistance: the four real reasons
1. The new system is genuinely worse at something
Often something small that matters daily. The old screen showed stock and price together; the new one needs two clicks. Twenty times a day, that is a real cost to a real person, and they are correct to object.
Ask what the old way did better. There is nearly always an answer, and it is usually fixable.
2. It makes work visible that was not visible before
This is the reason nobody says aloud. A system that timestamps every step reveals who is slow, who is overloaded, and who has been quietly covering for a broken process. That exposure is frightening even to people doing nothing wrong.
Address it directly. If the data will not be used for individual performance management, say so explicitly and then do not use it that way. If it will be, say that too — the damage comes from ambiguity, not from either answer.
3. Nobody explained why
People are told what to do and not why it matters. Someone who understands that the change removes a compliance risk or shortens customer waiting will work around a rough edge. Someone who was simply instructed will not.
4. The last three systems were abandoned
In organisations with a history of half-finished rollouts, staff have learned that new systems disappear if ignored long enough. That is not cynicism; it is pattern recognition, and it is earned.
What does not reduce staff resistance
- More training. If people know how and still do not, the problem is not knowledge.
- Mandates. They produce compliance in the system and the real work elsewhere — which is worse than open refusal, because now the data is wrong too.
- Removing the old system. Tempting and occasionally necessary, but if the new one genuinely cannot do something, you have removed the workaround and not the problem.
- Blaming the department. The information stops arriving, and you lose the ability to see the next problem.
What actually reduces staff resistance
Involve the loudest sceptic early
Not the enthusiast — the person with the most objections. They know the process better than anyone, their objections are usually specific, and if they end up defending the system, everyone else follows. We have watched this change the outcome of a rollout more than once.
Fix one visible thing fast
Take the most-repeated complaint in the first fortnight and fix it within days. The fix matters less than the demonstration that complaints produce change. After that, people report problems instead of building workarounds.
Let one team keep the old way for a month
Counter-intuitive, and effective. A parallel period lets people verify the new system produces the same answers. Trust is what you are building, and forcing it is slower than earning it.
Measure adoption, not attendance
Training completion tells you nothing. Count how many transactions actually go through the new system each week, by department. That number tells you where the problem is, and it is usually one team rather than the whole company.
The Jordan-specific dimension
In many Jordanian companies seniority and personal relationships carry real weight in how work gets done. A system that routes approvals purely by role can cut across an arrangement where a respected long-serving manager was consulted informally on everything.
Ignoring that is not neutrality — it is a change to the social structure of the workplace, made by software. It is better to acknowledge it and design the workflow to include the people whose judgement the organisation actually relies on.
The question to ask first
When adoption stalls, ask one person who is not using the system: "What does the old way let you do that this does not?"
Ask it neutrally, and listen to the whole answer before responding. In our experience the reply is specific, reasonable, and fixable — and it arrives within thirty seconds.
