Skip to main content
How to Get Staff Buy-In for Business System Change
Home / Blog / Digital Architecture & ERP
Digital Architecture & ERP

How to Get Staff Buy-In for Business System Change

Technology implementations fail for human reasons more often than technical ones. The ERP system is configured correctly. The data migration is complete. The training has been delivered. And six months after go-live, the team is using workarounds, the system data is incomplete, and management is wondering what they spent the money for.

The root cause is almost always the same: the people who were supposed to adopt the new system were never genuinely bought in to it. They complied with the minimum required by the implementation project. They reverted to their previous methods when no one was watching. The system became an additional burden rather than a replacement for what they were already doing.

Getting genuine buy-in (not compliance, but actual willingness to change) is the most important implementation challenge and the one most organisations underinvest in.

Why Staff Resist New Systems

Resistance to new systems is rarely irrational. Understanding the real reasons behind resistance is the first step to addressing it.

Fear of skill obsolescence. Staff who have built expertise around current systems and workarounds see a new system as a threat to that expertise. The person who knows how to reconcile the inventory spreadsheet and is the go-to when it breaks has informal authority that disappears when the new system makes the reconciliation automatic. This loss of informal authority is a genuine cost for that person.

Additional work during transition. In any system change, there is a period where staff are running two systems simultaneously, completing tasks in the new system as required by the implementation, and completing them in the old system because they don’t fully trust the new one yet. This is genuinely more work. Acknowledging this honestly rather than pretending the transition will be seamless builds credibility.

Lack of involvement in the decision. People are more willing to use systems they had input into than systems imposed on them. If the selection and configuration process was entirely management-driven with no user input, don’t be surprised when users treat the system as something done to them rather than for them.

Insufficient training. Underprepared users avoid systems they don’t understand. When using the new system is harder than using the old system or workarounds, the old system wins. Adequate training is not a nice-to-have; it is a core requirement for adoption.

No visible management commitment. If senior management talks about the new system but doesn’t use it, doesn’t reference it in meetings, and doesn’t insist that reporting comes from it rather than the old spreadsheets, the message to the team is that the old way is still acceptable. Management behaviour is the strongest signal about whether change is real.

Strategies That Actually Build Buy-In

Involve Users Before Configuration, Not After

The most effective change management strategy is involving the people who will use the system in defining how it will be configured. Not a symbolic consultation after the decision is made, but genuine input into how the system will handle their specific workflows, what screens they will see, and what the data entry process will look like for their daily tasks.

When someone has contributed to how the system works, they are invested in it working. They also become the informal champions who help their colleagues adopt it. The best people to train their colleagues are the ones who were involved in the configuration, they know the system, they understand the rationale for its design, and their colleagues trust them more than an external trainer.

Be Transparent About What Will Change and What Won’t

Uncertainty creates anxiety. Anxiety produces resistance. The antidote is specific, honest communication about what the new system will change, what it will not change, and what the timeline for change is.

Specific concerns to address directly: Will this system replace my job? The honest answer for most implementations is that it will change the nature of the job but not eliminate it. Staff who spend four hours a day on manual data entry will spend that time on higher-value work instead. Being clear about this is more reassuring than avoiding the question.

Identify and Enable Internal Champions

Every team has people who are early adopters of new tools, curious about technology, and influential with their peers. Identify these people before implementation starts and give them additional involvement, training, and visibility. They become the internal support network that sustains adoption after the implementation team has moved on.

Champions are more effective than management mandates in sustaining adoption. Peer influence is more persuasive than top-down instruction for day-to-day behaviour change.

Remove the Old System Quickly

The biggest adoption killer is keeping the old system available after go-live. If staff can still access the old spreadsheets or the previous system, they will use them when the new system is unfamiliar or frustrating. The ability to fall back to the old way removes the necessity to learn the new way.

The standard advice is to run parallel systems for a period after go-live to catch any data issues. This is operationally prudent, but the parallel period should be as short as possible, two to four weeks rather than three to six months. Set a clear cutover date and communicate it in advance.

Measure and Celebrate Adoption Milestones

Measure system adoption, not just system performance. Track the percentage of transactions going through the new system vs the old method. Track the number of active users. Track the data completeness rate. Celebrate milestones visibly, when 90% of orders are going through the new system in week three, acknowledge it.

Early momentum is self-reinforcing. A team that can see that the change is happening successfully is more motivated to maintain it than a team that doesn’t know whether the transition is on track.

The Management Commitment Test

There is a simple test of whether management commitment to a new system is genuine: in the first management meeting after go-live, does the reporting come from the new system or the old spreadsheets?

If management reverts to the old reporting formats in the first meeting because the new system’s reports aren’t quite right yet, or because it’s easier, or because someone hasn’t had time to set them up, that behaviour sends a clear signal to the entire organisation. The new system is optional.

Genuine commitment means accepting that the new system’s reports will be imperfect at first and working through it in the new system, not reverting to the old one. This is the most important thing management can do in the first 30 days after go-live.