Tuesday, July 15, 2008

Problems with software training

When a business buys new software, they require training on the use of the software. Unfortunately, most of this is generic. They tell you everything that you need to know if you want to use all of the features and functions of the software. Most of this is forgotten by the students, as they return to their jobs and just try to get their jobs done. In addition, much of the online help is virtually useless, as you can find the information only if you know what you are looking for. The terminology is often totally foreign to business people.

I like to refer to this training as trying to drink from a firehose.

When installing new software, we need to recognize that people's lives are being disrupted. Everything they know (and love?) is changing. They don't know how to do their jobs anymore. They become unproductive and frustrated. Until they are comfortable in the new environment, they simply want to know how to do what they were doing with the new software. Once they are comfortable, they may be ready to learn new things.

We can't train them on what they need to know unless we understand their business, how it works and how the software is being used within the business. Even though the software is standard, every company uses it differently. So we should always start with the business process. What is it within this specific business? What is imprortant within this specific business? How will the software be used to address the process needs? Now train the staff to do that with the software.

We can follow up that training with a more detailed set once things are stable. This training should also be focused on how the business process can be improved by using more features and functions in the software.

No comments: