When listening to fears and concerns about ERP solutions, implementation is usually on the top of most lists. Yes, it can be daunting, but it is the cornerstone of the overall project. So why do implementations fail? Below is our countdown of the most common ERP implementation errors and how to avoid them.
5) Don’t “Train the Trainer”
Proper implementation of an ERP solution takes a full-court press from your company. Many times companies simply underestimate what it takes to get it done. The “train the trainer” approach to cut costs can get you in trouble. Having only one or two key people learn the system, so they can train other employees is a recipe for disaster. All users should have an opportunity to work directly with the vendor’s implementation team. Meet with your vendor to get a clear understanding of what it takes to fully implement the system so you can reap the benefits throughout your organization.
Also, avoid the temptation to train your personnel by department; such as having customer service train from 8:00 to noon on Monday and then have purchasing take over after lunch. These sessions usually just devolve into a demo rather than interactive training. But worse, trainees have no sense of how the software integrates nor how they are affected by events upstream and how they impact those who are downstream.
4) Underestimating Implementation Days Needed
In order to keep costs down so they can close the deal, some vendors suggest you purchase fewer implementation days than you really need. This leaves you with buyer’s remorse when you learn you must spend more than you expected in order to fully exploit the software – not to mention the cost of a delayed or failed implementation. Vendors will never guarantee they can get the implementation done with the days they quote, but press them to be up front with what it really takes to get their system up and running throughout your shop. Ask for specific examples of other similar projects and their implementation durations – and insist on references.
3) Resistance to Change
Culture shock is possibly the most difficult hurdle in an ERP rollout. Employees are resistant to change for a myriad of reasons; usually rooted in some type of fear. They may be worried that their jobs are in jeopardy or that they will be unable to learn the new system. Some may just be afraid of computers. Whatever the reasons; education is the answer. Try to let them see how the new system will Manufacturing Engineer Salary California benefit them personally. They may be less stressed because all the information they need is readily available; they may be less exposed to failure because they have greater control and visibility or they may simply have time to organize a meaningful thought rather than just run from fire to fire. Once they see how their own lives will be easier, they will actually be excited about the new system.
2) Choosing the Wrong …
General
