ERP gone bad: Lessons from real-world failures

FREE

Become An Insider

Sign up now and get free access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content from the best tech brands on the Internet: CIO, CSO, Computerworld, InfoWorld, IT World and Network World Learn more.

Spectacular flameouts have much to teach managers about the right way to run projects

ERP projects are among the most critical efforts IT ever undertakes, as they touch almost every part of essential business operations and are complex technically. Not surprisingly, some fail -- spectacularly. Although ERP has been an enterprise focus for a decade, many companies are still embarking on such efforts, and even more are dealing with ERP redos because of mergers and business changes. Here's what you can learn from the failures of others and put to use on your own ERP projects.

I focus on failed SAP deployments because the details are more commonly available, thanks to SAP's huge presence in large publicly owned enterprises and government, where documents surrounding litigation and major cancelled projects must be made public. But the lessons apply to Oracle and other ERP deployments as well.

What is an ERP project failure? Not mere cost overruns, but an event whose effects are so large that they force a company to restate its earnings or a government entity to cancel a project that is substantially funded.

To continue reading, please begin the free registration process or sign in to your Insider account by entering your email address:
Top 10 Hot Internet of Things Startups
Join the discussion
Be the first to comment on this article. Our Commenting Policies