How to Sequence a System Rollout So It Actually Gets Used

Why do most system rollouts miss their goal?

Between 55% and 75% of ERP implementations fail to meet their business objectives, according to implementation analyses compiled by Prosci and others. The post-mortems rarely blame the software. They name weak planning, thin training, and process change nobody managed.

Picking the platform is a fraction of the work. Deciding what the process becomes on go-live day is the rest.

What does adoption actually mean after go-live?

Adoption means the new path is the shortest path for the person doing the work. Go-live is a date on a plan. Adoption is a behavior on the floor. A technically sound system that people route around returns nothing.

As of 2026, the implementation literature has largely settled on naming user adoption, rather than go-live, as the real success metric. Someone slower in the new system is usually protecting their day, not resisting the change.

Which workflow should you configure first?

Configure the workflow that touches cash first. Teams usually sequence by what is easy to set up, so invoicing and cash application land last, after the data model is already fixed.

Whatever goes in last inherits a shape built without it. The money workflow ends up describing a job one way and the rest of the system describes it another, and someone reconciles the difference by hand every month from then on.

How do you spot a rollout that is drifting?

Look for the spreadsheet someone keeps beside the new system. Treat it as data, not as a discipline problem. It is a free map of the step your new workflow does not cover, built by the person closest to the work.

There are two records worth comparing, not one:

• The system tells you what got entered; the side spreadsheet tells you what people needed to enter and could not.

What has to be decided before you buy?

Two things, and only two: who owns the outcome, and what happens on the exception.

Field names, screens, and notification timing are all cheaper to settle inside a tool than in a meeting about the tool. If you cannot name the owner and the exception rule, no software will decide them for you, and you will pay for the tool and the argument.

What does a rollout look like when it works?

We rebuilt a B2B roundtable-events business that ran its entire operation on one 50-worksheet spreadsheet, where a broken formula in a single tab cascaded errors into the others. The replacement put a database at the center as the single source of truth, automated the full email lifecycle from invitation through post-event follow-up, and let people browse and sign up for events on their own. It returned roughly 8 hours a week of the owner's time.

That gain did not come from better software. It came from deciding where the record of truth lived before anything got configured.

How do you measure whether the rollout worked?

Time one task, both ways, with the person who actually does it. If the new way is slower, fix the workflow before you buy more training.

Adoption follows the shorter path, every time.