Difference between revisions of "Lessons learned"
(→Common pitfalls) |
(→Common pitfalls) |
||
| Line 45: | Line 45: | ||
* After the lessons learned from the event are discussed, no action plan will be designed to improve the performance in the future. | * After the lessons learned from the event are discussed, no action plan will be designed to improve the performance in the future. | ||
* Although the findings of the lessons learned session are written down and stored, but they are not communicated, and they are not made available to possible interested partners or staff members. | * Although the findings of the lessons learned session are written down and stored, but they are not communicated, and they are not made available to possible interested partners or staff members. | ||
| − | * See also the Common | + | * See also the Common pitfalls part of the [[After action review|after action review]]. |
==Related articles== | ==Related articles== | ||
Revision as of 12:48, 9 March 2016
Contents
Definition
Concise descriptions of knowledge derived from experiences that can be communicated through mechanisms such as storytelling, debriefing etc., or summarized in databases.
Purpose and benefit
Lessons learned from a project or from a certain action show in a concise form what was done right, what should be done differently and how to improve the process and product to be more effective in the future. They are often considered a key component of, and ongoing precursor to, effective risk management.
Description
Lessons learned often reflect on ‘what was done right’, ‘what should be done differently’, and ‘how to improve the process and product to be more effective in the future’. In the nuclear industry, operating experience feedback is an example of an applied lessons learned programme. Usually they are the outcome of the after action review.
Variations
Because of the large variety of nuclear organizations and of the large variety of events and actions that may occur in them, no unique form of the lessons learned report can be given.
However, in all cases it is advisable that the findings be recorded in a written form and inserted in the knowledge data base of the organization.
The reports should contain not only the failures but also the successes of the evaluated action, together with all relevant information available. Also, all opinion of the involved staff members should be recorded and included in the lessons learned report, even if they are partly contradictory.
The report should contain also an action plan how to use the lessons learned to improve the performance.
Implementation guidelines
- Get the findings in writing, and record all successes and failures together with all important parameters and circumstances.
- Create also an action plan. The idea is to learn from the successes and failures not only to document them.
- See also the Implementation part of the after action review.
Sucess factors
- Avoid that the team feels that the meeting is about punishment or assigning blame. The management has to develop a reputation for listening openly to input and not punishing people for being honest.
- Make the lessons learned report available to those who might profit from it. This is especially important in the nuclear industry, where the operators of NPPs (and also other nuclear organizations) should learn from each-others operating experiences.
- See also the Success factors part of the after action review.
Common pitfalls
- The lessons learned meeting is not taken seriously. Either it will not be organized at all or it will not be prepared well.
- The meeting will be organized only at a much later time than the relevant process or event was finished. This leads to a substantial loss of the relevant information.
- There is not enough time assigned to the evaluation meeting. Not all aspects could be discussed, and not all opinions could be expressed.
- Not every involved member of the team was invited. As a result, the final statements could be biased, not every point of view could be included in the final report.
- The lessons learned meeting has turned into a 'finding someone to blame' session. This only does not help to learn from the lessons learned, but also creates an atmosphere of suspicion and fear inside the organization, which prevents expressing honest opinion in the future.
- The results of the lessons learned meeting are not recorded in written form. Therefore they cannot be included in the knowledge base of the organization, and cannot be communicated to other possibly interested partners.
- After the lessons learned from the event are discussed, no action plan will be designed to improve the performance in the future.
- Although the findings of the lessons learned session are written down and stored, but they are not communicated, and they are not made available to possible interested partners or staff members.
- See also the Common pitfalls part of the after action review.
