ERP go-live: the bottleneck your tech won't fix
The system went live Monday at 6 a.m. By 10:15, three managers have already called you.
Not about a bug. About people working around the new process, going back to their old Excel file, deciding to "wait and see." You delivered a multi-million-dollar ERP, on time. And yet, on the floor, the team isn't on board.
If you've lived through this, you know: the hardest part of a SAP go-live starts once the system is on.
You delivered the system. Now comes buy-in.
Your project lead talks to you about modules, interfaces, data migration. Your technical teams will handle all of that. The day-to-day is another story: a clerk logging receipts on paper "just to be safe," a supervisor calling the super-user ten times a day, a team scanning out of order because the new sequence makes no sense to them.
Your managers are your best allies
A distribution-center manager who has run operations the same way for 12 years doesn't change his reflexes that easily. He needs to understand why, to feel capable, and to bring his team along. You promoted them because they're excellent at what they do. But handling a hard conversation while everything's in motion, reassuring an anxious employee, redirecting someone who's pushing back without cornering them: no one ever taught them that. A good operator isn't automatically a good mobilizer. Those are two different muscles.
Change management: what to do in the first weeks
Getting your managers ready before and during the rollout is the best return on your investment.
You don't need a massive parallel project. You need to prepare them to see the human issues coming and to understand what sits behind the behaviors and the patterns.
The 4 faces of change resistance
Change resistance doesn't have a single face. It has four, and you probably have all of them on your teams right now.
The anxious one is afraid of no longer being good at their job. They're not challenging the system, they doubt themselves. They need reassurance, not convincing. Create safety, show them you won't drop them during the learning curve.
The angry one feels the decision landed on them, they'd have wanted a say. Hear them out for real: sometimes they're pointing at a genuine blind spot. Then be clear: using the new system is part of the job, it's not up for negotiation. You hear them on the how, not on the whether. A refusal that settles in becomes a management conversation, with consequences.
The overwhelmed one isn't against it. They're drowning. A new system on top of an already-full load. Help them break the learning into small steps so it feels less huge: one function at a time, a first small win, then the next. Give them room to breathe.
The indifferent one is the biggest group, and the most dangerous. They're not even resisting. They just don't see the link between this new system and their real work, they don't get what it's for. It's on you to draw that link, otherwise they'll fake surface-level adoption and slip back to old habits the moment you look away.
Leading change means recognizing who you're talking to and adapting your approach.
The 3 pillars: See. Choose. Act.
See. Identify the 4 types of resistance with your managers. Just putting words on it changes how they read their team. They stop seeing "resisters" and start seeing people with different needs.
Choose. Faced with someone who resists, the reflex fires on its own. Help your managers choose their posture instead of reacting on autopilot. Which reaction, which tone, which way to step in for the person in front of them. An anxious employee you choose to reassure at the right moment can make all the difference.
Act. Seeing and Choosing is half the work. The bulk of it is taking action: having the conversation you were avoiding and stepping in with respect. Here, for instance, that could mean adopting the posture suited to the type of resistance and to the person behind it. Then own your decision fully and move forward. That's where change becomes real.
As I often say in my talks: you choose, or you endure. There's no third option.
Bottom line
Your ERP is probably well configured. The ROI you'll present at the next board meeting ties directly to your managers' ability to lead their teams through the change. The tech, you've bought it. Buy-in needs leaders who can mobilize.
FAQ
Why don't teams adopt a new ERP even when it works? Because a successful go-live depends first on team buy-in. The system can be perfectly configured: if managers don't mobilize their teams through the change, people work around the new process and go back to their old habits.
Why isn't technical training enough to drive ERP adoption? That kind of training teaches people to click. It doesn't touch the fear, the loss of status, or the question everyone asks in silence: will my job still exist after this. That's the managers' work, not the training plan's.
What are the 4 types of change resistance? There are four: the anxious one, afraid of no longer being good at their job; the angry one, who'd have wanted a say; the overwhelmed one, drowning under the load; and the indifferent one, who doesn't see the link to their work. Each needs a different response.
How do you handle an employee who resists a new system? By first identifying their type of resistance, then adapting your posture: reassure the anxious one, truly listen to the angry one, lighten and break the task down for the overwhelmed one, draw the concrete link for the indifferent one. One message for everyone doesn't work.
How long does the productivity dip last after an ERP go-live? Usually 4 to 12 weeks. It's normal and it can be planned for. Organizations that budget neither money nor support for this period experience the dip as a failure, lose users' trust, and see parallel Excel files appear that never go away.
Why does an ERP break in production when the tests passed? Often because the tests validated each function separately without covering the end-to-end process (order, inventory, production, shipping, invoicing, collection) at realistic volume. And because the people who know the real process only flag the gaps when they feel safe. An engaged team tests honestly; an anxious team checks the box and stays quiet.
When should you start preparing for adoption? Ideally well before the go-live. The earlier you equip your managers, the less time resistance has to settle in.
