Go-live is not adoption: why new systems fail after launch

There is a moment in every system rollout when the project is declared a success: the software works, the data is migrated, the invoices are paid. And then, six months later, someone notices that half the organisation still runs the process in the old spreadsheet.

Why training doesn’t fix it

The standard answer is “more training”. But people don’t avoid new tools because they can’t use them — they avoid them because the old way is faster for them, because nobody explained what’s in it for their work, or because their manager quietly tolerates the workaround.

Adoption is managed, not hoped for

What actually works is unglamorous: mapping who is affected and how, before go-live. Giving managers — not the project team — ownership of adoption in their units. Training that fits daily work instead of a one-off classroom day. And measuring actual usage until the new way is simply the way.

The AI angle

This matters more now, not less. AI changes workflows more than any system before it — an AI agent or a new automated process only creates value when people trust it and use it daily. Adoption is where AI investments are won or lost.

Rolled something out that didn’t stick? Book a 30-minute discussion — we’ll find out where it stalled.