Across South Africa, organisations are pouring billions into ERP platforms and large systems transformations. Retailers are rebuilding supply chains. Municipalities are digitising billing platforms. Banks are modernising core systems. Manufacturers are connecting operations to real-time data. The logic is sound. Modern ERP platforms promise visibility, automation and the ability to run a business with far greater precision.
Yet, often the results on the ground tell a more uncomfortable story.
In recent months alone, South Africans have watched several high-profile system failures unfold in public view. The Spar SAP rollout triggered major supply chain disruptions and ultimately led to an R168 million lawsuit from franchisees. The City of Johannesburg’s billing platform collapse that left residents unable to see or verify payments. And across multiple industries, large ERP programmes have quietly reset timelines, budgets and scope.
These stories tend to be framed as technology failures. In reality, most of them are not.
After more than two decades working on large transformation programmes, I have yet to see a major ERP implementation collapse because the software did not work. SAP works. Oracle works. Microsoft works. The technology itself is rarely the problem. The problem is what happens inside the organisation when the system goes live.
ERP projects rarely fail technically
By the time an ERP platform reaches go-live, the technical build has usually been tested extensively. Integrations have been validated, workflows configured and infrastructure scaled to support the system.
Technically, the platform can often do exactly what it was designed to do. What is far less prepared is the organisation that now has to operate inside that system and manage data effectively.
An ERP system does more than automate processes. It changes how decisions are made, who owns them, and how work and data move through the organisation. Tasks that once lived in spreadsheets are suddenly governed by system controls, and teams must operate in ways that feel unfamiliar at first. In theory, that shift is exactly what transformation is meant to achieve. In practice, it is often the moment when programmes begin to struggle.
When that adjustment does not happen smoothly, people fall back on what they know. Managers override controls to keep operations moving. Teams quietly rebuild workarounds outside the system simply to keep work flowing, and data quality begins to slip because accountability for inputs is unclear.
The most dangerous phase of any ERP programme is not the build. It is the first six to twelve months after go-live, which is when operational pressure collides with unfamiliar processes.
In retail, it may mean distribution teams bypassing new workflows to get stock onto trucks faster. In finance, it may mean departments delaying transactions because they do not fully understand the new process. In municipalities, billing data may stop flowing correctly because ownership of data inputs was never clearly defined.
Business always blames the system
The pattern that follows is remarkably consistent. Operational performance starts to dip, customers feel the disruption and executives begin to question whether the programme is working at all. Before long, emergency stabilisation teams are assembled to “fix” the situation.
The instinctive reaction is to blame the system. Yet in most cases, the technology is doing exactly what it was designed to do. What it is actually revealing are organisational issues that existed long before the system went live. In particular, it exposes gaps in how organisations prepare for change, including the absence of clear operating models, aligned leadership direction and well-defined user adoption journeys. This is why the real risk in 2026 is not software selection.
South African organisations are generally very good at choosing technology. Procurement processes are rigorous, vendors are carefully evaluated and implementation partners are selected through extensive due diligence. Boardroom debates tend to focus on whether SAP, Oracle or Microsoft is the right platform, or whether a move to cloud-based ERP makes strategic sense.
What rarely receives the same level of attention is the organisation’s ability to absorb the change that follows.
That capability is not built through communication campaigns or training schedules, and it cannot be outsourced to temporary consultants who disappear once the system launches. It requires internal leadership, clear accountability for adoption and the operational discipline needed to embed new ways of working.
The capability most organisations overlook
Technology programmes do not transform organisations. People do.
The success of an ERP programme depends far less on software features than on whether leaders take ownership of the behavioural change required to make the system work in practice. That means clarity on who is accountable for adoption across functions, governance structures that monitor operational behaviour rather than just technical milestones, and leaders who understand the system well enough to embed it into daily decision-making.
When these elements are missing, the consequences become visible very quickly. Municipal billing systems across South Africa have repeatedly struggled after upgrades, not because the technology could not process transactions, but because data governance, process ownership and operational accountability were never fully embedded in the organisation.
In my experience, those who succeed with large transformation programmes rarely do so because they selected better technology. They succeed because they treat organisational change as a core operational discipline rather than an afterthought. And they drive a focused change management journey from the outset, actively managing both business and people risks, while tracking leader and employee adoption against clearly defined KPIs. In this context, change management becomes a discipline grounded in data, used to anticipate and address readiness issues before they impact performance.
The lesson behind the headlines
If a system fails the technology blame game starts and questions are asked about the software vendor, the implementation partner or the size of the project budget.
But when you examine these failures more closely, a different pattern tends to emerge. Systems are often implemented faster than organisations can realistically adapt. Leaders assume that adoption will follow naturally once the technology is live, and the internal capability required to guide that transition is either underestimated or absent altogether.
South African companies are not short of ambition when it comes to transformation. Significant investment is being made in modern platforms, digital capabilities and new operating models. What they often lack is the internal capability required to ensure those transformations actually take hold.
