eLifeMagz.Com » 10 Ways Poor Training Can Cause Your ERP Implementation To Fail

Home > Business > 10 Ways Poor Training Can Cause Your ERP Implementation To Fail

10 Ways Poor Training Can Cause Your ERP Implementation To Fail

October 30th, 2010 elifemagz Leave a comment Go to comments

CIO – When outward practice consultants evaluate ERP implementations already in progress, they deed really ample similar to doctors. First they inquire the patients (in this box the CIO, plan teams, HR and practice leads, etc.) what they are experiencing. Then they poke in to a couple of areas seeking for suffering points and opening issues. They run a couple of tests to see if the aspect symptoms tie in the deeper issues, and go serve to detect underlying practice problems that might not nonetheless have appeared as symptoms to the exposed eye.

To total the analogy: Most of us have a useful “medical symptoms” guide or have bookmarked a Website to help us establish if that suffering in the belly is expected appendicitis, indigestion, or something far worse. The next step is to deliberate your physician. In the same vein, if you think that practice is or could be inspiring the outlay of your ERP implementation, then you should right away meeting a creditable ERP practice consultant.

In the meantime, ponder this your useful guide to ERP Training Symptoms.

For large-scale implementations, such as SAP, practice is frequently finished as segment of the initial proposal. The practice elements are line listed with specifics, suited to any stage on the doing plan (in SAP R/3, this doing plan is called ASAP). And, in the most appropriate case, this includes a plan for customizing the practice plan and relating this to inner and outmost resources.

More often, however, practice is bulleted as a unclear deliverable towards the bottom of the offer and no insights or specifics are supposing as to how practice will be designed, documented or delivered. Even worse, the client organization, that is spending millions of dollars on an ERP doing and, even more importantly, is counting on the outlay of this network to encounter key organizational goals, has no thought what commission of their stipulate is allocated to training, nor of any ROI or metrics reserved to the training.

What can you do? Before you pointer the contract, inquire the integrators to supply allocated bill and resource sum – together with a timeline as to when the plan teams will be lerned and when the end-user practice report will be provided. (Commonly this occurs when defining the business processes.) We moreover rarely suggest you obtain a third-party examination of this practice plan and process. Think of it as a second viewpoint by a specialist, that is always endorsed before any leading operation.

Interviewing the line managers will help establish if the exercise skeleton fairly simulate what the finish users will do on the job, i.e. relating real-world processes and functions, but a rapid evaluation of exercise skeleton frequently shows that this information is not even in place.

While starting with a template creates great sense, the template is not a plan in itself. If you are 6 months from pilot/rollout and these are still void shells (in SAP terms, this would meant not having Business Process Procedures, or BPPs, in place), you will be scrambling to total them in time for end-user training. The reduction time you have to do so, the reduction fairly they will simulate the real-world processes and procedures and the more problems you will see at post go-live.

Before every ERP doing is funded, the group creates a business box detailing the ROI, outlay and effect of the system. This document should be the measuring hang by that all decisions are made. By assessing the preference creation routine as go-live nears, you will frequently see decisions being done that are only written to encouragement meeting growth deliverables and not the business objectives.

An e.g. is reallocating resources from the practice teams to program plan teams with no set skeleton to reinstate those resources. We moreover see finish user practice being pushed back or, worse, marginalized to a array of task-based interactions that do not supply an bargain of the new business routine and when and how they correlate inside of that process. This causes costly practice problems and delays and/or decreases the effect the ERP will have on the business.