I run a company called the Knowledgeone Corporation that produces a software application called RecFind 6 that is used to provide records management, document management, workflow, document imaging, email management and general business process management functionality. Every installation is different because we configure RecFind 6 to the exact requirements of each customer. All installations include some form of business process management and many include a reasonable degree of complexity, especially, when integrating to other systems.
We are always proposing to new and existing customers and negotiating contracts and the one item in the pricing summary that is always under attack is training. As well as questioning the need for face to face training, many customers also try to reduce the cost by just training a core group that will then train the rest of the staff who will use the new system.
I try to explain that effective and complete training is fundamental to the success of the project; that training isn’t a cost, it is an investment in success. I rarely win.
I also try to convince my customers of the importance of ongoing training for new releases and new employees but I am rarely successful.
I try to explain that cutting costs on training is a sure fire way to ensure that the project will never be as successful as it could be. I rarely win this argument either.
And finally, I always recommend that an IT person attends the training course because his/her services will be need by the application administrator throughout the year. This rarely happens.
Yet, time after time and in example after example, projects (not just ours) are significantly less successful than they should be because someone in management decided to cut costs by skimping on training; by not training operational staff in how to use the product in the most cost effectively and productive way possible.
If you skimp on training you are almost certainly dooming your project to failure.
Lack of knowledge on how to best use a product is an insidious cancer. The project may begin with a big bang and lots of congratulations but deep within your organization the cancer has already started to grow. “I don’t like this product.” “This product is too hard to use.” “I can’t find anything with this product.” “My staff don’t understand this product.”
By year two, many people and departments simply don’t use the product any more. By year three there is a concerted push to find a replacement for this product that “is too hard to use. No one understands it.” The replacement project manager or application owner, who hasn’t been trained, is unable to address the complaints and soon also decides that the problem is with the product. It would be a bad career move to decide anything else.
In year four the organization begins looking for a replacement product. In year five, at great expense they select a replacement product and then lower costs by skimping on training. The cycle starts again.
If you skimp on training and re-training your project is doomed to failure.
How many expensive failures does it take before we learn the lesson?
Training is an investment in productivity, not a cost.