top of page

10 Reasons ERP Best Practice Adoption Fails

Writer: George Pilling
George Pilling
6 days ago
2 min read

Having supported numerous ERP and finance transformation programmes, project success is rarely determined by software selection alone. More often, it is the avoidable organisational and governance challenges that determine whether best practices are successfully adopted.


Here are 10 common causes of failure and how organisations can avoid them.



1. Excessive ERP Customisation

Customisations can become increasingly difficult to manage as ERP systems evolve, particularly in SaaS environments where vendors deliver frequent updates and new AI-driven capabilities. Over time, organisations may face additional testing and maintenance requirements, or discover that new standard functionality has replaced the original customisation altogether.


2. Lack of Organisational Preparation

Successful change starts well before implementation. Clear communication around the purpose of the change, its benefits, and its impact helps prevent rumours and resistance from developing within teams. Early engagement allows employees to better understand and support the journey ahead.


3. Resistance from Key Individuals

Every project encounters sceptics. It's important to invest time in understanding concerns and communicating the benefits of change in a way that is relevant to the individual, their team, and the wider business. Where alignment cannot be achieved, project leadership must ensure that resistance does not impede progress.


4. Insufficient Governance and Control Points

Regular project reviews and governance meetings are essential. They provide visibility of progress, allow risks and issues to be identified early, and help maintain control over timelines, scope, and budget.


5. Inadequate Funding

Projects require realistic budgets and appropriate contingency planning from the outset. Executive sponsorship and effective steering committee governance are critical to managing scope changes, making decisions, and securing additional investment if required.


6. Poor Planning

Strong planning lays the foundation for successful ERP adoption. Pre-project preparation, clear objectives, defined responsibilities, and ongoing project management all contribute to smoother implementations and better outcomes.


7. Failure to Conduct a Post-Implementation Review

Many organisations move straight into business-as-usual activities after go-live and miss a valuable learning opportunity. Post-implementation reviews help identify lessons learned, measure success against objectives, and improve future projects.


8. Inadequate Testing

Testing is one of the most critical activities in any ERP implementation. Comprehensive testing helps identify defects, process gaps, and missing functionality before go-live, reducing the risk of disruption to the business.


9. Lack of Executive Sponsorship

Significant business transformation requires visible support from senior leadership. Without executive sponsorship, projects can lose momentum, struggle to obtain resources, and fail to realise their expected benefits.


10. Too Many Changes at Once

Attempting to implement multiple changes in a short period can overwhelm employees and create uncertainty. This often increases resistance, reduces adoption rates, and ultimately limits the success of the initiative. Organisations should carefully manage the pace of change and ensure users have sufficient support throughout the transition.


Final Thoughts

The success of ERP and best practice adoption programmes is rarely determined by technology alone. More often, success depends on effective planning, governance, communication, leadership, and change management.


By understanding these common pitfalls before embarking on a transformation journey, organisations can significantly improve their chances of success and maximise the value of their ERP investment.


At E-kwip, we regularly see that the organisations achieving the greatest benefits from ERP transformation are those that focus as much on people, processes, and adoption as they do on technology.

 

 
 
bottom of page