Most platform rollouts are declared a success on the day the system stays up. The return is decided in the ninety days after that, and few are measuring it. Panorama Consulting published a piece on 14 September on what it calls "green go-live" failures: implementations that are technically sound and organisationally hollow. It lists four signals, and names a cause it never turns into a check: ownership ended at go-live. Here is how to check for all five in your own business, what each one is costing you, and what to do about it, whether or not you own a digital adoption platform.
Because the project was judged on cutover, and the benefits were promised on behaviour change that nobody owns after cutover. Panorama's analysis names four causes: requirements captured the current state rather than the future one, schedule pressure forced configuration to replicate legacy processes, training covered the software but not the process change, and project ownership ended at go-live so nobody was accountable for the benefits. The cost of the resulting friction is not small. WalkMe's State of Digital Adoption 2026 study, which is vendor research and should be read as such, puts it at 51 workdays per employee per year lost to software and AI friction. A system that runs perfectly and changes nothing is the most expensive kind of success there is, because the licence is being paid for and the old way of working is still being paid for too.
If a team maintains a spreadsheet alongside the new system, the system has lost that team's trust and the data inside it is probably already out of date. Ask each operations team lead one question: what do you keep outside the system, and why? The answers cluster into three groups. The system does not hold a field they need, which is a configuration fix. The field exists but nobody knows where it is, which is a guidance and training gap and the cheapest of the three to close. Or the process was configured to mirror the old way, so the workaround survived, which is the expensive one, because the benefits case was built on a process that never arrived. Count the spreadsheets. That number is your adoption gap in plain sight.
Inconsistent practice across sites means the process was never standardised, and the platform has simply given every team a faster way to do it their own way. Pull the same transaction type from three teams and walk through how each one records it, step by step. In regulated firms this matters beyond efficiency: a process performed three ways is three sets of evidence for the same control, and an auditor will ask which one is right. Standardising after go-live is a change job before it is a tooling job. In-app guidance, mandatory fields and task-level analytics all help enforce the standard once it exists. The decision about which of the three ways is the right way has to be made by an owner with authority, and that owner is exactly the person Panorama says usually disappeared at cutover.
Unused modules are the easiest gap to see and the easiest to measure. Most enterprise platforms report feature usage natively; the reports are rarely reviewed once the implementation team leaves. Run them. Then separate the unused functionality into two piles: things the business decided not to use, which is fine but should come off the bill at renewal, and things it intended to use and never started, which is the real gap. Forrester research commissioned by Whatfix and published in March 2026 estimated that a 1,000-person enterprise loses around $10.9 million a year to poor digital adoption, with workers spending 728 hours a year navigating poorly adopted environments. Treat vendor-commissioned figures as directional rather than precise. The point stands: the licence line on the P&L is only the visible part of the cost.
If claims, onboarding, invoice processing or case handling take as long as they did before go-live, the benefits case has not landed, however green the dashboard looks. This is the check many firms cannot run, because they never baselined the old process. If that is you, baseline now. Take the five highest-volume processes on the new platform, measure end-to-end time and the number of human touches this month, and hold that as the reference point. Panorama recommends re-baselining metrics within ninety days of go-live rather than waiting for an annual review, and its case study describes a public sector implementation, stalled partly because there was no documented current state to measure against, regaining momentum within three months of an organisational assessment. A baseline taken late is worth far more than none, because from that point on you can see whether anything you change actually moves the number.
If the answer is "the vendor" or "IT", nobody does. The benefits case was signed by an operations or transformation leader, and the return needs a named owner from the same side of the business, with one number to report every month. In practice the roles that work are a Head of Change or Adoption with real usage analytics, or a process owner per platform with the authority to change configuration and guidance without a change request. This is also where a digital adoption platform earns its keep: it gives that owner a view of who completes which workflow, where they drop out, and a way to fix a step the same day. On WalkMe-enabled processes we have seen support tickets fall by 60 per cent. That only holds when someone owns the number and reads it every week; the tool alone does not do it. A dashboard nobody owns is decoration.
It produces a short list of fixes with a named owner and a number attached to each, not a lessons-learned deck. Run the five checks above in a fortnight. For each signal you find, write down the process, the cost (spreadsheet hours, licence spend, cycle time, ticket volume), the fix, and who owns it. Then agree the one number the executive sponsor will see each month. Most of the fixes are small: a field surfaced, a step guided, a report switched on, a standard chosen. The value is in doing them in the window when people are still forming habits on the new system, rather than eighteen months later when the workaround has become the process. If your rollout went live this year and none of this has happened yet, the ninety days are a target, not a cut-off. Start the count now.
Within ninety days. Panorama Consulting recommends re-baselining metrics inside that window rather than waiting for an annual review, because habits on a new system form quickly and workarounds harden into process.
No. The first four checks need nothing more than usage reports, a spreadsheet count and a stopwatch. A digital adoption platform makes the fixes faster and gives the return a permanent owner-facing view, which is where it pays back.
The business leader who signed the benefits case, or someone reporting to them, with authority over configuration and guidance and one adoption number to report monthly. Not IT alone, and never the vendor.
Your teams are not using your software the way you intended. Find out what that is costing you: the Digital Adoption Scorecard takes nine questions.
Tell us what you are rolling out and where adoption, automation or AI is sticking. We will come back with a clear plan for the first steps, what success looks like, and what it costs. No fifty-slide pitch.
Book a call