ERP + Adoption

Your ERP is live and nobody uses it

Huceptron InsightsBy the Huceptron senior partners·5 min read

The system went live on the planned date. The steering committee closed the programme and thanked everyone. Six months later, finance still closes the month in spreadsheets. Nothing failed, and nothing changed.

01 Go-live is a technical milestone wearing a business milestone’s clothes

It proves the software runs, the data moved and the integrations hold. It proves nothing about whether the work is now done differently. Those are separate achievements with separate plans, and only one of them usually gets funded.

02 The three places adoption dies

Training happened once, as an event, before anyone had real work to do in the system - so it was rehearsal, not learning. The workaround was never closed: a spreadsheet that bridged a genuine gap during cutover, still there a year later, now load-bearing. Nobody measured usage, so nobody knew. A programme that does not measure adoption cannot tell the difference between a system people use and a system people avoid.

03 How to tell which one you have

Pull the numbers you already hold: logins by role, transactions by route, the share of month-end journals still entered by hand. Then ask one question on the operational floor - what do you do when the system will not let you do the thing you need to do? The answer is your adoption problem, described by the people who have it.

04 Fixing it after the fact

An ERP that is technically sound and operationally ignored does not need replacing. It needs the change track that was never run: the workarounds named and given owners, the process decisions that were deferred at cutover actually made, training rebuilt around real tasks, and someone accountable for usage rather than uptime. Replacing the platform instead is the most expensive way to avoid that conversation, and it reproduces the same ending.

05 What a better ending looks like

Go-live starts the measurement period rather than closing the programme. Thirty days of measured usage against a plan, a named owner for every workaround, and a decision point at the end where the programme is closed on evidence instead of on the date.

Related: why your AI pilot will not scale.

ERPAutomationAdoptionChange managementProgramme delivery
One week. Then you know.
The AI audit week - what applies to you, where the gaps are, and what to do first
See what the week covers →