9.9 Lessons Learned, Documentation, and Training for Sustainment

Lessons learned and benefits realized

The Body of Knowledge asks Black Belts to document the lessons learned and benefits realized from all phases and to identify strategies for reinforcing and replicating improvements.

Capture across phases, not at the end

Lessons captured only at closure are reconstructed from memory and biased toward the successful ending. The practical discipline is a running log with an entry at every toll gate:

Record the failures. A log of what did not work is more valuable than a list of what did, because the next team will otherwise try the same things. A rejected hypothesis with the data that rejected it saves the next project weeks.

Benefits realized

The benefit recorded at closure must be the validated figure, signed by finance, computed on the same basis as the baseline. Record hard and soft separately, state the calculation method, and note the period over which it was measured. A common requirement is a follow-up validation at 6 or 12 months confirming the benefit persisted -- projects whose gains decay are not visible without it.

Replication

Replication is where a Six Sigma deployment gets its leverage: one solved problem applied to twelve similar processes.

1. Characterize the solution. What conditions must hold for it to work?
2. Search for matching processes. Same equipment type, same failure mode, same transaction type, other sites, other lines, other shifts.
3. Assess transferability. Identical, adaptable, or not applicable.
4. Assign owners and dates for each replication target.
5. Track them as a portfolio, with their own benefit numbers.

Two practical rules: replication needs a named owner at the receiving process, not just a shared report; and the replicating site must verify locally rather than assume, because the conditions that made the solution work may not hold.

Documentation

The Body of Knowledge names SOPs, work instructions, and control plans.

Writing documentation people follow

• Write at the point of use. Draft it at the process, with the person who does the work, and have someone unfamiliar attempt the task from the draft alone.
• Use images. A photograph of the correct condition beats three paragraphs describing it.
• Say what is different. Highlight the change from the previous revision so experienced staff do not have to re-read the whole document.
• State the reason for critical steps. People deviate from steps whose purpose they do not understand.
• Keep it at the reading level and in the language of the users.

Change control

Documentation changes must run through the organization's controlled process:

1. Draft the revision with the process owner.
2. Route for approval by the defined approvers -- typically process owner, quality, and in regulated environments a regulatory or validation function.
3. Assign a revision number and effective date.
4. Remove and destroy superseded copies. An obsolete laminated instruction still hanging at the station is a control failure, and it is the most common audit finding after a process change.
5. Train affected staff before the effective date.
6. Update every downstream reference: the training matrix, the audit checklist, the control plan, the FMEA.

In regulated industries the change may also require revalidation and, in some cases, customer or regulatory notification. Those lead times belong in the project plan from Define, not discovered in Control.

Training for process owners and staff

The Body of Knowledge asks for training plans handed off to process owners, to ensure consistent execution of revised methods, with KPIs to confirm sustained benefits and standards to maintain the improvement.

The handoff package

Train to competency, not to attendance

A signature on an attendance sheet records that a person was present. The standard should be a demonstrated performance against the objective: the operator performs the task unaided, correctly, while an assessor observes. A four-level skills matrix -- aware, can perform with help, can perform unaided, can teach others -- makes coverage visible, and at least one level-four person per shift is what prevents the capability leaving with a single individual.

Confirm it transferred

Training evaluation at the reaction level -- did they like it -- says nothing about the process. The sustainment question is behavioural: are people doing it? Build that into the control plan as a key behaviour indicator with a defined audit frequency, for example the percentage of shifts where the layered process audit was completed, or the percentage of out-of-control signals with a documented reaction. That measure, owned by the process owner, is what turns a training event into a control.