Why Is It So Hard to Deliver a Successful ERP Project?

If you’re a project sponsor, you’ve probably asked this question at least once: “We hired good people, bought good software, so why is this ERP project still struggling?”

Here’s the honest answer: ERP projects are hard not because any one part of them is hard, but because so many different things have to work together, in the right order, at the same time.

Let me explain it the way I’d explain it to a friend, no jargon.

It Looks Like an Iceberg

From where a sponsor sits, an ERP project looks simple. You see a project plan, a go-live date, and a few status reports that say “on track.” That’s the tip of the iceberg, the part above the water.

Below the waterline is a completely different world: technology decisions, people problems, broken processes, architecture trade-offs, leadership gaps, resistance to change, governance rules, and yes, office politics. All of that is happening at once, mostly invisible to anyone who only looks at the status report.

The biggest mistake sponsors make is judging the project by what’s above the water. That’s exactly why so many ERP projects run into trouble, not because the tip of the iceberg changed, but because something shifted underneath it.

Think of It Like Cooking a Big Family Dinner, Not a Single Dish

An ERP implementation isn’t one recipe. It’s several recipes that all have to finish cooking at the same time and come together on one table.

Imagine hosting a big family dinner: a roast, a soup, a dessert, and fresh bread, all needing to be ready together. Each dish has its own steps, its own timing, and its own things that can go wrong. If the bread needs another 10 minutes but the roast is done now, you have a decision to make. Rush the bread? Let the roast rest longer? Change the plan on the fly?

That’s what running an ERP project actually feels like, except the “dishes” are things like:

• Technology – Does the software actually do what the business needs?
• People – Are the right skills in the room, and are they available when needed?
• Process – Are the old ways of working being redesigned, or just copied into new software?
• Architecture – Will the systems talk to each other cleanly, or will we be patching things together for years?
• Leadership – Is someone senior actually making decisions, or are hard calls being avoided?
• Change management – Are the people who’ll use the system every day being brought along, or just told at the end?
• Governance – Is there a clear, fast way to make decisions and resolve conflicts?
• Politics – Whose budget, whose turf, whose priorities are quietly shaping what gets done first?

Miss the timing on any one of these, or ignore it completely, and the whole dinner suffers, even if every individual dish looked fine in the kitchen.

Why “Simple Plans” Backfire

A common trap: sponsors ask for a simple, one-page plan because it feels reassuring. But a one-page plan that hides eight moving disciplines isn’t simple, it’s just simplified. And simplified is dangerous, because it lets problems build up quietly underwater until they surface as a missed deadline or a failed go-live.

A useful comparison: a pilot’s pre-flight checklist looks simple, one page, short items. But that simplicity was earned by years of testing every system underneath it, fuel, weather, mechanics, crew readiness. The checklist works because someone respected the complexity behind it. It didn’t work by pretending the complexity wasn’t there.

What This Means for You as a Sponsor

You don’t need to become a technical expert to sponsor a successful ERP project. But you do need to ask questions that go below the waterline, not just above it. A few examples:

• Instead of “Are we on track?” ask “Which of the eight areas (tech, people, process, architecture, leadership, change, governance, politics) is currently the weakest, and what are we doing about it?”
• Instead of “Is the software configured?” ask “Have the people who’ll use this daily actually tested how it fits their real work, not just a demo?”
• Instead of “Did we hit the milestone?” ask “What decision did we avoid making this month, and who is blocking it?”

The Bottom Line

An ERP project isn’t hard because the technology is hard. It’s hard because it forces a business to get technology, people, process, architecture, leadership, change, governance, and politics all pulling in the same direction, at the same time, in the right sequence.

The sponsors who succeed aren’t the ones who simplify the project down to a status color. They’re the ones who stay curious about what’s happening underwater, long before it surfaces as a problem.