While starting with a template makes great sense, the template is not a plan in itself. If you are six months from pilot/rollout and these are still empty shells (in SAP terms, this would mean not having Business Process Procedures, or BPPs, in place), you will be scrambling to complete them in time for end-user training. The less time you have to do so, the less accurately they will reflect the real-world processes and procedures and the more problems you will see at post go-live.
Symptom 3: Disappearing Resources
Before every ERP implementation is funded, the organization creates a business case detailing the ROI, output and impact of the system. This document should be the measuring stick by which all decisions are made. By assessing the decision making process as go-live nears, you will often see decisions being made that are solely designed to support meeting development deliverables and not the business objectives.
An example is reallocating resources from the training teams to software project teams with no set plans to replace those resources. We also see end user training being pushed back or, worse, marginalized to a series of task-based interactions that do not provide an understanding of the new business process and when and how they interact within that process. This causes expensive training issues and delays and/or decreases the impact the ERP will have on the business.
Symptom 4: The Legacy Loss
The training needs to clearly describe the bridge from the legacy system to the new process, how it will differ, and why. Assuming end users can move quickly from one system to another, without detailing the specific steps and reasons, is a symptom that the end users are not going to adopt the new system quickly or fully.
Note: there are also morale reasons to do so. By including end users in the new process you are telling them their previous hard work and knowledge is appreciated. And they will open their hearts to better learn the new system.
Symptom 5: Information Overload
We have all sat through this class. The 7-hour "one size fits all" training that provides a good intro and then bores us for 5 hours until we hit the 20 minutes that are relevant and valuable to our specific requirements.
Not only is it unproductive to have end users spend seven hours gaining what is really only 20-30 minutes of value, they also have to determine what portion of the training is relevant. Should they attempt to understand all this data, they will likely get only a vague impression of how to accomplish their unique tasks.
Symptom 6: Screens vs. Substance
