Skip to main content

Lessons Learned

What is Lessons Learned? Definition and meaning

Lessons Learned, German for “lesson learned”, is a term that originates from project management. It defines the acquisition of knowledge and insights gained during practical work on projects, which is then also documented. The goal of Lessons Learned is to learn from experiences and mistakes in order to make better use of these insights in the future.

Process of Lessons Learned

The process of Lessons Learned usually takes place in three phases:

  1. Lessons Identified:

    • Lessons Identified refers to the recognition and recording of problems, intentions and mistakes.
  2. Lessons Analyzed:

    • Lessons Analyzed means the analysis of these findings from Lessons Identified. Why did this not work? Under what conditions did this not work?
  3. Lessons Learned:

    • Lessons Learned stands for the result of what the organisation has learned from the situation. This is finally documented so that others affected are not confronted with the same situation in the future.

Documentation of Lessons Learned

The documentation of the lesson learned is best done in the form of checklists, worked-out document templates such as quality management reports, or software tools that support the project process step by step.

At a certain point in time, these Lessons Learned experiences should then be brought together, identified and analysed. This works, for example, in the project review, i.e. after the completion of a process or project, or in the retrospective once a sprint has been carried out in Scrum.

Frequently asked questions

What does Lessons Learned mean?
Lessons Learned, German for “lesson learned”, comes from project management and refers to the knowledge that arises during hands-on project work and is documented. In this way teams learn from experiences and mistakes for future projects.
How does the Lessons Learned process work?
The process usually falls into three phases: Lessons Identified (recognising and recording problems and mistakes), Lessons Analyzed (analysing these findings) and Lessons Learned (capturing the result so that others do not run into the same situation again).
How are lessons learned documented?
Ideally in the form of checklists, worked-out document templates or software tools that guide the project process step by step. Structured project documentation captures the findings and makes them usable in the project review or the retrospective.