However:
- the timing has to be right
- the process in which the person is being trained needs to be stable
- the systems that the person uses after training need to be free of bugs.
The process needs to be stable, otherwise the training may be out-of-date as soon as the trainee walks out the door. And the computer systems need to be bug-free since otherwise the trainees will be unable to distinguish between system issues and their own mistakes. Buggy systems make for noisy feedback which undercuts learning.
Kirkpatrick's training evaluation model can be an invaluable tool for determining whether training has been worthwhile.
It has four levels:
- Reaction of student - what they thought and felt about the training
- Learning - the resulting increase in knowledge or capability
- Behavior - extent of behavior and capability improvement and implementation/application
- Results - the effects on the business or environment resulting from the trainee's performance
The problem is that many training evaluations stop at the first level. I recall going to a training course on change management and there is no doubt that the trainer knew their subject, that it was interesting and informative and that most of those present enjoyed it and gave it good evaluations. Then they went back to their jobs and kept doing things the same way they had previously. The lesson is that the fact that trainees found the training enjoyable and interesting doesn't necessarily mean that it was worthwhile.
It used to be that when a person did training they were given pre-tests and post-tests, the theory being that the difference between their results on the two tests indicated an increase in knowledge. This seems to be out of fashion now, even though it at least had the advantage of showing that some learning had taken place. Without something comparable to this, it isn't clear that any of what was taught has stuck. Some options for measurement could include needing to complete some assessment tasks on the job and the plus in this is that it at least provides an indication of whether anything was remembered once the trainee left the training room. Plus it gets them integrating their learning into performance.
Which brings us to performance: is the person applying what they have learned? This is another area that seldom seems to be followed up except tangentially. In fact, the whole purpose of training in some instances is so that management can claim that the person was trained so that any subsequent deficit in performance is down to the employee not doing their job rather than them not having received the required training (however ill-timed or inadequate it might have been.)
Finally, if the worker did learn and apply what was covered in the training, what difference has this made to the organisation's performance: is work being done faster, more accurately, more effectively, with less waste or less downtime? If not, then the reason could be that the training wasn't properly matched to the organisation's needs and this is important feedback because it points to the need for better analysis before developing and rolling out training.
The bottom line is that training isn't about the trainees feeling good.
It is about the delivery of results and if it fails to deliver then it really wasn't worthwhile. Worse, it was a cost to the organisation without any commensurate benefit.
Resources
Official Site of the Kirkpatrick Model
No comments:
Post a Comment