Tuesday, 31 January 2012
There are generally two types of actions that come out of lessons learned reviews.
The first is an action to notify others, so that they can become aware of the lessons.
The second is an action to make a change to process, policy or procedure as a result of the lessons.
For example, a project may have identified a problem with a particular type of equipment from a particular supplier. Let’s call it the XMV valve seal, from XMF ltd. The first action would be to notify all operations that there is a problem with the XFS Vale seal. Any operation using this seal should consider themselves notified, and if they are smart, they will check these valve seals, see if they have the same problem, and change them. The second action would be to remove the XFS value seal from the list of preferred equipment, and to request a response from the XMF ltd concerning how they will address the problem.
Both of these actions are probably needed, but it is only the second type of action that will avoid the problem recurring in future.
Unfortunately most of the lesson-learning systems we are asked to review never deal with the second type of action – only the first.
Posted by Nick Milton at 07:00