9.9 Lessons Learned, Documentation, and Training for Sustainment

ASQ Certified Six Sigma Black Belt CSSBB

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CSSBB Exam Strategy

1.1 CSSBB Exam Format, Scoring, and Testing Windows 1.2 Eligibility, Project Affidavits, Application, and Recertification 1.3 Open-Book Strategy, Reference Materials, and a 16-Week Study Plan

2 Chapter 2: Organization-Wide Planning and Deployment

2.1 Fundamentals of Six Sigma and Lean Methodologies 2.2 Selecting the Right Methodology: DMAIC, DFSS, and Lean 2.3 Business Systems, Processes, and Stakeholder Relationships 2.4 Strategic Planning and Deployment of Six Sigma Initiatives 2.5 Six Sigma Roles and Responsibilities 2.6 Organizational Barriers and Common Causes of Six Sigma Failure 2.7 Change Management: Stakeholder Analysis, Readiness, and Communication

3 Chapter 3: Organizational Process Management and Measures

3.1 Impact of Six Sigma Projects on Customers, Suppliers, and Stakeholders 3.2 Benchmarking Types and Performance Goal Setting 3.3 Performance Measures: Balanced Scorecard, KPIs, KBIs, OKRs, and Line of Sight 3.4 Leading and Lagging Indicators and Performance Dashboards 3.5 Financial Measures: Revenue Growth, Margin, NPV, ROI, and Cost-Benefit Analysis 3.6 Cost of Poor Quality and Hard versus Soft Savings

4 Chapter 4: Team Management

4.1 Team Types and Constraints 4.2 Team Roles, Responsibilities, and Member Selection 4.3 Team Success Factors and Ground Rules 4.4 Motivational Techniques and Overcoming Demotivators 4.5 Stages of Team Development and Conflict Resolution 4.6 Team Communication Plans 4.7 Team Leadership Models: Direct, Coach, Support, and Delegate 4.8 Group Behaviors, Conflict Resolution, and Meeting Management 4.9 Facilitation Techniques and Team Decision-Making Methods 4.10 Team Training: Needs Assessment, Delivery, and Evaluation

5 Chapter 5: Define Phase

5.1 Customer Identification and Segmentation 5.2 Customer Data Collection: Methods, Validity, and Reliability 5.3 Customer Requirements: CTX, CTQ Trees, and Operational Definitions 5.4 The Kano Model and Quality Function Deployment 5.5 SIPOC and Process Mapping 5.6 Business Case Justification 5.7 The Project Charter and the Problem Statement 5.8 Project Scope and Boundaries 5.9 SMART Goals and Project Performance Measurements 5.10 Project Charter Reviews and Toll-Gate Governance 5.11 Project Management Tools: Gantt Charts, Toll-Gate Reviews, WBS, and RACI 5.12 Analytical Tools Used Throughout the DMAIC Cycle

6 Chapter 6: Measure Phase

6.1 Process Flow Metrics and the Hidden Factory 6.2 Process Analysis Tools and Value Stream Mapping 6.3 Types of Data and Measurement Scales 6.4 Sampling Concepts, Methods, and Sample Size for Estimation 6.5 Data Collection Plans and Common Pitfalls 6.6 Gage R&R for Variable Measurement Systems 6.7 Attribute Agreement Analysis and Audit MSA 6.8 Measurement Systems Across the Organization, and Metrology 6.9 Population Parameters, Sample Statistics, and Valid Statistical Conclusions 6.10 Descriptive Statistics: Central Tendency, Dispersion, and Shape 6.11 Graphical Methods for Exploratory Data Analysis 6.12 Probability Concepts, Common Distributions, and the Central Limit Theorem 6.13 Additional Distributions: Hypergeometric, Exponential, Lognormal, Weibull, and Bivariate 6.14 Process Capability and Performance Indices 6.15 Capability Studies, Attributes Capability, Yield Metrics, and Long-Term Capability

7 Chapter 7: Analyze Phase

7.1 The Correlation Coefficient, Its Confidence Interval, and Causation 7.2 Linear Regression and Residual Analysis 7.3 Multivariate Tools: Factor Analysis, Discriminant Analysis, and MANOVA 7.4 Hypothesis Testing Terminology, Errors, and Single-Sample Tests 7.5 Statistical Versus Practical Significance 7.6 Sample Size for Hypothesis Tests 7.7 Point Estimates, Confidence, Prediction, and Tolerance Intervals 7.8 Tests for Means, Variances, and Proportions 7.9 Analysis of Variance 7.10 Chi-Square Goodness-of-Fit and Tests of Independence 7.11 Types of Risk and Failure Mode and Effects Analysis 7.12 Gap Analysis and Root Cause Analysis 7.13 Waste Analysis: The Seven Classic Wastes and Resource Under-Utilization

