Lessons Learned
Lessons Learned
Introduction and Definition
A lesson is knowledge or understanding gained by experience. The experience may be positive (a best practice), or negative. Successes and failures are both considered sources of lessons. A lesson learned must be significant in that it has impact on the project; valid in that it is factually and technically correct; applicable in that it identifies a specific design, process, or decision; and has the potential to reduce or eliminate future failures and mishaps or reinforces a positive result. Project Managers should familiarize themselves at an early stage with applicable Lessons Learned that may be related to their project, as well as documenting Lessons Learned as the project proceeds.
Purpose
The purpose of a lessons learned activity is to understand what lessons can be used from a particular event and apply as lessons learned as the project moves forward, or may be useful to other projects. The ultimate purpose is to provide information that can increase effectiveness and efficiency, and to build on the experience that has been earned by each completed project. If documented and disseminated properly, lessons learned provide shared ideas for improving work processes, operation, quality, safety and cost effectiveness, etc. and help improve management decision making and worker performance through every phase of a project. They also help future Project Managers avoid similar difficulties.
Documenting Lessons Learned
Lessons learned and best practices should be captured throughout the continuum of a project. Within 90 days of CD-3 approval, up-front project planning and design lessons learned shall be submitted to OPA. Likewise, project execution and facility start-up lessons learned shall be submitted within 90 days of CD-4 approval. In addition, these lessons learned shall simultaneously be submitted to the LBNL institutional lessons learned database.
Directions for adding Lessons Learned to the LBNL database:
Go to: https://www.lbl.gov/a-z-index/l/ and select Lessons Learned and Best Practices Database
Select "Create New Lessons Learned/Best Practice"
Under "Category", choose "Project Management Office"
Under "Event Date" select the date the document was written
Under "Sub category", add selections as appropriate (you must select at least one subcategory and you can select multiple subcategories)
Title: Name of Project and CD phase should be part of title
Discussion: write "See attachment"
Actions to Prevent Recurrence: write "See attachment"
Upload the LL document
Distribution Lists: leave these unchecked
Click "Save", then "Route"
Notes: Emil Nassar should be the default Subject Matter Expert if the Project Management Office is selected as the "Category" (#3, above). The LL submittal will be routed to him for approval, then to LBNL's Institutional Contractor Assurance Office (ICAO) for final approval. After ICAO approval, the LL will be viewable to the LBNL community. A database entry can be edited by the creator after the post has been made public.
DOE G 413.3-11 Project Management Lessons Learned
DOE G 413.3-11 (8-5-2008). Note: Although memorandum DOE N 251.109 (11-9-2011) canceled this guidance, it provides useful information on the lessons learned process.