Why The Best ERP In The World Fails (If You Don’t Know How to Listen)

(Part 1 of 5 of the series “The Human Code of ERP”)

You can configure your ERP system perfectly. But if a warehouse manager doesn’t trust you, your million-dollar project is already dead. Here is the harsh, unspoken truth about ERP implementations.

The Real Reason Users Say No

A few years ago, while at a client’s site during the blueprint phase, I noticed a familiar look in the eyes of one of the users. It was that classic blend of skepticism mixed with the boredom of someone hearing the same old corporate fairy tale repeated for the hundredth time.

After talking for a while, I paused and asked if he wanted to add anything. He crossed his arms, which is a textbook sign of denial in behavioral psychology, and bluntly stated that the new ERP system would never work. It was “too generic” he argued, and completely ignored the myriad of specificities that made their business unique.

I realized right then that his critique was directed at the massive, overwhelming change hiding behind the software.

And in that moment, I was reminded of the golden rule of consulting: bad psychology kills more ERP projects than bad code ever will.

Welcome to the first part of The Human Code of ERP, a series dedicated entirely to the people who actually have to press the keys, looking beyond the bits, bytes, and APIs of our job. Today, we are talking about the hardest barrier to break in any software migration: the wall of “we have always done it this way”.

The Grief of the Legacy System

When a company decides to change its ERP, the management sees an upgrade. They see real-time data, AI-readiness, and streamlined operations.

For the end-user, changing the ERP feels like a profound loss of identity. In the best-case scenario, they see it as a waste of time because they have already memorized all the necessary steps in the old system. The mere thought of having to learn something entirely new from scratch is perceived more as a punishment than a genuine way to improve their daily workflow.

Think about it. The veteran key user from my story had spent twenty years mastering the quirks of the old system. He knew exactly which shortcuts to use to bypass a system lock. He knew how to extract a report that the other colleagues loved.

His expertise, his value to the company, and his daily confidence were inextricably linked to that obsolete software.

When we, the consultants, walk into the room and announce that management has decided to leverage the new functionalities of an ERP more modern than the currently installed system, we instantly reset their competence level back to zero alongside changing their tools. We are turning the undisputed master of the department into a confused beginner.

This triggers a response that is identical to the stages of grief:

1. Denial: “This new system is just a fad, management will cancel it once they see the cost.”

2. Anger: “This interface is garbage! It takes three clicks instead of one!”

3. Bargaining: “Can we just customize the new system so it looks exactly like the old one?”

4. Depression: “I don’t know how to do my job anymore.”

5. Acceptance: “Okay, show me how this new dashboard works.”

Beyond mapping data tables, our true job as ERP Consultants is to guide users through these five stages as quickly and painlessly as possible. We are change-psychologists disguised as ERP experts.

The 20/80 Rule of Listening

The biggest mistake many consultants make is trying to win over a hostile user by focusing too much on the technical features of the software rather than the actual business processes.

They open the software, project it on the screen, and start lecturing about how the new single logistic multi-site setup is vastly superior. They proudly explain how it creates a single, unified container for master data, eliminating the need to log in and out of different companies every time.

The user glazes over. They don’t care about your master data architecture. They care that they have to leave at 5:00 PM to pick up their kids, and your new system looks like it will keep them at the office until 7:00 PM.

To overcome resistance, you must apply the 20/80 Rule of ERP Workshops:

• Spend 20% of the time explaining how the new system works.

• Spend 80% of the time shutting up and listening to how they actually work.

Before you ever propose a solution in Infor LN or any other ERP, you need to ask questions. What is the most frustrating part of your Monday morning? Why do you export this list to Excel every week? What information is missing from this screen that forces you to call the warehouse?

When a user realizes that you are genuinely interested in the pain of their daily routine and want to understand their perspective, their defensive walls begin to crack. They stop seeing you as an invader and start seeing you as a partner.

The Ultimate Bug Fix: Trust

In my previous series on data migration, I talked about Garbage In, Disaster Out regarding data quality. The same applies to human relationships. If the relationship is toxic from day one, the implementation will be a disaster.

Here is a non-secret that everyone should always remember: If the users trust you, they will forgive the software’s flaws. If they resent you, they will weaponize every minor bug against the project.

During a Go-Live, things will break. Errors will pop up. Processes will momentarily stall. If the warehouse manager trusts you because you spent hours sitting next to him on a forklift understanding his process, he will look at an error screen and say, “Hey, we have a glitch here, let’s figure it out.”

But if you acted arrogant, ignored his input, and forced a standard process down his throat, he will look at that exact same error screen, cross his arms, call the CEO, and scream: “I told you this ERP system was a piece of junk!”

Trust is the ultimate shock absorber for the Go-Live. And you cannot configure trust in a software menu. You have to build it, face-to-face, months before the cutover.

Breaking the Wall

So, how do you practically build this trust and overcome the resistance of the most difficult Key Users? Here are three actionable steps you can implement in your next project:

1. Shadowing Before Blueprinting

Never start a project in a meeting room with a PowerPoint. Go to the user’s desk. Sit next to them for two hours while they do their actual job on the legacy system. Watch their hands. Notice when they sigh. Notice when they write something on a Post-it note because the system doesn’t have a field for it. You will learn more about the company’s real processes by watching them work for two hours than by reading 50 pages of official documentation.

2. The Five Whys for Absurd Customizations

When a user demands a highly expensive, non-standard customization (e.g., I need this screen to flash red when a specific component is missing!), do not just say No, the Cloud doesn’t allow that. Play the toddler game of the Five Whys.

Why do you need it to flash red? “Because I forget to check it before releasing the production order.” Why do you forget? “Because the bill of materials is too long to check manually.” Why is it a problem if you release it missing? “Because the shop floor will start the job and then stop, wasting time.”

Suddenly, you realize they don’t need a flashing red screen. They just need you to configure the MRP exception messages properly so the system alerts them to material shortages before they even attempt to release the order.

You have successfully solved a business problem and avoided writing unnecessary code.

Remember that asking questions, and asking a lot of them, is absolutely right and sacrosanct. Nobody cares about a consultant who walks in acting like they hold all the absolute truths in their pocket. When it helps you understand the real process, drop the ego and just ask, ask, ask.

3. Make Them the Protagonist of the Change

Always frame the new ERP as the tool that will finally empower them to focus on high-value tasks, rather than a system they are forced to use. The ERP is, after all, just a tool designed to put people in the best position to work smarter. By using the right narrative, such as With your deep knowledge of this supply chain, imagine what you could do if you didn’t have to waste three hours a day doing manual data entry?, you elevate their status. This makes them the protagonist of the change rather than a victim of it, and they will champion your system.

The Human behind the screen

The tools we use are changing rapidly. We are moving from on-premise servers to Cloud architectures, from manual data entry to Artificial Intelligence and Agents.

But while the technology evolves at breakneck speed, the human brain remains exactly the same. We still fear change. We still hate feeling incompetent. We still crave being heard.

The true value of an ERP Consultant lies in having the emotional intelligence to navigate the fears of the organization, far beyond memorizing every single technical parameter of the software. It is about turning a traumatic software transition into a unified step forward.

Because a perfect system with zero adoption is just an expensive screensaver.

Next up: How to stop the eternal war and build a true alliance between Functional Consultants and Developers.

Written by Andrea Guaccio 

April 30, 2026