News, ideas and a software CEO's thoughts from 25 years in the industry.

Lessons From a Failed ERP Implementation

Recently, a site called Proformative.com published a brief article from someone who said they lost their job over a failed ERP implementation. (The original post can be found here.)

The article’s author, who posted anonymously, provided a list of “what I learned from this experience” which we are compelled to reprise here. All ERP projects have “issues.” They’re almost always late (largely unavoidable) and usually over-budget (mostly avoidable) in our real-world experience of many years. That being said, here’s what the poster claimed he/she learned from the experience:

Consider more options earlier

Define the expected benefits earlier and more clearly and then use as a compass going forward and a benchmark of success at the end.

Assume it will cost more and take longer. If it doesn’t, you’re a hero and if it does you’re realistic.

Take in more information from others without a vested interest who have been there and done that before spending any money.

Admit and move on from mistakes faster.

Have a good/committed in-house technology partner before proceeding.

Review the project on a regular basis and often.

Plan on more testing.

Plan on more staff education.

Delegate and verify more.

The author notes and accepts his/her varying degrees of responsibility for some of these elements, and provides a happy ending. After noting that s/he “learned a great deal from this experience… I was offered an assignment helping another company that is embarking on their own ERP implementation.”