Why ERP Implementations Fail, and What the Winners Do Differently
By Dudley Peacock
Why ERP implementations fail
Ask why ERP implementations fail and most people point at the software. The real answer is almost always different. Projects fail because the organisation treats go-live as the finish line, when it is really the starting line. This is the heart of the two-phase model behind 100 Days and Beyond: the first 100 days build the system, and the beyond is where the return actually happens.
Key Takeaways
- The software is rarely the reason a project fails. - Treating go-live as the finish line is the most common mistake. - Process, data, and adoption decide the outcome more than features. - Winners plan for Phase 2 before they start Phase 1. - The return shows up in the months after go-live, not the launch week.
Phase 1: the first 100 days
The first 100 days are structured and finite: discovery, configuration, testing, training, go-live. Most teams pour everything into this phase and then exhale at launch. That exhale is the problem. The system going live is the moment the real work of getting value from it begins.
Phase 2: the beyond
The beyond is where efficiency compounds, manual work disappears, and the numbers start to speak. By month six things click. By month twelve the case is obvious. The organisations that get there are the ones who planned and budgeted for this phase before they signed anything.
The adoption dip is real
Right after go-live, productivity usually drops before it climbs. People are learning, edge cases surface, and confidence wobbles. Teams that expect this dip and support people through it recover quickly. Teams that assumed launch was the end mistake the dip for failure and stop investing at exactly the wrong moment.
Data and process beat features
A clean process on an average system beats a broken process on a brilliant one. Most failed projects automated a messy process or migrated poor data and then blamed the platform. Fix the process first, then let the system do its job.
What the winners do differently
They define what good looks like in month twelve, not launch week. They schedule quarterly reviews. They treat the system as a long-term growth trajectory, not a one-time purchase. You are not buying software, you are buying a trajectory.
If this is the kind of thinking you want more of, get the newsletter, join the community, or explore the services behind the philosophy.
FAQ
What percentage of ERP projects fail? Estimates vary by study and definition, but a large share run over time or budget or fail to deliver the expected benefits. The common thread is what happens after go-live, not the software choice.
Is the software usually to blame? Rarely. Most failures trace back to process, data, adoption, and the absence of a plan for the months after go-live.
What is the single best predictor of success? Whether the organisation planned for Phase 2, the beyond, before it started Phase 1. Teams that budget for ongoing optimisation get the return.