Lessons from ERP Software Failures
Eric Kimberling
Technology-Agnostic Digital Transformation Expert | ERP, Human Capital, Business Intelligence, and Supply Chain | Change Management | Expert Witness | Speaker | Author | Tech Influencer | S/4HANA | D365 | Oracle ERP
My career has been deeply intertwined with guiding businesses through the often turbulent waters of digital transformations, with a particular focus on ERP (Enterprise Resource Planning) system implementations. These systems, designed to integrate and streamline all major functions of a business, can be revolutionary when successfully implemented. Yet, they are notorious for their high rates of challenges and failures.
In this article, I will share insights into the common pitfalls of ERP projects and provide detailed strategies for navigating these complex initiatives successfully. Below is a summary from my latest podcast episode, which you can watch in full here:
Understanding ERP Failures: Insights from an Expert Witness
In my extensive experience serving as an expert witness in ERP-related court cases, I've collaborated closely with Scott Janke, Ph.D. , Director of Strategy and Transformation at Third Stage Consulting Group . Together, we've analyzed numerous ERP failures to understand their root causes and testify about them in court. This unique vantage point has given us a comprehensive understanding of what goes wrong and why.
Project Mismanagement and Poor Planning: One prominent theme in ERP failures is the lack of adequate project management and strategic planning. Scott recalls a situation involving a large manufacturing firm that embarked on an ERP implementation intended to replace a 30-year-old custom system. The company underestimated the complexity involved in configuring the new ERP to match their deeply ingrained processes.
This misalignment between their legacy practices and the new system's capabilities led to significant operational disruptions when the new system couldn't perform as expected right out of the box. The failure here wasn’t due to the technology per se but rather to a misalignment of expectations and a lack of robust planning that should define clear, achievable goals.
Poor Documentation and Communication: Another critical issue that often leads to ERP setbacks is the insufficient documentation and communication throughout the implementation process. In another instance, a healthcare provider implemented an ERP system without maintaining comprehensive documentation. As the project progressed, this lack of detailed records made it increasingly difficult to align the evolving system configuration with the initial strategic objectives, resulting in significant discrepancies between expected and delivered functionalities.
Strategies for Mitigating Risks in ERP Implementations
Drawing from these lessons, Scott and I have identified several strategies that are crucial for mitigating risks associated with ERP implementations. These strategies are not just theoretical but are backed by real-life examples and experiences from the field.
领英推荐
1. Detailed Planning and Requirements Definition: Before initiating an ERP project, it is critical to conduct a thorough analysis of business needs and how the ERP system can meet these needs. This step should result in a comprehensive documentation that acts as a blueprint throughout the project lifecycle. For example, a retail chain we worked with benefited immensely from spending several months in the planning phase, clearly outlining each department's needs which informed the customization of their ERP system. This upfront investment in detailed planning helped prevent scope creep and kept the project aligned with the business’s core objectives.
2. Engagement and Alignment Among Stakeholders: Ensuring all key stakeholders are engaged and have a unified understanding of the project's goals is vital. This engagement should span from C-suite executives to end users. In one successful project I led, regular workshops and meetings were held to keep all stakeholders informed and involved in decision-making processes, which significantly enhanced project buy-in and reduced resistance to the new system.
3. Strong Governance and Oversight: Robust governance structures are essential for maintaining project alignment and accountability. This involves setting up a governance committee that includes members from different areas of the business who meet regularly to review project progress and make strategic decisions. For instance, during a complex ERP implementation for a multinational corporation, we established a multi-tiered governance structure that facilitated timely decision-making, which was crucial for the project's success.
4. External Expertise: Leveraging expertise from external consultants who specialize in ERP implementations can provide the necessary guidance and an impartial perspective often needed to navigate project complexities. A case in point is a technology firm that, recognizing their lack of in-house ERP experience, engaged our services from the project's inception through to post-go-live support, ensuring they had expert guidance every step of the way.
5. Effective Change Management: Given that ERP implementations are as much about people as they are about technology, effective change management is critical. This includes comprehensive training programs, regular communication updates, and support structures to help staff adapt to new systems and processes. For example, a professional services firm we worked with implemented a 'super user' program, where selected employees were trained extensively on the new ERP system ahead of the rest of the staff. These super users then acted as on-the-ground change agents, facilitating a smoother transition and deeper acceptance of the new system across the organization.
Conclusion
Implementing an ERP system is a transformative but challenging journey. The potential for operational revolutionization is significant, but the path is fraught with potential pitfalls. By understanding these challenges—through detailed planning, stakeholder engagement, strong governance, leveraging external expertise, and effective change management—organizations can vastly increase their chances of a successful ERP transformation.
To learn more, you can watch the full interview with Scott and I in my most recent podcast episode. You can see that episode here .
If you’re considering an ERP project or are in the midst of one and facing challenges, feel free to reach out. My team and I at Third Stage Consulting are here to help guide you through to a successful transformation. Contact us here to brainstorm ideas on how to make your ERP implementation more successful.
Software company Investor and Advisor
6 个月The ERP era ended several years ago Eric Kimberling. My advice to any exec team whose CIO presents a proposal for a new ERP suite is to have him or her immediately escorted from the building. Don't believe the lies about comprehensive, integrated suites, unified data models, consistent enterprise-wide processes, and so on. The future is more modular, based on a few platforms that are leaders in their specialist area. Some may come from SAP, Oracle, etc but most should not. Once you embrace this future vision you can start a digital transformation program that gradually replaces the least effective legacy systems, and leaves the better ones in place for years, if not for ever.
CEO @ XPERIX INC. | IT Program Management, Digital Engineering, Sustainable Innovation, Digital Transformation, Industry 4.0
6 个月Eric Kimberling Excellent summary of the key failure points in these projects. Even in the best of projects it can feel like a tornado while you are constantly aligning goals to solution capabilities to technical expertise to highlighting incremental progress toward goals. Doing it well keeps the tornado moving furiously forward toward the goals.
Strategic Advisor to the C-Suite ? Business Transformation Expert
6 个月Following Eric Kimberly is like reading your own business autobiography, written by someone else. I remember my first SAP interview where I was asked to rescue a distressed implementation. I was asked to give an overview of my experience and expertise of SAP and which specific modules I was most familiar with. My answer..... "I can spell it". The room fell silent for what seemed like forever and the next question was, "why are you in this interview"? My answer..... " I have a reputation for being able to move the business needle forward, enabling the correct business processes with the right technology when and where it needs to be applied in order to meet the overall business objectives at hand. "I was asked to come speak to you folks.". The CIO from the client was secretly and silently listening to these interviews and I guess he liked my answer. That started a very good relationship resulting in a successful implementation once we got the truck out of the ditch it was currently in. However I "type-casted" myself into these type of rescue missions and although it provided some good job security over several years, walking into these repeating hostile environments got old after awhile.
I make business processes seamless
6 个月Eric Kimberling couldn't agree more. Often, software providers are focused on selling a solution vs. solving a problem and those are two different things. Companies risk a rocky implementation when they are focused in on the solution they were sold vs. having clear documented process on the problem they need solved.
Strategic Advisor/Analyst Specializing in Emerging AI Tech, Sales and Marketing (Procurement) - A Trusted Voice in procurement and supply chain
6 个月What made your post jump off the page, Eric Kimberling is that we are still talking about ERP failures in 2024. Here is a link to a white paper I wrote for the CATA Alliance in 2008 - https://bit.ly/4aIT4j2 The list of organizations in the public and private sectors that struggled with their ERP initiatives in the early 2000s reads like a Who's Who of the business world. Again, this was more than 20 years ago. Why is it still an issue today, or maybe a better question is if it is, in fact, still an issue. This past week, I read two posts talking about relational contracting. The first was by Kate Vitasek - https://bit.ly/4dqiWSj The second post is by Andy Akrouche MBA, RCCM-I, CSM - https://bit.ly/3JIqxOK I have been in high-tech and procurement for over 40 years and have seen much history. The archives for my Procurement Insights blog alone consist of over 2,000 articles. That does not include the countless white papers and ghostwritten articles for senior leaders from both the practitioner and provider sides. Once again, I will return to the question: WHY, after all these decades, are we still talking about ERP failures? David Loseby Dr. Thierry Fausten John Powell Tim Cummins Martin Medforth Jane Lynch Duncan Jones