The Problem is not the ERP. It’s the Blindness.
Most problems have simple solutions.
Health: eat less, move more, rest. Money: earn more, spend less, invest. Family: listen more, say less, change yourself before you try to change anyone else.
We know this. We have always known this. The solutions are not hidden. They’ve been solved a thousand times before us. And yet — we circle. We spin. We exhaust ourselves looking for something more sophisticated than the simple answer that was already there.
ERP programs work the same way.
The basics of a well-run technology program are not mysterious. Define what you’re trying to achieve before you select a system. Maintain executive visibility throughout delivery, not just at gate reviews. Ensure the people closest to the work have the authority to raise problems early. Hold vendors to what they committed to. Don’t let scope drift quietly while the status report stays green.
None of this is new. None of it requires a framework you haven’t heard of.
And yet programs worth tens of millions of dollars fail — not at the technology layer, but at the layer of basic discipline that every executive in the room already knows about.
So what’s actually happening?
It is your unconscious incompetence and overconfidence on conscious incompetence. The first means you don’t know what you don’t know. The second — and this is the harder one — means you know there’s a problem, but you’re confident you can manage it yourself, from the inside, without help.
Both conditions feel identical from where the executive is sitting. The program looks manageable. The team is working. The vendor is communicating. There’s motion everywhere. And motion, in the absence of a clear standard for what good looks like, reads as progress.
The blindness is not stupidity. It’s structural.
No one inside a failing program has the incentive to name the failure clearly. The project team needs the program to succeed. The vendor needs to protect the contract. The sponsor needs to protect the decision they already made. So problems get managed rather than resolved. Status reports describe activity rather than outcomes. Steering committees hear what the room has silently agreed to say.
And the executive — who has full authority and genuine intent — spins. Not because they’re incompetent, but because every source of information they rely on is compromised by the same system they’re trying to oversee.
The catastrophic failures I’ve seen weren’t caused by bad technology or bad people. They were caused by simple problems that weren’t registered as problems early enough — and when they were finally registered, the instinct was to solve them internally rather than to ask whether the internal capability was equal to the task.
Most of our problems are not unique. They have been solved before. The solutions are often simple.
The question worth sitting with is this: who in your program is positioned to tell you the truth before the cost of correction becomes too high?
