7 min read Rollout

Why ERP rollouts fail (and it's hardly ever the software)

The six real reasons an ERP gets abandoned. None of them appears in a feature comparison, and all of them can be prevented.

A missing feature is hardly ever it

When a company abandons its ERP, the explanation given is usually «it didn't work». But when you ask in detail, a feature is hardly ever missing: what's missing is anyone using it properly.

Twenty years of watching this up close gives a fairly clear pattern, and it's six causes.

The six causes

  • The project outlasted everyone's patience. Eighteen months of rollout is long enough for the business, the team and the sponsor to change. What's delivered at the end is no longer what was asked for.
  • Nobody taught what each screen was for. The training covered which buttons to press, not which decision each piece of data supports. The result: fields filled in just to get past them.
  • Dirty data got migrated. Duplicate customers, items at zero cost, balances that didn't add up. The new system inherits the problem and takes the blame.
  • The old process was replicated. The ERP was configured to do exactly what was done before, workarounds included. Then it adds nothing, only steps.
  • Nobody owned it. The project belonged to IT, and IT can't decide how a purchase gets approved.
  • The vendor vanished at go-live. The real problems show up three months in, when the first close and the first odd case arrive.

The most underrated cause is the second one. A screen the user doesn't understand is filled in wrongly from day one, and from then on every report that uses it is wrong — with nothing failing.

What does work

  • Start with one module, not everything. The one that hurts most. Live in weeks, not quarters.
  • Clean the data before, not during. It's boring work and it's what decides whether the new system is born trustworthy.
  • Review the process before configuring it. If approval happens on WhatsApp today, automating that is automating the mess.
  • An owner from the business, not from IT. Someone who can decide how things get done.
  • Help inside the screen. So whoever hesitates finds the answer where the field is, not in a manual nobody opens.

If you're at the choosing stage, it's worth reading the awkward questions worth asking before you sign.

Choosing an ERP and getting value from it

On the same topic

An ERP you start with one piece

Zyntello is bought module by module: you start with whichever hurts today and add the rest on top of the same data, with no year-long project.