Lessons Learned

A blog by Dr. Uwe-Klaus Jarosch, November 2025

In the blog “Knowledge – Management,” I attempted to provide an explanation for knowledge in companies.

This knowledge, these instructions for action, are subject to change. This also means that knowledge – unless it concerns the fundamental laws of nature – becomes outdated.

Look at the knowledge that loses its value in its old form due to technical developments and must be replaced by new rules as an example.
Take a work instruction for operating a lathe. If you are working on a “conventional,” mechanically controlled lathe, you have to follow completely different instructions than if you are operating a CNC-controlled lathe.

An organization (i.e., a company, a government agency, or even my private household) must keep its knowledge and rules up to date. Otherwise, the rules can no longer be applied in a meaningful way. This applies to all forms of knowledge, from management systems and standards to current instructions in today’s projects.

One sign is when rules are suspended or circumvented because they are no longer appropriate. In this case, supervisors and process managers should respond and check whether the rules still make sense.

Another sign that a rule needs to be changed is when errors occur in the process or as a process result.

Another way to keep knowledge up to date is by a lessons learned process.

Lessons learned is a tool for continuous improvement.

Regularly, ideally at short intervals, recent events are critically analyzed:

  • What went well but has not yet been codified?
  • What went wrong according to the existing process and should be improved?

The result of this analysis should consist of three parts:

  1. What were the boundary conditions under which the problem occurred?
  2. What were the causes that led to this problem?
  3. What are the successful solutions that should be applied again elsewhere and on other occasions? What were unsuccessful attempts at solutions that do not need to be considered in the future?

Lessons Learned shall become effective in future.

Experiences should be recorded in order to derive instructions for action.

Mistakes happen. But they should not be repeated.

Lessons learned means learning from failures.

This learning only has a lasting effect if

  • the lessons learned are available and distributed. What is not known and accessible will not be applied.
  • this knowledge accumulation must be a company process with a responsible driver. Therefore, an advocate, a sponsor, is needed. This can be an LL representative in management or the experts responsible for a technical topic (Center of Competence).
  • The effort required to carry out the analysis properly requires a budget.
  • And it requires authorization within the company to turn the new findings into a valid rule.

Professions that deal with life and death cultivate intensive lessons learned.

  • After every military operation, every special police operation, and every critical medical procedure, the latest events and steps are discussed critically.
  • New findings and possible improvements are immediately incorporated into future procedures.
  • In these teams, they are bindingly agreed upon.
  • Everyone in the team is informed of the decisions and must follow them.

Development teams in agile development processes also conduct regular reviews to adapt the next steps and procedures to current requirements.

In larger organizations, lessons learned are often difficult.

  • The effort involved in regularly critically questioning one’s own working methods is avoided. When it does take place, it is often only to the point of collecting problems.
  • What are the consequences? Who needs to be involved in the solution? In which cases should the solution be binding, and in which cases should it be an option?
    Where are the new findings recorded and authorized?
  • Is it even the intention and practice of the company to prescribe working methods to other working groups, departments, or plants? (Keyword: standardization)

Another point of contention is the type of filing system.

Should lessons learned be entered into systems—in the sense of a database?

Or should lessons learned be linked to individuals who are informed and drive the use of the new findings?

From my perspective, Lessons Learned must be a combination of storage in an organized data pool AND the timely information flow to all people who shall use these LL.

Conclusions: 

  • Lessons learned is a process within the company that must be organized and supported.
  • The goal of standardization is supported by LL; the greater the standardization, the more important and comprehensive LL becomes.
  • The more success or even life and limb depend on everytime learning, the more intensively LL is pursued.
  • The larger the circle of LL users is to be, the more difficult the implementation. It requires management support and authorization of the new rules.
  • Simply naming problems (writing on the wailing wall) is not LL.

Stay curious

Uwe Jarosch

Leave a Reply

Your email address will not be published. Required fields are marked *