Browse Business Software Categories



Confessions of an SAP Expert Witness: SAP Failures

Confessions of an SAP Expert Witness: SAP Failures

Over the past 15 years, I have seen my share of successful ERP implementations. The Panorama team and I have successfully managed a number of complex implementations over the years—ranging from SAP accounting sofware to Oracle E-Business Suite, to Microsoft Dynamics to Tier II ERP implementations—and have the battle scars to show for it. In addition to managing implementations, we’ve also been called upon to provide expert witness testimony and analysis for some of the highest-profile ERP and SAP failures in the industry, many of which you’ve probably heard or read about in recent years.

This experience as an ERP and SAP expert witness has provided many valuable lessons that can help organizations avoid failure and make their projects more successful.

Just as a side note and point of clarification, our independent research shows that there is no correlation between ERP failure rates and the specific ERP software implemented. However, SAP just so happens to have the largest market share in the industry and some of the highest-profile Fortune 500 clients — with pockets deep enough to afford legal battles — so many of the lawsuits we’re hired for relate to SAP implementations. Although most cases we’re involved with have court orders prohibiting Panorama from sharing client-specific details, there are a number of interesting patterns that have emerged during the various cases we’ve supported over the years.

Below are just a few confessions I can share from approximately a dozen cases that I have supported as an SAP expert witness. After all the deep-dive reports, depositions, discussions with attorneys, and jury trials, I can say with confidence that SAP failures typically boil down to a handful of common themes:

SAP failures are rarely about the software

When looking at SAP failures, it is easy to get stuck in discussions about system configuration, Netweaver integration, poorly written customization code, and functionality of the software, but these minute details are typically indicators of deeper root causes. For example, poor project management, lack of organizational change management, and inadequately defined business process workflows are often the causes of some of these symptoms. Of all the expert witness cases we have been involved with to date, not a single one had much to do with the software itself. Instead, it had more to do with how the software was implemented.

SAP failures typically begin early in the sales cycle

Expert witness work is similar to crime scene reconstruction. In the thousands of pages of documentation available in most cases, we have plenty of evidence (and the benefit of hindsight) to be able to assess what went wrong and when and how it did. What we find in most cases is that the stage is set for failure early in the sales cycle — before implementation even begins. Mismanaged expectations, poorly reviewed contracts, ill-defined statements of work, poor project plans and a host of other breakdowns early in a project often create a domino effect of a series of failure points throughout the implementation. For this reason, we often advise our clients that they are actually influencing their likelihood of success or failure just as much in the software selection and implementation planning stages of the projects as they are in the execution phase.

Every SAP failure involves poor organizational change management

Poor organizational change management is the single (and only) issue that we can definitively say was a key contributing factor to each and every expert witness case we’ve been involved with. In each case, user resistance, unclear understanding of business processes, roles and responsibilities, and poor training are just some of the organizational change management issues experienced by the implementing organizations. Too often, organizations who have suffered SAP or ERP failures had implementations that were too focused on technology issues rather than the more important business process, people and organizational issues.

Executive abdication is one of the root causes of SAP failure

The above issues are often symptomatic of even deeper issues at the executive level. Too often, CFOs or CIOs delegate an entire SAP implementation to a project manager or project team with little to no executive involvement, which is a sure-fire recipe for disaster. Executives need to be engaged, make key decisions regarding how their operations will look going forward, and provide oversight and governance of the project. However, too many executives assume they can abdicate themselves of these responsibilities, which often lead to the issues outlined above.

While every ERP implementation and SAP expert witness cases involves various nuances and unique factors, most can be traced to the above four issues. The person or people most responsible for the above failure points vary from case to case, but regardless of who is at fault, they are issues that need to be proactively addressed and managed. Whether you are implementing SAP, Oracle E-Business Suite, Microsoft Dynamics, JD Edwards or any of the multitude of Tier II ERP systems, these lessons can help avoid failure and, more importantly, ensure that your ERP implementation is successful.

[This post originally appeared on Panorama Consulting’s 360 ERP blog and is republished with permission.]

  • Consultant

Panorama Consulting

ERP Consultant, Panorama Consulting Solutions
Independent ERP Expert
Panorama Consulting Solutions is an independent, niche consulting firm specializing in digital transformation and ERP systems expertise for mid- to large-sized private- and public-sector organizations worldwide. One-hundred percent technology agnostic and independent of vendor affiliation, Panorama offers a phased and ...