10 November 2026 | 5 minute read
A proven ERP solution doesn't guarantee a confident workforce. When previous implementations have failed to deliver, rebuilding trust becomes as important as getting the technology right.
Imagine being asked to invest your time and energy in another major technology implementation after the last attempt failed to deliver.
You're told the new implementation partner is experienced. The solution is proven. The project has a robust methodology, clear governance and a credible delivery plan.
All reassuring.
But you've heard versions of this before.
So when the project team asks you to attend workshops, validate processes, test functionality or prepare your team for change, you hesitate.
Not necessarily because you oppose the transformation. You may understand exactly why the organisation needs it.
You're simply not ready to invest again until you have some confidence that this time will be different. Knowing and understanding that is important.
A proven solution doesn't automatically create confidence
ERP implementations often bring together two groups with very different starting points.
The implementation team may have delivered the same technology successfully across multiple organisations. They understand the system, know the common implementation risks and have confidence in their approach.
The client organisation brings something different: its own history.
People remember previous commitments, implementation challenges, disrupted priorities and the effort invested in projects that didn't deliver what was expected.
These experiences shape how they interpret the next project.
What looks like a straightforward request for engagement to the implementation team can feel like another demand on already stretched people who are unsure whether their contribution will lead anywhere.
Neither perspective is necessarily unreasonable, but when the difference isn't acknowledged, it creates tension.
Engagement is not the same as trust
We often measure change engagement through participation.
How many people attended the workshop? Have stakeholders been consulted? Are business representatives completing their assigned activities?
These measures are useful, but they don't necessarily tell us whether confidence is growing.
Someone can attend every workshop and still believe the project will fail.
Equally, someone who challenges the proposed solution may be demonstrating genuine commitment to getting the implementation right.
The more useful question is not simply whether people are participating. It's whether their experience of the project is giving them reason to trust it.
That trust develops through what people observe.
Are commitments followed through? Are difficult questions answered directly? Does feedback influence decisions? Are risks acknowledged early? Can people see how their contribution affects the outcome?
Communication matters, but confidence is built through consistent evidence.
The cost of asking people to believe too early
When an organisation has experienced unsuccessful implementations, there can be pressure to rebuild enthusiasm quickly.
Leaders want visible momentum. Project teams need access to business expertise. Sponsors want assurance that the organisation is getting behind the change.
But asking people to demonstrate confidence before they've seen evidence can backfire.
It risks treating understandable caution as a behavioural problem to overcome.
And it can create the appearance of engagement without the commitment needed to make the transformation work.
The consequences may not become obvious until later, when the organisation needs people to test thoroughly, make difficult process decisions, challenge assumptions and prepare their teams to operate differently.
This is where ERP change management needs to do more than generate awareness or encourage participation.
It needs to help create the conditions in which confidence can be rebuilt.
What leaders can do differently
Three leadership disciplines become particularly important.
1. Acknowledge the history without allowing it to define the future.
People don't need another assurance that everything will be different this time. They need to understand what has actually changed. That might include the delivery approach, governance, decision rights, resourcing or how risks will be escalated and resolved. Be specific about what the organisation has learned and how those lessons are influencing the current implementation.
2. Make progress visible through evidence, not optimism.
Confidence grows when people can see commitments being met and issues being addressed. Demonstrate how the solution works in the organisation's context and close feedback loops and show how business input is shaping decisions. Importantly, don't confuse demonstrating technical functionality with proving operational readiness. Both matter, but they represent different mindsets.
3. Treat trust as a leadership responsibility, not a communications deliverable.
The project team can demonstrate capability and create opportunities for engagement. But organisational leaders influence whether people believe their time and effort will be respected. Sponsors and business leaders need to reinforce priorities, make timely decisions, address competing demands and demonstrate that the transformation matters beyond the project reporting cycle. Trust is strengthened when leadership behaviour matches the commitments being made.
Go-live is a milestone. Confidence is part of what makes the benefits possible.
Ultimately, an ERP implementation is not successful simply because the technology goes live.
The organisation must be able to use the system effectively, sustain new ways of working and realise the operational and financial benefits that justified the investment.
That requires people to contribute their expertise during implementation, challenge what doesn't work and develop confidence in the new processes before they become business as usual. It requires them to adopt and sustain new ways of doing their work.
For organisations with a difficult implementation history, rebuilding that confidence is not an optional engagement activity, it is part of managing the risk to benefits realisation.
A proven system can demonstrate that the technology works. But it takes consistent delivery, credible leadership and evidence of progress to convince people it will work here. And without that confidence, the benefits the organisation invested in may remain out of reach.
Key Takeaways
Employee scepticism isn't necessarily resistance. Previous implementation failures can make people understandably cautious about investing their time and energy again.
Technical credibility and organisational trust are different things. An experienced project team may know the solution works, but employees need evidence that it will work in their environment.
Participation doesn't equal confidence. Workshop attendance and completed change activities tell us little about whether people believe the implementation will succeed.
Trust is built through delivery, not reassurance. Visible progress, honest communication, closed feedback loops and consistent leadership behaviour matter more than promises.
Trust affects benefits realisation. When confidence is low, the organisation risks losing the meaningful participation, challenge and ownership needed to make the system deliver value.
Frequently Asked Questions
Why do employees resist ERP implementations?
What appears to be resistance may reflect previous implementation failures, competing operational demands, uncertainty about new processes or a lack of confidence in project delivery. Employees who have invested significant effort in unsuccessful projects may be reluctant to commit again without credible evidence that things will be different. Effective ERP change management starts by understanding these concerns rather than treating reluctance as a problem to overcome.
How can leaders rebuild trust during an ERP transformation?
Trust develops when employees see consistent evidence that the project is delivering on its commitments. Leaders can strengthen confidence by acknowledging previous implementation challenges, explaining what has changed, involving employees in meaningful decisions and demonstrating how feedback influences the solution. Executive sponsors also need to resolve competing priorities and ensure the organisation has the capacity to participate effectively. Trust grows through repeated experience, not simply more communication.
About Louise
Louise Zawada is an executive coach and change consultant based in Perth, Western Australia. She works on the leadership side of execution.
After twenty years inside complex organisations, she’s watched sound strategies stall for reasons that never show up in the project plan. Decisions drift or get escalated past where they should sit. Alignment holds in the room and comes apart outside it. Hard conversations wait until they’re expensive. She calls this leadership friction, and her work is to name it, cost it and clear it.
She works with senior leaders, executive teams and sponsors in mining and resources, energy, government, infrastructure and professional services. Usually she arrives when a transformation is already under way and the people side is where it’s getting stuck.
Through Lead Lightly, she writes about decision quality under pressure and the conversations sitting underneath the ones leaders are actually having.
If parts of this felt familiar, the Leadership Friction Calculator gives you a rough sense of what it might be costing. Or get in touch for a private conversation.
