It’s no secret that ERP implementations fail. In fact, Gartner Research estimates that between 55 to 75 percent of all ERP implementation projects fail. Even if you think that the latter number is a bit high, the thought that over half of these projects may be considered a failure is quite frightening. Not only that, but it is something that you may find yourself having to recover from.
We have talked quite a bit about steps you can take to help prevent your implementation project from failing, but what if you are one of those who are looking around knowing that your ERP solution isn’t working for you? If your organization has come to terms with the fact that you are dealing with a failed implementation, then its time to start planning a comeback. The following steps will get you started on the road to recovery.
Take a long, hard look at your software
Many times, a failed ERP project can be traced back to the software itself. More specifically, the fact that the software you chose wasn’t a good fit for your organization. The recovery team should meet with the team that chose the failed solution so that they can get a perspective on why this particular option was the one purchased. Maybe its just that you need to purchase additional modules or have some customization work done. On the other end of the spectrum, if may be that the software is the wrong choice for a company in your industry or of your size.
Revisit the training program
Take the time to talk to the people using the software to see if they feel that they were adequately trained on how to use the solution in real world situations. Often times, training sessions cover how to do tasks in pristine test environments. If end users don’t know how to react when real world issues arise, then they are certainly going to see this as a failure.
Reexamine your expectations
One common cause of failure is that there are unrealistic expectations set from the beginning. Maybe the features of a more expensive solution are wanted or needed but the budget won’t allow for that application. Another common problem is wanting an implementation to take less time than is actually needed so adequate testing and training is not scheduled into the project plan. In any event, take the time to see if you are setting your solution up for failure by mismanaging expectations from the very beginning.
Get the right team in place
If your project has failed, then make sure your recovery team is both knowledgeable about the solution you are implementing; but also make sure that they are accepting of any changes that are taking place. You don’t want your project to slow down because people are learning on the fly or because they are resisting the change that is taking place.
Failed ERP implementations are costly, however, you lose more by not fixing what is broken. If you find yourself in the position of having to recover from a failed project, make sure to reach out to the right people to get things back on track as quickly as possible.
The post Recovering from a Failed ERP Implementation appeared first on Merit Solutions.
Image may be NSFW.Clik here to view.
