The morning after
Go-live was at 6 AM on a Saturday. By Monday at 10:14 — I remember the time because I was reading email standing up — a department head wrote: "Everything is fine. The team is using the old format on paper and someone keys it in at the end of the day."
That single sentence cost the company more than the implementation. Not because anything in the software was broken. Because the change had been announced, but not absorbed.
A new system rolls out in a weekend. A new habit takes a quarter.
The memo myth
Most ERP projects budget change management as a line item somewhere between "User Manual" and "Town Hall." Both deliverables get checked off. Neither one moves a person from the way they worked on Friday to the way you need them to work on Monday.
The memo myth is the belief that announcement equals adoption. It almost never does. Behavior is sticky. Spreadsheets are sticky. The ten-year-old workaround that one person built and the whole team relies on is the stickiest thing in the building.
If you can't name three people who will lose status from the new system, you haven't found the resistance yet.
Three things, repeated
Across five go-lives, the change-management tactics that actually moved adoption were small, embarrassingly low-tech, and repeated constantly.
Train on the Tuesday job
Not "how to create a vendor." The actual sequence Rina runs from 9 AM to 5 PM on a normal Tuesday — including the awkward parts.
Walk the floor every morning
For two weeks post-launch, the BA stands next to operators while they do real work. No demos. No screens projected. Just stand and watch.
Promote a champion per shift
One operator, one shift, formally named. They don't fix bugs. They translate, defuse, and report what's actually happening.
Field notes
What I tell C-levels now
When I scope an enterprise engagement now, I'm explicit about the math of a go-live. The software is roughly 50% of the budget and 30% of the impact. Adoption is the rest. If a leadership team isn't willing to fund the boring part — floor walks, named champions, three rounds of refresher training, a feedback loop that closes the same week — I'd rather they wait six months and start when they are.
Because the worst outcome for an ERP project isn't a bug. It's a quietly successful go-live with a team that, three months in, has reverted to the spreadsheets — politely, around the system, without ever telling anyone.
Adoption is what people do; it sits on top of two things that have to be right first. The data they see on day one has to be trustworthy — that is the job of a disciplined Excel-to-Odoo migration. And the workflows have to actually fit the Tuesday job — which is what a real UAT script surfaces before go-live, not after. Change management cannot rescue a system that fails on either.
Change management isn't a memo. It's the patience to keep showing up on the floor until the new way of working becomes the only way anyone remembers.
FAQ
Why does ERP change management fail in Bangladesh?
It fails because it is treated as a communication task rather than a behavioural change programme. Sending a memo or holding one training session is not change management. Real change management requires sustained engagement from senior leadership, department-level champions, and visible accountability before, during, and after go-live.
What is the most effective change management approach for Odoo ERP?
The most effective approach combines three things: executive visibility (senior leaders visibly using the system), departmental champions (power users who support colleagues every day), and tight feedback loops (regular pulse checks and same-week issue resolution). Training is necessary but never sufficient on its own.
How long should ERP change management activities run?
Change management should start at project kick-off and run at least 90 days post go-live. The pre-go-live phase builds awareness; the hypercare phase (first 30 days live) is the highest-intensity; the 60–90 day post-hypercare phase embeds new behaviours permanently. Most failed projects stop change management at go-live — which is exactly when it matters most.
If you're scoping a rollout and want a sober view of what adoption actually costs — let's talk →