Lack of Training
Monday, October 20th, 2008Identifying deep, root causes of poor performance is one of the key tasks that project teams encounter as they work to improve process or product performance. In my experience, the most commonly identified root cause - by far - is “lack of training.” Unfortunately, “lack of training” is not a root cause; instead, it points to a solution.
The problem with listing a potential solution as a root cause is that it can lead to the implementation of something that doesn’t significantly impact the performance of the process - “more training,” for instance, without exploring other solutions that would lead to improvement. I am willing to bet that as a reader of this blog, you have seen resources (time and money) spent on training, with little or no resulting improvement.
To see the impact that limiting solution options too early can have, let’s first identify the true root cause. When someone says, “The problem is caused by a lack of training,” I ask, “So why would additional training help?” The answer typically is, “It would help ensure they have the proper skills and understanding to do the job.” There’s the root cause - insufficient skills and understanding, rather than a lack of training.
Now that the root cause has been identified, are there more solution options beyond just training? How about simplifying the process or product to lower the level of skills required? How about implementing mistake-proofing methods to make it impossible to do something incorrectly? How about implementing clear, easily understandable visual work instructions that can be used as a guide when doing the work? Etc. Etc.
I’m not saying that training is never an appropriate solution, but look at the additional options that open up when you first start with a root cause, rather than a preconceived solution.






