Lessons Learned: When and Why to Update
Timing the update of lessons learned is a critical process in ensuring the continuous improvement of projects or organizations. The question "When are lessons learned updated?" thus arises, with various factors influencing the answer. The frequency and occasions for updating lessons learned can vary greatly depending on the industry, the complexity of the project, and the organization's processes.
In many projects, lessons learned are typically captured at key milestones or phases, such as at the end of a project, or following significant events like project pivots orscope changes. However, the most effective organizations continually capture and update lessons learned throughout the project lifecycle, ensuring that recent insights and learnings are reflected in their knowledge base.
Formal Project Phases
For many projects, lessons learned are updated at the end of each formal phase. This could include:
- End of Initiation: After the project's objectives, scope, and stakeholders have been clearly defined.
- End of Planning: After the project plan, including schedule, budget, and resource allocation, has been finalized.
- End of Execution: After the project's deliverables have been completed and delivered.
- End of Closure: After the project has been formally closed and the final deliverables have been accepted.
End of Project
The end of a project is a common time to update lessons learned. At this stage, the project's outcomes can be analyzed, both in terms of their success in meeting objectives, and how effectively processes were managed. Lessons from the project's successes and failures can then be documented.
Example: A software development project might document how the implementation of Agile methodologies improved collaboration and responsiveness to changing requirements. Conversely, it might note that a lack of understanding about a specific technical constraint led to delays.
Post-Mortem Reviews
Lessons learned can also be updated following post-mortem reviews or project audits. These typically occur after the project has ended and involve a thorough examination of the project's processes and outcomes. Lessons learned from these reviews can then be fed back into the organization and used to improve future projects.
Example: A construction project might find that suppliers are not meeting promised delivery dates consistently. This could spark a review of supplier management processes and the addition of new lessons learned around more stringent supplier selection and monitoring.
Continuous Improvement
Agile and lean methodologies advocate for continuous improvement, which can also influence the timing of lessons learned updates. In these environments, lessons learned can be updated frequently, often at the conclusion of each Sprint or work cycle.
Agile environments often use techniques like "Lessons Learned Retrospectives" or "Retros" to encourage continuous improvement. These sessions provide a dedicated space for teams to reflect on their work, identify what went well, what didn't, and how they could do things differently next time.
Sprint Review or Retrospective
In Agile development, each sprint (or work cycle) concludes with a review and retrospective. Lessons learned from each sprint can then be documented and incorporated into future sprints.
Example: A Scrum team might document during a retrospective that the team's lack of understanding of a new tool led to inefficient work. This would then become a lesson learned, with the team making a point to improve their understanding of the tool in future sprints.
Quarterly or Annual Reviews
For some organizations, lessons learned are updated during quarterly or annual reviews, providing a longer-term perspective on improvements and developments. These reviews can focus on broader organizational or industry trends and how the organization can adapt to them.
Example: A quarterly review may identify an emerging technology that could revolutionize the industry. This would then become a significant learning for the organization, influencing future strategic planning.
In essence, the timing of lessons learned updates depends on various factors, with different projects and organizations having different needs and priorities. Some may prioritize continuous learning and evolution, while others may prefer more scheduled, structured updates. The key is to ensure that lessons learned are updated regularly, making it an integral part of the project or organizational culture.