8 Chapter 8: Improve Phase

8.1 Design of Experiments: Objectives, Terminology, and Effects 8.2 DOE Design Principles: Randomization, Blocking, Replication, and Resolution 8.3 Planning and Evaluating Designed Experiments 8.4 One-Factor Experiments: Completely Randomized, Randomized Block, and Latin Square Designs 8.5 Full Factorial Experiments and Design Selection 8.6 Two-Level Fractional Factorial Experiments and Confounding 8.7 Response Surface Methodology and Optimization 8.8 Waste Elimination: Pull Systems, Kanban, 5S, and Poka-Yoke 8.9 Cycle-Time Reduction: Continuous Flow, SMED, and Heijunka 8.10 Kaizen, Kaizen Blitz, Theory of Constraints, and OEE 8.11 Implementation Planning, Piloting, and Solution Selection

9 Chapter 9: Control Phase

9.1 SPC Objectives, Variable Selection, and Rational Subgrouping 9.2 Control Charts for Variables Data 9.3 Control Charts for Attributes Data 9.4 Short-Run SPC and Moving Average Charts 9.5 Control Chart Analysis: Common Cause, Special Cause, and Run Rules 9.6 Total Productive Maintenance and Visual Controls 9.7 Measurement System Reanalysis 9.8 Control Plan Development and Process Owner Handoff 9.9 Lessons Learned, Documentation, and Training for Sustainment 9.10 Ongoing Evaluation of the Improved Process

10 Chapter 10: Design for Six Sigma (DFSS)

10.1 DFSS Frameworks: DMADV, DMADOV, and Design Transfer 10.2 Design for X (DFX) 10.3 Robust Design, Parameter Design, and Verification 10.4 Tolerance Design and Statistical Tolerancing

9.9 Lessons Learned, Documentation, and Training for Sustainment

Key Takeaways Explain This Topic AI

Lessons learned must be captured across all phases, not only at closure, and must include what did not work.

Replication strategies convert a single project's gain into an enterprise gain by identifying similar processes and transferring the solution.

SOPs describe what and why at the process level; work instructions describe exactly how at the task level.

Documentation must go through the organization's change control process, with revision numbers, approvals, and removal of superseded copies.

Training handed to process owners requires objectives, a competency standard, and a measure of whether behaviour changed on the job.

Last updated: August 2026

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:

Phase Questions to answer

Define Was the problem correctly framed? Was the scope right in hindsight? What did the charter miss?

Measure Did the measurement system hold up? Which data proved unobtainable? What did stratification reveal?

Analyze Which hypotheses were rejected, and what would have found the answer faster?

Improve Which solutions failed in pilot, and why? What did the pilot reveal that the analysis did not?

Control What did the process owner need that we had not prepared? What nearly slipped?

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.

Characterize the solution. What conditions must hold for it to work?

Search for matching processes. Same equipment type, same failure mode, same transaction type,

other sites, other lines, other shifts.

Assess transferability. Identical, adaptable, or not applicable.

Assign owners and dates for each replication target.

Track them as a portfolio, with their own benefit numbers.

Replication target Similarity Transferability Owner Estimated benefit
Line 4, same plant Identical equipment Direct Line 4 supervisor $86k
Plant B, lines 1-2 Same equipment, different material Adaptable Plant B quality lead $140k
Plant C Different technology Not applicable -- --
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.

Document Scope Answers Typical audience

Standard operating procedure (SOP) A process or activity What is done, by whom, in what sequence, and why Supervisors, auditors, trainers

Work instruction A single task or station Exactly how to perform the task, step by step The person doing the work

Control plan The characteristics being controlled What is measured, how, how often, by whom, and what to do when it is out of control Operators, quality, process owner

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:

Draft the revision with the process owner.

Route for approval by the defined approvers -- typically process owner, quality, and in regulated

environments a regulatory or validation function.

Assign a revision number and effective date .

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.

Train affected staff before the effective date.

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

Element Content
Learning objectives What the trainee must be able to do, observably, and to what standard

Materials Work instruction, control plan, reaction plan, job aids -- ideally the same documents used on the job

Competency standard Demonstrated performance, not attendance
Trainer Named, and qualified to at least a can-teach-others level
Coverage plan Every shift, including relief and temporary staff
Refresher interval Defined, with a trigger for retraining after any change
Evidence Training records tied to the training matrix
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.