1. Method Name

Lessons Learned Session (Review of Lessons Learned)

2. Alternative Names

Post-mortem, After-Action Review (AAR), Debrief

3. Brief Description

"Lessons Learned" is a structured meeting that takes place after the completion of a project, a project phase, or a significant event. Its purpose is to identify and document what went well, what didn’t go well, and what lessons the team can take away for the future.

4. Purpose / When to Use

It is used to promote organizational learning and to prevent the same mistakes from recurring in future projects. It is a key tool for improving project management and for sharing knowledge within the organization.

5. Procedure / How to Apply It

1. Schedule a meeting: Invite all key members of the project team. Send them questions to ponder in advance.
2. Create a safe environment: Emphasize that the goal is not to assign blame, but to learn from the experience.
3. Discuss key questions
: - What did we plan to achieve? (Original goals)
- What did we actually achieve? (Actual results)
—What worked well and why? (Successes to replicate)
—What didn’t work well and why? (Problems to avoid)
—What would we do differently next time? (Specific recommendations)
4. Document the results: Create a concise and clear “Lessons Learned” report that includes key findings and specific recommendations.
5. Share and store: Save the report in a central knowledge database and actively share it with other teams and project managers.

6. A Real-World Example

After the marketing campaign was completed, the team met for a "Lessons Learned" session. They found that the Facebook campaign worked very well (lesson learned: invest more in Facebook), but the collaboration with the influencer was ineffective and expensive (lesson learned: vet influencers more carefully). They incorporated these insights into the planning for the next campaign.

7. Benefits

- Prevents mistakes from recurring
.- Promotes a culture of learning and continuous improvement
.- Improves planning for future projects
.- Preserves and shares valuable knowledge within the organization.

8. Risks / Limits

- Blame-shifting: A meeting can easily turn into a finger-pointing session
.- Forgotten lessons: If the report is simply filed away in a drawer and no one reads it, the entire process is pointless.
- Subjective memories: People may remember events inaccurately or with bias.
- Participation: If not all key members participate, the picture may be incomplete.

9. Practical Tips

- Do this on an ongoing basis: Don’t wait until the very end of a major project. Conduct smaller “Lessons Learned” sessions after each important phase
.- Use an independent facilitator: This will help keep the discussion constructive and focus on the process, not the people.
- Focus on the future: The goal isn’t to cry over spilled milk, but to learn from the experience and formulate specific recommendations for the future.
- Lessons Learned vs. Retrospectives: They are very similar. Retrospectives are typically more frequent, shorter, and focused on improving teamwork within iterations. Lessons Learned often take place at the end of a larger project and focus on the project as a whole.