The Change Challenge#
ERP implementations fail more often from human factors than technical factors. Users resist change, work around the system, or simply fail to adopt new processes. Understanding change resistance is essential for implementation success.
Why Users Resist Change#
Loss of Competence#
Users who are expert in legacy systems become novices in the new system. This loss of competence is threatening.
Symptoms: Users complain that the new system is "harder" or "slower" even when objective measures show otherwise.
Response: Acknowledge the learning curve. Provide adequate training. Celebrate early adopters.
Loss of Control#
ERP systems standardise processes. Users who had flexibility to handle exceptions may feel constrained.
Symptoms: Complaints about "rigidity" and "bureaucracy." Requests for customisation to restore flexibility.
Response: Explain the business rationale for standardisation. Establish clear exception processes.
Loss of Information Advantage#
ERP systems democratise information. Those who previously had exclusive access may resist.
Symptoms: Hoarding of information outside the system. Delayed data entry. Missing data.
Response: Make transparency expectations explicit. Monitor data quality and timeliness.
Genuine System Problems#
Sometimes resistance reflects genuine problems with the system or its implementation.
Symptoms: Specific, consistent complaints about functionality that doesn't work.
Response: Take user feedback seriously. Distinguish between change resistance and valid concerns.
Change Management Strategies That Work#
Executive Sponsorship#
Sustained, visible executive sponsorship is the strongest predictor of change success.
What works: - Executives actively communicate the vision - Executives participate in training - Executives use the system themselves - Executives address resistance directly
Stakeholder Engagement#
Early and continuous engagement builds ownership.
What works: - Involve key users in requirements and design - Create super-user network across departments - Regular communication about progress - Celebrate milestones and early wins
Training That Works#
Traditional classroom training is often ineffective.
What works: - Role-based training focused on actual tasks - Hands-on practice in realistic scenarios - Just-in-time training close to go-live - Ongoing support after go-live - Multiple learning modalities (visual, auditory, hands-on)
Incentive Alignment#
Align incentives with system adoption.
What works: - Performance metrics that require system use - Recognition for early adopters - Consequences for non-compliance (applied fairly)
Change Management Anti-Patterns#
The Big Bang: Training everyone at once, long before go-live. By the time the system launches, knowledge has faded.
The IT-Led Change: Positioning ERP as an IT project rather than a business transformation.
The Mandate Without Support: Requiring use without providing adequate training and support.
The Ignored Feedback: Soliciting user input but visibly ignoring it.
Measuring Change Readiness#
Before go-live, assess change readiness:
Training completion: Have all users completed training?
Confidence levels: Do users feel prepared?
Process clarity: Do users understand new processes?
Support availability: Do users know where to get help?
NZ/AU Considerations#
Cultural factors: NZ/AU workplace culture may have specific characteristics around change receptiveness.
Geographic distribution: Change management across multiple locations requires additional coordination.
Union environments: Some industries may have union considerations for system change.
Conclusion: Invest in Change#
Technical implementation is necessary but not sufficient. ERP success requires sustained investment in change management. The organisations that underinvest in change are the ones that wonder why their technically successful implementation is considered a failure.