Once we complete a part or a complete project, we come across many situations where we realize we could have done it the other way around or done it better. We can learn from those shortcomings and record them so that they can be used in future projects.
Lessons Learned Registers contain categories of lessons, their descriptions, and the circumstances in which the problem was encountered.
Lessons Learned Registers may contain effects, suggestions, and planned actions. Challenges, difficulties, realized risks and opportunities, and other items that may provide details about the lessons learned.
It is an output in the early stages of the project that is used as input in the subsequent stages and modified as output.
Organizations maintain something known as a Lessons-Learned Register that holds information about the lessons learned from various projects that is updated to the repository at the end of each project.
Key Points
A file that serves as a diary and records all the insights obtained throughout a project is the lessons learned register.
– A It keeps track of the good and bad things that happen to the team as they go through the project.
– A It’s a compilation of the good, the bad, and the room for improvement for similar initiatives in the future.
– A Imagine it as a book that lays out every step of the project and how to prevent every possible problem.
– A In order to gain insight from one another’s experiences, the team works together to produce and share it.
– A In order to avoid making the same mistakes in future projects, this record is useful.
– A By documenting the important takeaways from the project, it serves as a useful tool that encourages ongoing development.
