Picture this: a company spends eight months and a lot of money implementing a new system. Go-live day arrives. Three weeks later, half the sales team is still working from their personal notebooks, whispering “I’ll input it tonight” and then forgetting. The warehouse supervisor is hiding the old paper forms in a drawer.
You can buy the best software in the world and it will fail if people refuse to touch it.
I walked into this exact situation at a window manufacturer with 90 employees. The owner’s first instinct was more training sessions. But the problem was trust, not understanding. Senior staff had seen three “new systems” come and go in ten years, and each one was abandoned within a year.
I’ve watched this pattern repeat in dozens of companies. That’s why ERP Consulting looks at people before it looks at screens.
The real reason people resist
It wasn’t laziness. Older warehouse staff worried the system would make their experience useless. Sales reps worried management would finally see exactly how long they spent on each account. And honestly? Some of those worries were justified.
The system did expose inefficiencies. The trick was framing that exposure as a tool for them, not a weapon against them.
The turning point came when we let the loudest critic of the system help design the daily workflow. He was a warehouse lead with 22 years of experience. Within a week, he found a way to cut two hours of scanning time per shift. After that, he became the system’s biggest champion.
- Find the most vocal skeptic and give them a real role in configuring how their team uses the system
- Put the old paper forms in clear physical view but require a brief explanation in writing whenever someone uses them
- Publish a weekly “wins” board listing specific numbers, like “order entry time dropped from 9 minutes to 4”
How fast can attitudes actually change
Faster than you’d think, if the evidence is concrete. By day 45, the warehouse lead was showing new hires how to scan. By day 60, the sales team was logging in on their own before their morning coffee because they discovered the system showed them their commission status in real time. Nobody had to nag them.
Here’s the principle that mattered: people accept a new system when it solves a problem they personally feel, not when it solves a problem the CEO describes. Also, you can’t out-train a trust problem—giving people ownership beats another slideshow every time.
What I’d tell any owner before go-live
Set aside 30% of your implementation energy for the human side before you even pick software. When you’re stuck and the rollout is going badly, that’s exactly when to bring in an outside pair of eyes. ERP Consulting often gets called in after a failed launch, and in nine cases out of ten, the fix is simpler than the owners feared: stop defending the system, start listening to the critics, and redesign the workflow together.
Your next step is small but real: schedule a 30-minute private conversation with the one person most opposed to the change and ask them what the system makes worse for them personally. Write down their answer. That one conversation tells you more than any vendor demo ever will.