The Hardest Part of a $2M ERP Implementation

I've run ERP rollouts across three different environments — teams with no system at all, teams on manual spreadsheets, and teams on legacy software so old that no one remembered who built it. Every time, the technology worked. Every time, the people were the problem.

Not because they were difficult. Because they were rational.

The procurement manager with the Excel file wasn't being stubborn. He had built that file over ten years. He knew exactly where everything was. He had formulas that finance depended on. He had workarounds for edge cases the new system hadn't accounted for yet. Asking him to abandon it on go-live day was asking him to trade something that worked for something unproven — on your schedule, not his.

That's not resistance. That's risk management.

In every rollout I've been part of, the resistance came in three forms:

Fear of exposure. When work is invisible, mistakes are invisible. A shared system makes both visible. Some people are not against the software — they are against accountability. You cannot fix this with training.

Comfort with the known. The old process, no matter how bad, is a known quantity. People have built habits, workarounds, and tribal knowledge around it. The new system asks them to feel incompetent for a few weeks before they feel capable. Most organizations underestimate how much that costs people psychologically.

Distrust of the project itself. In companies where previous initiatives were announced with fanfare and quietly abandoned, people wait to see if this one is real before they invest in it. They are not wrong to wait.

Every rollout I've been part of where adoption succeeded had one thing in common: we stopped trying to sell the system and started solving specific problems.

Before go-live, I sat with each department head — not to demo the software, not to run a training session. I asked one question: what is the one thing about your current process that costs you the most time or causes you the most headache?

Then I showed them exactly how the new system fixed that one thing. Nothing else. One pain point, one solution, demonstrated in ten minutes.

The procurement manager's problem was that he spent two hours every Monday manually reconciling purchase orders against delivery receipts. We showed him how the ERP automated that reconciliation and flagged exceptions automatically. His Monday mornings back. That was it. He became one of the rollout's strongest internal advocates within three weeks.

One win per person. The rest follows from there.

People talk about go-live like it's the crisis point. It isn't. The crisis point is week two, when the initial adrenaline has worn off, the edge cases start appearing, and the users who were never fully bought in start drifting back to old habits.

The teams that hold their adoption past week two are the ones where real people had real wins in the first week. Not system wins. Not efficiency metrics. Personal wins — a task that used to take an hour now takes five minutes, a question that used to require three emails now has a dashboard.

That is what carries an ERP past the go-live.

If you're planning a digital transformation and you're spending 90% of your energy on the technology — flip it.

The system will work. The question is whether the people around it will. And the answer to that question is decided before anyone logs in for the first time, in the conversations you have with each stakeholder about the one problem you're going to solve for them specifically.

The technology is the easy part. It always has been.