The ERP vendor’s Sales team kept things simple—too simple. They barely mentioned what truly matters: readiness for ERP adoption, change management, data quality, or the skills needed for testing, training, and embedding the new system into the business.
The project started on the back foot. The client realised—too late—the depth of skills, capacity, and capabilities needed in-house to make it work.
A qualified ERP Project Manager came on board eventually and somehow got Phase 1 over the line. But by then, the organisation was burnt out. Change fatigue had set in. Phase 2 never happened.
The system delivered in Phase 1? Only partially used. And with staff turnover, most of the knowledge walked out the door.
A few years later, they were shopping for a new ERP.
Same mistakes. Different year.
History repeated itself.
This isn’t rare—70% of ERP functionality often goes unused years after go-live. Not because the product was wrong. But because the organisation wasn’t ready.
So the question is—what will you do to break the cycle?
If you’re a decision-maker, I urge you to educate yourself on every step of the ERP journey.
This isn’t a choice. It’s your duty.
The truth? No one is going to say this to you. Because once you’re equipped with knowledge, you become dangerous.
So dangerous that others can’t quietly push their own agendas. Don’t forget—I’m with you.
