Chapter 40: Lessons Learned Programs: Preventing the Same Nonconformance Across Products, Shifts, and Sites

One of the most common failure modes in manufacturing is solving the same problem twice, in different places, at different times, without learning from the first solution.

A lessons learned program is a formal system for capturing the root cause analysis and corrective actions from closed CARs into a searchable knowledge base that becomes part of your organizational memory. This is especially critical in Canadian manufacturing because:

1. Shift rotations and staff turnover mean the person who solved a problem last year isn't always there when the same problem recurs.
2. Multi-site operations (many Canadian manufacturers run plants in different provinces) need a way to share learning across locations without duplicating effort.
3. New product launches introduce risk of repeating known failures—your lessons learned database becomes a pre-launch checklist.

Here's how to build a practical lessons learned program:

Step 1: Formalize CA Documentation Standards

Your corrective action form should capture not just what happened and why, but the exact lesson learned. Example:

• Nonconformance: Solder joint cold joint failures on circuit board assembly, SKU ABC-2240
• Root cause: Temperature profile in reflow oven not stable between 230–245°C during morning startup; oven was not warmed up before production began
• Corrective action: Require 20-minute warm-up cycle before first production run each shift; update work instruction with photo and time clock reference
• Lesson learned: "Reflow oven thermal stability is shift-dependent. Always warm up the equipment first."

The lesson learned is the knowledge artifact—the thing a new operator, a new shift supervisor, or a new product team can read and understand without reading the full CAR.

Step 2: Build a Searchable Knowledge Base

Use your quality management system corrective process to store CARs and lessons learned in a way that's searchable by:

• Product family or SKU
• Process (e.g., soldering, assembly, painting, machining)
• Root cause category
• Date range

When a new product launch team is preparing to run SKU ABC-2340, they run a query: "What lessons learned exist for circuit board assembly SKUs?" They get three results, including the solder joint lesson. They implement the 20-minute warm-up requirement before they ever see a cold joint failure.

Step 3: Implement Horizontal Deployment

This is a requirement in IATF 16949 for automotive suppliers and a best practice everywhere else. Horizontal deployment means: when a corrective action is issued in one location or product line, automatically flag whether that same issue could exist elsewhere.

Example: A plant in Quebec discovers a supplier specification issue affecting plastic injection molded components. Before closing that CAR, the quality team asks:

• Do any other product lines use this supplier?
• Do any other plants use this supplier?
• Are there similar specifications in use that might have the same root cause?

If the answer is yes to any of these, the CAR includes a verification step: "Confirm that supplier specification revision is applied across all affected SKUs and locations. Plant manager sign-off required."

A company with plants in British Columbia and Ontario that manufactures industrial fasteners implemented horizontal deployment in 2023. They discovered it reduced re-occurrence rates by 67% compared to plants that didn't systematically check for similar issues.

Step 4: Make Lessons Learned Part of Onboarding

New hires in quality, production, and engineering should review relevant lessons learned as part of onboarding. A new quality inspector in final assembly should read the last 24 months of lessons learned for that process. A new product engineer should review lessons learned from previous product launches in the same family.

This isn't punitive—it's knowledge transfer. The veteran operator who solved a problem two years ago has now trained the new person without being in the room.