Difference between revisions of "Lessons learned"

From NKM WIKIDOC
Jump to: navigation, search
(Common pitfalls)
(Success factors)
 
(32 intermediate revisions by 3 users not shown)
Line 11: Line 11:
 
<!-- '''Source: ''' [[Planning and Execution of Knowledge Management Assist Missions for Nuclear Organizations]] -->
 
<!-- '''Source: ''' [[Planning and Execution of Knowledge Management Assist Missions for Nuclear Organizations]] -->
 
== Purpose and benefit ==
 
== Purpose and benefit ==
Lessons learned from a project or from a certain process 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.
+
Lessons learned from a certain action or event or incident have the benefit to help define an action plan how to improve the action to be more effective and avoid failures or incidents in the future. They are often considered a key component of, and ongoing precursor to, effective risk management.
  
 
== Description==
 
== 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.
+
Lessons learned often reflect on ‘what was done right’, ‘what should be done differently’, 'what didn't work as expected and why', and ‘how to improve the process or action to be more effective in the future’. In the nuclear industry, operating experience feedback is an example of an applied lessons learned programme. In many cases the lessons learned report is the outcome of the [[After action review|after action review]], but also other procedures can be used (informal discussions, personal interviews, consulting external experts, [[Peer assist|peer assists]] etc.).
  
 
== Variations ==
 
== Variations ==
Lorem ipsum
+
Because of the large variety of nuclear organizations and of the large variety of events and actions that may occur in them, no universal form of the lessons learned report can be given.
 +
 
 +
However, in all cases it is advisable that the findings are recorded in a written form and inserted in the knowledge 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 ==
 
== Implementation guidelines ==
* Organize a lessons learned meeting after a completed larger process or project or incident.
+
* Get the findings in writing, and record all successes and failures together with all important parameters and circumstances.  
* Plan the lessons learned meeting carefully, and assign enough time for the meeting to discuss all aspects - positive and negative - of the process.
+
* Include all opinion of all involved staff members in the report, even if they seem to contradict. People at different positions may see the same event from different points of view. 
* Invite all involved members of the team, and listen openly their views.
+
* Create also an action plan. The idea is to learn from the successes and failures not only to document them. The action plan is critical and should not be overlooked/disregarded, the action plan helps to ensure that learning and improvement takes place.
* Get it in writing, and record all successes and failures together with all important parameters and circumstances.  
+
* See also the Implementation part of the [[After action review| after action review]].
* Create an action plan. The idea is to learn from the successes and failures not only to document them.
+
  
== Sucess factors ==
+
== Success factors ==
* The date of the lessons learned meeting should be quite close to the termination of the process, so that all information be still live and available.
+
* Make the lessons learned report concise and concentrate on the most important findings.  
* 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.
* Make the outcome of the lessons learned meeting available to those who might profit from it. This is especially important in the nuclear industry, where the operators of NPPs should learn from each-others operating experiences.
+
* Implementing the action plan and a follow-up to ensure that the action(s) have been implemented is critical.
 +
* See also the Success factors part of the [[After action review|after action review]].
  
 
== Common pitfalls ==
 
== Common pitfalls ==
 
<!-- '''Source: ''' [[Planning and Execution of Knowledge Management Assist Missions for Nuclear Organizations]] -->
 
<!-- '''Source: ''' [[Planning and Execution of Knowledge Management Assist Missions for Nuclear Organizations]] -->
* Not taking the lessons learned meeting seriously. Either it will not be organized at all or it will not be prepared well
+
* The lessons learned report is not taken seriously. Either there is no occasion at all to capture the lessons learned from an action or event, or it will not be prepared well.
* The meeting will be organized only at a much later time than the relevant process was finished. This leads to a substantial loss of the relevant information.
+
* The lessons learned report does not contain all the relevant informations, since the capturing event was organized only at a much later time than the relevant process or event was finished, and some of the information have already been lost.
* There is not enough time assigned to the evaluation meeting. Not all aspects could be discussed, and not all opinion could be expressed.  
+
* Not all aspects of the case is contained in the report, since not all opinions could be expressed. This can occur because either the time allocated for the discussion was not sufficient, or not all involved members of the team were invited to the discussion. In both cases the lessons learned report is superficial or biased and is of little use.  
* 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 on the lessons learned.  
+
* The lessons learned report does not reflect the true feelings and thoughts of the involved team members, since they were concerned to express their personal opinion honestly, because of the general blaming attitude of the management.  
* 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.
+
* The lessons learned 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.  
* 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 either.  
+
* No action plan will be designed and included in the lessons learned report, to improve the performance in the future.
* After the learned lessons are discussed there is not action plan to improve the performance in the future.
+
* Although lessons learned are written down and stored, but they are not communicated, and they are not made available to possible interested partners or staff members.
* The findings of the lessons learned session is written down, they are stored, but they are not communicated, and are not made available to possible interested partners or staff members.
+
* See also the Common pitfalls part of the [[After action review|after action review]].
  
 
==Related articles==
 
==Related articles==
 +
[[After action review]]
 +
 
[[Learning]]
 
[[Learning]]
  

Latest revision as of 10:21, 10 March 2016


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 certain action or event or incident have the benefit to help define an action plan how to improve the action to be more effective and avoid failures or incidents 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’, 'what didn't work as expected and why', and ‘how to improve the process or action to be more effective in the future’. In the nuclear industry, operating experience feedback is an example of an applied lessons learned programme. In many cases the lessons learned report is the outcome of the after action review, but also other procedures can be used (informal discussions, personal interviews, consulting external experts, peer assists etc.).

Variations

Because of the large variety of nuclear organizations and of the large variety of events and actions that may occur in them, no universal form of the lessons learned report can be given.

However, in all cases it is advisable that the findings are recorded in a written form and inserted in the knowledge 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.
  • Include all opinion of all involved staff members in the report, even if they seem to contradict. People at different positions may see the same event from different points of view.
  • Create also an action plan. The idea is to learn from the successes and failures not only to document them. The action plan is critical and should not be overlooked/disregarded, the action plan helps to ensure that learning and improvement takes place.
  • See also the Implementation part of the after action review.

Success factors

  • Make the lessons learned report concise and concentrate on the most important findings.
  • 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.
  • Implementing the action plan and a follow-up to ensure that the action(s) have been implemented is critical.
  • See also the Success factors part of the after action review.

Common pitfalls

  • The lessons learned report is not taken seriously. Either there is no occasion at all to capture the lessons learned from an action or event, or it will not be prepared well.
  • The lessons learned report does not contain all the relevant informations, since the capturing event was organized only at a much later time than the relevant process or event was finished, and some of the information have already been lost.
  • Not all aspects of the case is contained in the report, since not all opinions could be expressed. This can occur because either the time allocated for the discussion was not sufficient, or not all involved members of the team were invited to the discussion. In both cases the lessons learned report is superficial or biased and is of little use.
  • The lessons learned report does not reflect the true feelings and thoughts of the involved team members, since they were concerned to express their personal opinion honestly, because of the general blaming attitude of the management.
  • The lessons learned 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.
  • No action plan will be designed and included in the lessons learned report, to improve the performance in the future.
  • Although lessons learned 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.

Related articles

After action review

Learning

Best practice

Learning between projects

Peer assist