Every project generates experience. The question is whether we turn that experience into better decisions and practices.
Without a deliberate effort to learn from past experience, teams risk repeating mistakes, overlooking successful practices, and missing opportunities to improve. A Lessons Learned Report helps capture what happened, understand why it happened, and identify what should change or continue in future projects.
The process behind the report
A Lessons Learned Report is one output of a structured learning process that includes an After Action Review (AAR).
An AAR is a facilitated discussion that examines project experiences to understand what happened, why it happened, and what can be learned. It encourages participants to compare expectations with actual outcomes, explore the reasons for differences, and identify ways to improve.
A typical AAR revolves around four fundamental questions:
- What was supposed to happen? Establish the original objectives, plans, and expectations.
- What actually happened? Examine the outcomes and events, using evidence wherever possible.
- Why was there a difference? Analyze the factors and causes that contributed to the results.
- What can we learn from it? Identify what should change, what should continue, and what actions will improve future performance.
The objective is to move beyond describing events and develop a shared understanding of what can be learned from them.
The stages of an effective Lessons Learned process
1. Preparation
Define the scope of the review, identify participants, gather relevant project records, and prepare the questions that will guide the discussion. Include people with different perspectives and create an environment where they can speak openly.
2. Review and Documentation
Conduct the After Action Review. Examine what was planned, what actually happened, why it happened, and what can be learned. Document the findings in a Lessons Learned Report, distinguishing observations from conclusions and recommendations.
3. Follow-up and Application
Translate recommendations into specific actions. Assign owners, agree on deadlines, and monitor implementation. Share relevant lessons across the organization and check whether the changes improve performance in subsequent projects.
The process is complete only when the organization has acted on the lessons and made the learning available to others.
Who should participate?
Learning from a project requires more than the project manager’s perspective. Team members, relevant stakeholders, subject matter experts, clients, and suppliers may each see different aspects of the same experience.
Involving the right people helps uncover information that might otherwise be missed. It also builds a shared understanding of what happened and what can be learned.
An open, constructive discussion is essential. The objective is to understand the factors that influenced the outcome, not to assign blame.
More than a summary
The Lessons Learned Report documents the conclusions of the review and translates them into recommendations that others can use. Its value depends on whether the findings reach the people who can act on them.
Recommendations generally fall into two categories:
- Things to Improve: Processes, practices, decisions, or ways of working that need to change.
- Things to Preserve: Successful approaches, effective practices, and decisions that contributed to positive outcomes and should be repeated.
Both matter. Organizations need to understand why things went wrong, but they also need to recognize what enabled success.
Whenever possible, recommendations should identify a specific action, an owner, a deadline, and a way to verify that the change has been implemented. This turns learning into a practical commitment rather than a list of observations.
The findings should also be shared with the people who can benefit from them. A lesson learned by one project team becomes far more valuable when other teams can apply it to their own work.
Learning is a goal worth pursuing
The real measure of a Lessons Learned Report is not how much it contains, but what changes because of it.
Continuous improvement requires an organizational culture that encourages honest discussion, welcomes constructive feedback, and treats mistakes as opportunities to learn. It also requires a commitment to acting on the findings and checking whether the recommended changes make a difference.
When organizations apply what they learn, experience becomes an asset that strengthens future projects. Teams make better decisions, processes improve, and successful practices spread beyond the projects in which they first emerged.
Every project is an opportunity to learn. The challenge is to ensure that the next project benefits from what the previous one taught us.
