Two decades of experience in one industry is a long time, especially in an area as dynamic as the ERP software industry. Over the years, Panorama has helped many companies succeed in their ERP implementations, watched competitors struggle with the same mistakes time and time again, and helped clean up many messes along the way. Clearly, enterprise software initiatives are not easy, which is why there are both so many ERP failures and so many opportunities to make a positive impact in the industry.
In his book “Outliers,” which is about the variables that make exceptional performers in their respective fields, Malcolm Gladwell suggests that it takes at least 10,000 hours of “practice” to become an expert. Over the last 20 years, I’ve probably accumulated somewhere around three to four times that amount of experience in ERP implementation, selection, project management and benefits realization. When we add the similar experience levels of Panorama’s global team of ERP consultants to the equation, it creates a staggering body of expertise that you simply won’t find anywhere else in the industry.
So what are the lessons of this unparalleled individual and collective experience? Through our extensive research, experience and thought leadership, we have spent quite a bit of time defining these lessons and baking them into our standardized methodology and toolset. While it is difficult to summarize 20 years of experience into a single checklist, below are some of the overarching themes we have encountered over the years:
1. ERP implementations are about business, not technology. We pioneered this concept in our early thought leadership and methodologies and, as evidenced by most of our competitors making the same assertion, it has now become accepted as part of the mainstream. ERP systems change over the years – and they have changed dramatically since I started in the industry in the 1990s – but the business, process and people challenges have remained the same. At the end of the day, SaaS technologies, business intelligence, sweet integration tools and other technical considerations have little to no impact on ERP failures or successes. Instead, it’s the company’s ability to address (or outsource) organizational change management, business process management, project management and planning, and other business considerations that ultimately determine the level of success of an ERP implementation.
2. The devil is in the details of ERP methodologies. It’s one thing to say you have a methodology, but it’s the details (or lack thereof) in those “methodologies” that often kill ERP initiatives. From what we’ve seen in person and in our expert witness work, most ERP consultants claim to have methodologies in place, but very few have them defined and standardized the level of methodological detail necessary for success. While the gun-slinging, heavy-hitting, industry veteran may look good on paper, that individual experience is not nearly as important as the methodologies leveraged by the team. When I look at some of the enormous project failures that we’ve analyzed as ERP expert witnesses, they often involved some of the strongest consultants in the field. The problem was that these consultants lacked detailed, time-tested methodologies to leverage during implementation. And, ultimately, it is their absence that leads to the demise of too many ERP projects.
3. Organizational change management is arguably the #1 ERP critical success factor. It’s tough to identify the single biggest contributor of ERP success or failure, but if we had to make a single declaration, organizational change management is our top choice. You can find the perfect ERP system, design and configure it flawlessly, and test it to your heart’s content – but still have a failure on your hands because your organizational change management was inadequate. Unfortunately, 95-percent or more of ERP consultants focus too much on software configuration and basic system training without mastering the art of organizational change. Our PERFECT Change™ OCM methodology identifies and addresses the most critical components of organizational change management, which goes well-beyond the myopic system-focused approach of most consultants. Learn more about organizational change management in chapter six of my book, An Expert’s Guide to ERP Success (available for free download with registration).
4. Realistic expectations are key. Unrealistic expectations can prove fatal to an ERP initiative. For too many years, ERP consultants, vendors and VARs have oversold and under-delivered, creating expectation gaps that lead to bad decisions. For example, if a $1 billion global manufacturing industry is sold a bill of goods that entails a full implementation across the globe in nine months, we can tell you with 90-percent or more certainty that this project will fail regardless of any other mitigating factors. In these types of situations, CIOs and CFOs end up having to cut short-term costs to meet unrealistic time and budget expectations, which ultimately leads to project failure and increases long-term expenditures.
5. ERP thought leadership makes us better practitioners. We’re considered the world’s leading independent ERP consultants not only because we have hundreds of thousands of hours of collective experience in the field of enterprise solutions, but also because we demonstrate our level of expertise in our thought leadership on a daily basis. When you read our blogs, listen to our podcasts, or attend one of our live or on-demand webinars – and then compare our content to that of our competitors – it is clear that we know what we’re doing. So the two-part question of the day for organizations considering an ERP initiative is: how much does your chosen ERP consulting firm appear to understand ERP systems and do they lead the industry in their knowledge and expertise?
There are many, many more ERP best practices and lessons learned that we will continue sharing with you over the years, but the above five points serve as a good starting point. And given the fact that we are the world’s leading experts on the forefront of our industry, I’m sure these lessons will evolve over time.
Read our client success stories to learn more about Panorama’s experience managing successful ERP implementations in industries as diverse as aerospace & defense, government, manufacturing and consumer services. Also be sure to join me for our Lessons Learned From Failed ERP Implementations webinar on January 24.
loading…
Reflections on Two Decades in the ERP Industry,








