Go-live is not adoption
Why enterprises keep paying for software their people never fully use, and what to do instead.
Every large software rollout has a day that gets celebrated. The system goes live, the project team is thanked, and the programme closes. On the plan, that day is the finish line.
For the people who have to use the system, it is the starting line. And that is where most enterprises stop paying attention.
The go-live illusion
We measure software projects by delivery: on time, on budget, in scope. Those are reasonable measures of a project. They say nothing about whether the business got what it paid for.
The value of an ERP, a CRM or a core banking system is not in its installation. It is in thousands of people doing their daily work through it, correctly and without friction. That happens, or fails to happen, in the months and years after go-live, long after the project budget has been spent.
The pattern is familiar. Usage climbs in the first few weeks, then settles at a level well below what the business case assumed. Workarounds appear: spreadsheets kept alongside the system, emails sent instead of workflows used, fields left blank. Support tickets rise. A small group of experienced users becomes the unofficial help desk, and their own work slows down.
None of this shows up in a project report, because the project is closed.
The load keeps growing
The problem is getting harder, not easier. In a 2023 survey of 4,861 employees, Gartner found that knowledge workers used an average of 11 applications for their work, up from six in 2019, and that 47% struggled to find the information they needed to do their jobs effectively.
Every new application adds screens to learn, rules to remember and places to look for answers. Every cloud release changes some of them. Every new joiner, transfer and reorganisation resets the clock for someone. A rollout plan that ends at go-live can’t keep up with any of this.
Adoption is an operation, not a project
The enterprises that get full value from their software treat adoption the way they treat security or finance: as an ongoing operation, with owners, tools and measures.
In practice, that means four shifts.
From training to guidance in the flow of work. Help should appear inside the application, at the moment someone needs it, rather than in a course they took last quarter.
From documentation to answers. Your policies and procedures already exist. The problem is finding them. People should be able to ask a question in plain language and get an answer from your own approved content, with the source.
From manual steps to action. Some work does not need to be learned at all. Routine, rules-bound tasks that span several systems can be done for people, within the permissions they already have.
From usage to outcomes. Logins tell you little. What matters is whether people complete key tasks, how long a new joiner takes to become productive, how often data is entered wrongly, and how many questions never needed to become tickets.
Who owns adoption?
In most enterprises, nobody does. The project team has moved on. IT supports the platform but not how it is used. The business assumes the system works. HR and L&D ran the training and closed the file.
Naming an owner changes everything that follows. Someone has to decide which processes matter most, watch where people struggle, and fix it, every month, for as long as the system runs. It is the same discipline as any other operation, applied to the gap between owning software and using it well.
What changes when you get this right
When adoption becomes an operation, the conversation with the board changes. Instead of asking why a system is underused, leaders can see which teams are struggling, with which tasks, and what was done about it. Upgrades become less risky, because people are guided through what changed. New joiners stop depending on the goodwill of busy colleagues.
Most importantly, the software you have already paid for starts doing what it was bought to do.
That is the idea behind ArkaFlows. The day a system goes live is the day the real work of adoption begins.
Next step: Pick the one application your people struggle with most, and ask what happens there after go-live. If the honest answer is “not much”, let’s talk.
Rather talk it through?
Thirty minutes on your own screens, with your own questions. No slideware.