Unread lessons learned are just an archive

A lessons learned template for manufacturing: one page per closed case, written at closure in the words the next engineer will search for.

Rows of grey binders on black, with one gold sheet in front of them.

A lessons learned template is a one-page form that records what a closed case taught: the symptom, the proven cause, what worked, what did not, and where else the cause applies. In manufacturing, the useful version is written at closure, in the words the next engineer will search for when a new complaint arrives.

We read three 8D guides that European manufacturers give their suppliers, in October 2026. All three use D7 to carry the lesson sideways, to similar products or processes.

None of them says how the next team finds the lesson when a new complaint arrives.

What a lessons learned template should hold

One page per closed case, written by the team that closed it.

Field What to write
Case Number, method (8D, 4-Step, PDCA), date closed
Symptom, in the line’s words How the operators and the customer described it, next to the defect code
Part and process Part family, operation, machine, material and supplier
Root cause Why it occurred, why it escaped, and the test that proved each
What worked The action, and the date and data of the proof
What did not work Actions tried and dropped, and why they failed
Where else Other parts, lines and products with the same cause, FMEA and control plan changes
Search words Five to ten words: symptom, part, process and cause, in the language of the plant
Who knows more The role, and where the data and samples are kept

Copy the table into Word or Excel, one row per field.

In my view, “What did not work” is the field the next team needs most. It saves them the same detour.

“Who knows more” names a role, not a person. People change jobs. The role and the data stay.

Write it at D8, read it at D2

At closure the team still has the evidence: the test results, the photos, the dates.

The lesson is read at the start of the next similar case, in D2, before anyone analyses anything. That is why the template asks for search words. The next engineer types the symptom as the line describes it, and the part. A page filed only under its case number is found only by someone who already knows the number.

Volume comes before answers

A collection of lessons answers only when there is enough in it. In our pilot paper we noted that SolveR’s suggestions from past cases are thinner while a plant has fewer than about 20 closed cases.

One page per closed case is how a plant gets past that number.

What the standards ask

ISO 9001:2015, clause 7.1.6, asks a company to determine the knowledge necessary for the operation of its processes, to maintain it and to make it available. A note to the clause names “lessons learned from failures and successful projects” as one internal source of that knowledge.

The new edition, ISO 9001:2026, makes it explicit that this knowledge is retained, applied and shared, to the extent necessary.

The TÜV Rheinland Akademie names one place a lesson can live: entered into the FMEA database in D7. That makes the lesson part of the next FMEA review. A new complaint starts in D2, so the lesson also needs the search words.

Start with the last three closed cases

  1. Take the last three closed 8D reports.
  2. Write one page for each with the template.
  3. Ask a colleague who did not work on them to find each case using only the symptom and the part.

If the colleague cannot find a case, the search words are missing.

In SolveR, every closed case stays in the knowledge base with its causes, actions and evidence, so the next similar case can find it.

More on galileon.si

  1. How SolveR works: the knowledge base
  2. Europe’s productivity is stuck in spreadsheets
  3. Pilot results: 10 real 8D cases at 8 manufacturers

References

  1. ISO 9001:2015, Quality management systems, Requirements, clause 7.1.6. ISO
  2. DNV GL (Norway), Do you determine the knowledge necessary for business performance? White paper on ISO 9001:2015 clause 7.1.6, August 2018. DNV
  3. Advisera (Croatia), ISO 9001:2015 vs. ISO 9001:2026, main differences, updated 8 October 2026. Advisera
  4. Abilene Academy (Switzerland), ISO 9001:2026: the complete guide, updated 29 September 2026. Abilene Academy
  5. Husqvarna Group (Sweden), 8D Pocket Guide, Issue D, no date. Husqvarna
  6. ARNOLD (Germany), Mindestanforderung 8D-Report Lieferanten, AA-00472, version 2.00, 26 May 2023. ARNOLD
  7. DeLaval (Sweden), 8D Process: A structured problem-solving methodology, information for suppliers, 7 July 2026. DeLaval
  8. TÜV Rheinland Akademie (Germany), Strukturierte Fehlerbehebung für höchste Qualität: der 8D-Report in der Praxis, 15 May 2025. TÜV Rheinland
  9. Matej Kalčič, Z umetno inteligenco podprt organizacijski spomin (AI-Powered Organizational Memory), proceedings of the 10th International Scientific Conference, Faculty of Industrial Engineering Novo mesto, 14 May 2026, pp. 77-82. PDF
All posts