“ERP implementations are about business, not technology. ” I agree with this in the context of your message, but isn’t it also true that choosing the solution with the right technlogy can impact success? For example, if the workflows could have been further streamlined had different technology been involved.
loading...
I heartily agree with the first 4 points. But I don’t agree with the 5th point even though I am an aspiring thought leader as well. My point is that just because you can “teach” a subject well, doesn’t mean you can “do” it well. If I were an ERP prospect I would ask to look at as much of the working documents (implementation plan, project charter, scope document) as possible in template form so that I could get a feel for the way the project will be implemented. I’ve seen excellent ERP firms with great track records have terrrible implementations for various of the first 4 reasons – just because you know what not to do does not mean you will not do it. (I offer McDonald’s as proof, most of us know that eating there is not the healthiest choice possible, but we do it anyway).
loading...
Thanks for your comments.
Christine, it’s true that the chosen technology has some impact on ERP success. Panorama’s take, however, is that without the right project management, change management, business process reengineering, etc. a company could implement the most technologically sound ERP system in the world and still have a failed project on their hands. Conversely, with all of those aspects in place, a company could receive a huge amount of benefits from a product that actually isn’t that technologically adroit.
Peter, I agree that teaching isn’t the same as doing. Absolutely. But an organization, like Panorama, that takes the time to assess, analyze and discuss the success factors and failure points of an ERP initiative is an organization that is thinking as well as doing. And that’s what I look for in any third-party firm I evaluate. Anyone can take a canned methodology and try to work through an implementation . . . the question is are they really giving thought to how to make it better? Are they open and transparent about their process and where it came from? And, from a more philosophical standpoint, are they working to share their knowledge to improve the industry on a whole? There is a lot of misinformation out there. And a lot of ERP failures. We are forging a new path.
Thanks again for your comments. It’s great to hear from our readers.
loading...
I agree with Bree’s responses to the comments. Finding the right ERP software is important, but just a small piece of overall ERP success. And as for thought leadership, I think the ability to write and teach takes understanding of best practices to a whole new level. Of course, you want a mix of both experience and thought leadership, but too many consultants focus on one or the other.
Thanks for the great comments and feedback!
loading...
My first reaction to the title of the blog entry was: “is this a cry for help?”
You are providing some good context and practical advice. There are combinations of factors that are at play with successful ERP projects that you have articulated very well.
I have a few comments though that could add some nuances.
The first builds on what Christine pointed out. There is a degree of business fit built into ERP or alternative best-of-breed solutions. The larger to gap, the more the other factors come into play.
The technology argument also plays out when considering how dynamic business change might be. (In our business, Government Resource Planning in developing countries, the pace of change is rapid). Technology can restrict this agility and it’s something that few vendors are good at.
Project Management 101 is often presented as the solution to all ERP implementation ills. Truth is that different business domain and customer situations make certain characteristics of the Project Management Body of Knowledge more critical and requires significant effort. Cultural/organizational change management is, I agree, almost always the number 1 contributor to success and failure. But, capacity building or stakeholder communications can be more critical in certain circumstances.
ERP is highly complicated. Many organizations who perform ERP consulting services are not “independent” in an objective way. They may have Oracle and SAP practices – but the point is, they generate revenue by selling more services, by adding more customization etc. And, there are incentives from large ERP vendors to some of these organizations. So, real independence is important and you can achieve this through thought leadership.
loading...