Lessons Learned Knowledge Management: Capture and Apply

What lessons learned and knowledge management mean

Lessons learned are insights from a project, problem or event that have been recorded, validated and turned into action so a mistake is not repeated and a success is. Knowledge management is the system that moves that insight out of a few people's heads and into the process.

On the shop floor, knowledge is lost in predictable ways: the launch engineer moves to the next program, the veteran operator retires, the report sits in a folder nobody opens. A lesson that exists only as a file is not learned; it is filed.

Visual map: capture, validate, share and apply

The map summarizes the four stages, the minimum record for each lesson and the numeric example in this article.

The four-stage cycle

1. Capture: record the lesson right after the event (phase end, 8D closure, launch, major breakdown), with the people who lived it in the room.
2. Validate: someone with technical authority confirms that the cause and the recommendation hold up. A lesson without validation is an opinion.
3. Share: get the lesson to the people who will need it, when they need it: project kickoff, training, area board.
4. Apply: build it into standard work, the FMEA, a checklist or a specification. Only here does the lesson stop depending on memory.

The PDCA cycle runs through all of it: capture and validate are Check, apply is the Act that feeds the next Plan.

What to record in each lesson

A short record that is the same for everyone gets used more than a long form. The useful minimum:

Example: stamping line transfer project

Fictional example. At project close the team logged 18 lessons. In technical review, 14 were validated and 4 were rejected (isolated cases with no proven cause). Of the 14 validated, 9 were built into standards, FMEA or checklists, and 5 had no owner or due date.

Incorporation rate = lessons incorporated ÷ lessons validated

The bottom number is the one that matters: only half of what the team learned became real change. The 5 validated but unincorporated lessons are next month's work list, each with an owner and a date. One that did get built in was "check the press oil level at die change", which went into the setup standard and the start-up checklist.

When to capture

• At the end of each project phase, not only at closure: in six months nobody remembers what went wrong in month two.
• After an 8D report or customer complaint, in the recurrence-prevention step.
• After a product launch or machine start-up, with production, maintenance and quality in the same room.
• After a kaizen event, to record what worked and what stalled.
• When key people leave, with a knowledge-transfer interview.

Explicit and tacit knowledge

Explicit knowledge fits in a document: procedure, drawing, parameter. Tacit knowledge lives in experience: the way of hearing a machine before it fails. Nonaka and Takeuchi show that tacit knowledge transfers only through shared work, demonstration and conversation. In practice:

• Explicit: standards, FMEA, checklists, A3 reports, a searchable lessons base by product and process.
• Tacit: side-by-side coaching, TWI training, kickoff meetings with people who have done it before, short operation videos.
• Routine: pull relevant lessons into daily management and at the start of every new project, from the project charter.

ISO 9001:2015 requires the organization to determine the knowledge needed to operate its processes and keep it available (clause 7.1.6). For the wider context see ISO 9001 implementation.

Common mistakes

• Doing it only at the end: memory has already erased the details.
• Hunting for someone to blame: if the meeting becomes a tribunal, nobody records the error. Stay on the process.
• Generic lessons: "improve communication" cannot be verified. Write the concrete action.
• No owner, no date: this produces the 36% of validated lessons left unincorporated in the example (5 of 14).
• A base nobody consults: if it is not in the path of the work, it is not read.
• Not measuring: without the incorporation rate, knowledge management turns into paperwork.

Frequently asked questions

What are lessons learned?

Insights from a project or event, recorded, validated and built into standards to avoid repeating mistakes and to repeat successes.

What is the difference between a lesson logged and a lesson learned?

A logged lesson has only been written down. A learned one has been validated and built into a process, document or training.

When should a lessons learned meeting be held?

At the end of each phase, after launches, after 8Ds and when key people leave, not only at project closure.

How do you measure knowledge management?

By the incorporation rate (incorporated ÷ validated) and the time from capture to incorporation. In the example, 9 ÷ 14 = 64.3%.

Does ISO 9001 require lessons learned?

It requires managing organizational knowledge (7.1.6) but does not prescribe a format. Lessons learned is one way to meet it.

Where should lessons be stored?

In a base searchable by product and process and, above all, inside the standards, FMEAs and checklists people already use.

About the author

Vagner Soares

Lean Manufacturing & Behavioral Management Specialist

Over 20 years in the automotive and metalworking industries (GM and Dana), Lean Manufacturing practitioner since 2006. SENAI instructor and mentor in Brazil’s Brasil Mais Produtivo program, delivering consulting, training and audits for 50+ companies, combining quality, productivity and people development.

LinkedInInstagramFull profile →