Ask a question Share knowledge Edit the page

Lessons Learned

Lessons Learned It is a systematic process of identifying, analyzing, documenting and reusing experiences gained in the course of working on projects, tasks or in the elimination of incidents.

Implementing this practice protects the organization from “attacking the same rake” (repeating past mistakes) and helps to scale successful decisions throughout the company, turning individual employee experience into general corporate knowledge.

What problems solve the lessons learned

General considerations

It’s not possible to measure the impact of a culture of knowledge sharing, nor to measure the state of that culture, and it can be different from team to team, from person to person, especially in large organizations, and that’s OK.

So let’s say that these things can be evaluated empirically, and that means you probably have to go to different organizations and different cultures to learn to see the differences.

Key learning formats

The practice of lessons learned is divided into three main formats, depending on context, scope and urgency:

  1. Incident Analysis (Post Mortem)
    It is used proactively after critical technical failures or accidents, focusing on technical reliability, blameless culture and systemic causes of failure.

  2. After Action Review
    Quick, iterative hot-follow analysis, right after small tasks, feature releases, or operational events are completed, takes 20-45 minutes and is built around four simple questions.

  3. Post-Project Reflection (Lessons Learned)
    Comprehensive retrospective analysis at the closing or major phase of a project: encompassing the entire project lifecycle: goals, timelines, budget, change management, and team interactions.

How to Start Implementing This Change

The main barrier to implementing this practice is psychological and organizational, and managers and teams often perceive debunking mistakes as “finding the guilty” or view collecting lessons as a waste of time.

For a successful start, we recommend you to familiarize yourself with the following materials:

To find really useful and applicable comments, focus on actions that can be changed in the future. The output template should be: "In situation X, we did Y, got Z. In future situation X, we recommend doing W."
To convince management of the value of the practice, show financial losses from recurring mistakes from year to year or demonstrate accelerated onboarding of new employees based on the lesson register.

Conduct of pilot sessions

When launching a pilot project, it is important to facilitate the meeting so that people feel safe and share problems openly.

Creative Commons License | by Igor Tsupko, Lana Novikova, Rodion Nagornov & community