Written by Chani Otto, Executive Associate at Change Logic
Across South Africa, organisations are investing billions into ERP systems by modernising finance, supply chains and core operations. Yet, despite this investment, failure rates remain alarmingly high. Retailers experience supply chain disruption. Municipalities struggle with billing systems. Banks delay transformation timelines. These failures are often labelled as “technology issues”.
We’ve seen this recently with the Spar SAP rollout, which triggered major supply chain disruption and ultimately led to an R168 million lawsuit from franchisees. We’ve also seen it with the City of Johannesburg’s billing platform collapse, which left residents unable to see or verify payments. Across multiple industries, large ERP programmes have quietly reset timelines, budgets and scope.
These issues are not simply “technology issues”. The reality is far more uncomfortable, and far more important for executives to understand.
ERP Systems Rarely Fail Technically
By the time an ERP system reaches go-live, the technology is usually sound. Platforms such as SAP, Oracle and Microsoft are robust, tested and capable. Integrations are validated. Infrastructure is scaled. The system works.What doesn’t work is the organisation’s ability to operate inside it. ERP systems fundamentally change how decisions are made, who owns data and how work flows across teams. Yet most organisations treat this shift as secondary to the implementation itself.
The Real Failure Point: Post-Go-Live Adoption
The most critical phase of any ERP programme is not implementation. It is the first six to 12 months after go-live. This is when teams begin reverting to old processes, workarounds emerge outside the system, data quality deteriorates and accountability becomes unclear. Operational pressure collides with unfamiliar systems, and behaviour wins. In this phase, the ERP system doesn’t fail. The organisation does.
Why Businesses Blame the System
When performance drops, the instinct is predictable: “The system isn’t working.”
But ERP systems don’t create new problems. They expose existing ones, including weak operating models, poor data governance, misaligned leadership and a lack of accountability. ERP doesn’t create dysfunction. It reveals it, and it does so at scale.
The Capability Gap No One Plans For
South African organisations are excellent at selecting technology, running procurement processes and managing implementation partners. But they consistently underestimate one thing: their ability to absorb change. This capability is not built through training programmes, communication campaigns or temporary consultants alone. It requires leadership ownership, behavioural accountability and embedded operational discipline.
Technology Doesn’t Transform Organisations – People Do
ERP success is not determined by software. It is determined by whether leaders drive adoption, whether teams change their behaviour and whether new ways of working become standard practice. Organisations that succeed treat change as an operational discipline, not a project phase. They track adoption using real metrics, intervene early when behaviour deviates and embed accountability into daily operations.
The Lesson Behind ERP Failures
ERP failures are rarely about technology. They are about timing and readiness. Systems go live faster than organisations can adapt. Leaders assume adoption will follow automatically, while the internal capability required to support the transition remains underdeveloped. South Africa is not lacking ambition or investment. It is lacking execution capability at the human level.
How to Prevent ERP Failure
To avoid failure, organisations must shift their focus from technology delivery to adoption execution. This means defining ownership of adoption across roles, measuring behaviour rather than only measuring project milestones, identifying risks early through adoption signals and embedding change into daily operations. ERP success is not achieved at go-live. It is earned through what happens next. To speak to one of our experts before your ERP project fails, reach out to Change Logic through our contact page.
CHAT TO OUR TEAM TO AVOID THE SAME PITFALLS.
______________________________________________________________________
Frequently Asked Questions
Why do ERP projects fail in South Africa?
ERP projects fail primarily because of poor adoption, a lack of leadership alignment, weak data governance and inadequate change management, rather than because of the technology itself.
What is the biggest risk in ERP implementation?
The biggest risk is the post-go-live adoption phase, during which teams may revert to old behaviours and fail to use the new system fully.
Are ERP failures caused by bad software?
No. Most ERP platforms, including SAP, Oracle and Microsoft, function correctly. Failures are typically caused by organisational and behavioural challenges.
How can ERP failure be prevented?
ERP failure can be prevented by driving leadership accountability, measuring user adoption, embedding change into operations and managing behavioural risks early.
What happens after ERP go-live?
After go-live, organisations face operational pressure, user resistance and process confusion. This is the most critical phase for ensuring that the implementation delivers its intended value.
What is ERP adoption?
ERP adoption refers to how effectively employees use the system, follow the new processes and integrate the platform into their daily operations.
