Who should own adoption after an ERP or WMS go-live?

An executive on your side, named in writing before kickoff, who owns adoption on the floor after the deployer leaves. Not the implementation partner, not the project team and not the deployment strategist: they leave with a sign-off, and the floor keeps working the week after the project ends.

How it works

Most deployment plans end at go-live. The floor does not. The people who configure the system arrive with a tool, frame every problem in its terms and are gone by month three, when the work has moved and the misfits show. If nobody on your side owns that moment, each fix lands in an account with nobody’s name on it, and the go-live stays on record as a success.

The deployer cannot be that owner, however good. A deployer answers to the contract and to the sign-off. Adoption needs someone who answers to you after the vendor has gone.

Evidence

In a 1997 management-journal article, Lynne Markus and Robert Benjamin named a belief they found in IT-enabled change: the magic bullet theory. Nobody is assigned to make the change happen, and everyone assumes the technology will do it by itself.

What this does not prove

Sources

From the field notes The Smith and the Tailor · PDF, 10 pages