Analysis
Why ERP implementations fail
Most ERPs don't fail because of the technology. They fail at the five points where the vision is mistranslated before it reaches the system.
When an ERP implementation disappoints, the conversation usually revolves around the software, the vendor or the project team. But if you look closely at almost any case, the failure didn't happen in the technical configuration. It happened much earlier, in a chain of translations that no one looked after.
Gap 1 — The vision was never made explicit
The owner knows what they want, but carries it in their head. The project starts on assumptions, not on an articulated vision. The system ends up automating what the team thought it understood, not what the leader imagined.
Gap 2 — The current process was digitized, not the right one
Configuring the ERP on top of the process that exists out of inertia crystallizes bad habits into the system. Now the disorder not only persists: it's backed by an expensive tool and it's harder to change.
Automating a broken process only gives you a faster way to get the same bad result.
Gap 3 — Business and vendor spoke different languages
The business asks in terms of outcomes; the vendor hears in terms of features. Without someone to translate between the two, exactly what was asked for gets delivered —and exactly what wasn't needed.
Gap 4 — No one translated the change to the people
The system switches on, but people don't understand the why. They experience it as an imposed burden, not as an improvement. The 'resistance to change' that gets so much blame is almost always, in reality, a translation that never happened.
Gap 5 — The support ended at go-live
The project is declared closed on launch day, just when the real problems begin. Without sustained support, adjustments aren't made, shortcuts return and the system degrades until it becomes yet another tool people bypass.
The common pattern
The five gaps are the same problem at different moments: the vision gets distorted every time it drops a level and no one translates it. The technology was right; what failed was the translation that was meant to guide it.
Before your next implementation, measure where your vision is getting lost.
Schedule your Gap DiagnosisFrequently asked questions
We resolve the essentials
Because the failure is rarely technical. It happens across five translation gaps: the vision isn't made explicit, the wrong process gets digitized, business and vendor don't understand each other, the change isn't translated to the people, and support ends at go-live.
It's almost never the cause, but a symptom. When a team resists, it's usually because no one translated the why of the change to the people who live it every day.