We often hear:
ERP projects are chaotic.
ERP projects are complex and expensive.
ERP projects often fail.
These statements sound factual. In reality, they are weak. They quietly remove responsibility from leaders. They imply that failure is natural, that chaos is inevitable, that nothing more can be done. As if ERP is a storm we must endure.
ERP projects are not inherently bound to fail. The issue is rarely the system. The issue is our lack of understanding, experience, and competence in managing them properly.
Chaos begins when noise overwhelms signal. Too many opinions. Too many side agendas. Too little clarity on decision rights, scope, and priorities. The project does not create the chaos — it exposes it.
Complexity is relative. What feels complex to one organisation feels structured to another. Complexity is often a reflection of our capability to understand cross-functional processes, governance, data structures, and change management. The less prepared we are, the more “complex” the project appears.
Expense is another misunderstood narrative. ERP initiatives are perceived as expensive because we underestimate the true cost of transformation. We ignore internal backfill, business SME time, change management effort, and governance overhead. We assume the vendor fee is the project. It is not. The real investment is organisational energy.
ERP projects do not fail. We fail to implement them well.
These initiatives typically happen once every 10–15 years. Many executives will sponsor one or two in their career. Organisations rarely build internal capability between cycles. Institutional memory disappears. Lessons are forgotten. The same mistakes repeat.
The problem is not the ERP.
The problem is how seriously we take governance, architecture, resourcing, and education.
If leaders treat ERP as a strategic transformation — not an IT installation — outcomes change. When executives invest in competence, clarity, and disciplined governance, chaos reduces, complexity becomes manageable, and cost becomes intentional rather than reactive.
ERP is not a gamble. It is a capability test.
