Study guide
8.11 Implementation Planning, Piloting, and Solution Selection
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
8.11 Implementation Planning, Piloting, and Solution Selection
Key Takeaways Explain This Topic AI
The Pugh Concept Selection Matrix systematically evaluates candidate solutions against a baseline benchmark using weighted criteria, scoring alternatives as better (+), worse (-), or same (0).
Failure Mode and Effects Analysis (FMEA) in the Improve phase updates Risk Priority Numbers (RPN = S x O x D) to quantify risk reduction achieved through error-proofing and process changes.
A Pilot Study tests proposed solutions on a limited, representative scale to validate statistical hypothesis improvement, detect unintended operational side effects, and refine standard work.
Financial Return on Investment (ROI = [Net Financial Benefits / Total Project Cost] * 100%) and Net Present Value (NPV) provide rigorous financial verification required for executive tollgate sign-off.
Improve phase tollgate approval requires documented proof of root cause solution, Pugh selection, PFMEA risk reduction, successful pilot validation, and validated financial ROI.
Last updated: August 2026
The Improve phase transitions a project from root cause identification to solution design, risk evaluation, pilot testing, and full-scale implementation. Black Belts apply structured decision tools to select optimal solutions that maximize customer value while minimizing implementation risks.
- Systematic Solution Selection Tools
- 1. Solution Selection Matrix (Pugh Concept Selection Matrix)
Compares candidate solution concepts against baseline current process performance across key evaluation criteria (CTQs, cost, feasibility, risk):
Baseline Scoring : Current process is assigned a rating of 0 0 0 across all criteria.
Candidate Evaluation : Alternatives are rated as + 1 +1 + 1 (Better), 0 0 0 (Same), or − 1 -1 − 1 (Worse) relative to baseline.
Weighted Total : Sum of weighted scores guides selection of winning solution concept.
2. Effort vs. Impact Prioritization Matrix
Ranks potential solutions into four action quadrants:
Quick Wins (High Impact, Low Effort) : Implement immediately.
Major Projects (High Impact, High Effort) : Plan carefully; allocate capital resources.
Fill-Ins (Low Impact, Low Effort) : Implement if resources permit.
Thankless Tasks (Low Impact, High Effort) : Discard.
Failure Mode and Effects Analysis (FMEA) for Risk Mitigation
FMEA is a proactive risk assessment tool used to identify potential failure modes in proposed solutions before full-scale deployment.
Calculation of Risk Priority Number (RPN)
Every failure mode is scored on three 1-to-10 ordinal scales: RPN = Severity (S) × Occurrence (O) × Detection (D) \text{RPN} = \text{Severity (S)} \times \text{Occurrence (O)} \times \text{Detection (D)} RPN = Severity (S) × Occurrence (O) × Detection (D)
Rating Scale 1 (Best) 10 (Worst)
Severity (S) Minor inconvenience; no safety/functional impact. Catastrophic failure; safety hazard or severe regulatory violation.
Occurrence (O) Extremely unlikely; < 1 < 1 < 1 in 1 , 000 , 000 1,000,000 1 , 000 , 000 . Very high; persistent failure occurring > 1 > 1 > 1 in 10 10 10 units.
Detection (D) Automated 100 % 100\% 100% check will always detect error. Absolute uncertainty; no control mechanism exists to detect error.
Action Threshold : Failure modes with RPN > 100 > 100 > 100 or Severity ≥ 8 \ge 8 ≥ 8 require immediate corrective action plans.
Pilot Implementation Strategy
A Pilot Study is a small-scale, controlled trial of the proposed solution conducted prior to full rollout.
Objectives of a Pilot Study
Confirm real-world solution effectiveness without exposing entire customer base to risk.
Validate predicted financial COPQ savings.
Identify unexpected operational friction, operator training gaps, and measurement flaws.
Refine standard operating procedures (SOPs) based on empirical pilot feedback.
Poka-Yoke (Error-Proofing) Taxonomy
Poka-yoke mechanisms prevent human errors from turning into customer defects:
Prevention-Type Poka-Yoke : Physical design mechanisms that make it impossible for an error to occur (e.g., asymmetric electrical connectors that fit only one way).
Detection-Type Poka-Yoke : Automated sensors that immediately halt the process and alert operators if a non-conformance occurs (e.g., photoelectric light curtains verifying part placement).
Control-Type Poka-Yoke : Automatic shutoff switches that interrupt power if operating parameters exceed safety limits.
Pilot Validation & Statistical Conformance Metrics
Before launching full-scale implementation, pilot results are evaluated using formal statistical tests:
Two-Sample t t t -Test / Paired t t t -Test : Verify that mean process performance during pilot ( Y pilot Y_{\text{pilot}} Y pilot ) is significantly better than baseline ( Y baseline Y_{\text{baseline}} Y baseline ) at α = 0.05 \alpha = 0.05 α = 0.05 .
F F F -Test / Levene's Test : Verify that process variance during pilot ( σ pilot 2 \sigma^2_{\text{pilot}} σ pilot 2 ) is significantly lower than baseline.
Process Capability Re-Assessment : Confirm that pilot C p k C_{pk} C p k achieves ≥ 1.33 \ge 1.33 ≥ 1.33 target.
Detailed Cost-Benefit Analysis (CBA) & Financial ROI
Before final solution selection, Black Belts compute financial payback metrics:
1. Net Present Value (NPV)
Calculates the present value of future cash flows generated by the solution discounted at cost of capital ( r r r ): NPV = ∑ t = 1 n Cash Savings t ( 1 + r ) t − Initial Investment \text{NPV} = \sum_{t=1}^{n} \frac{\text{Cash Savings}_t}{(1 + r)^t} - \text{Initial Investment} NPV = t = 1 ∑ n ( 1 + r ) t Cash Savings t − Initial Investment
2. Payback Period
Calculates the exact elapsed time required for cumulative net financial savings to equal initial solution implementation capital: Payback Period = Total Initial Capital Investment Annualized Net COPQ Savings \text{Payback Period} = \frac{\text{Total Initial Capital Investment}}{\text{Annualized Net COPQ Savings}} Payback Period = Annualized Net COPQ Savings Total Initial Capital Investment
Benchmark Criterion : Industrial Six Sigma projects typically require a payback period of < 12 months < 12\text{ months} < 12 months and a positive NPV.
- Implementation Planning, Pilots, and Simulation
- Body of Knowledge section VII.C asks Black Belts to develop plans for implementing proposed
- improvements, including conducting pilot tests or simulations, and evaluate results to select the optimum
solution -- at the Evaluate level, the highest in this section.
The implementation plan
- Element Content
- Scope of the rollout Which lines, shifts, sites, product families, and in what sequence
- Sequence and dates Pilot, evaluation gate, phased rollout, full implementation
- Resources Capital, engineering hours, downtime windows, training time
- Prerequisites Tooling, software changes, supplier agreement, change control approval
- Training Who, on what, by when, to what competency standard
- Documentation SOPs, work instructions, control plan, FMEA update
- Risk plan What could go wrong at each step and the countermeasure (a PDPC is the natural tool)
- Contingency and rollback The trigger for reverting, and how the reversion is executed
- Acceptance criteria The measured result required before the next step is authorized
- The two elements most often missing are the rollback plan and the acceptance criteria . Without a
- rollback plan, a failed implementation becomes an argument rather than a decision; without acceptance
criteria agreed in advance, the pilot result is negotiated after the fact.
Simulation as an alternative to a physical pilot
Where a physical pilot is impossible, prohibitively expensive, or unsafe, simulation substitutes.
Technique Models Typical use
Discrete-event simulation Entities flowing through a queueing network over time Layout changes, staffing levels, buffer sizing, scheduling rules
Monte Carlo simulation Output distribution from input distributions Tolerance stacks, cycle-time distributions, financial risk
Process mapping walkthrough Logical flow with subject-matter experts Transactional processes, low-cost first pass
- Physical mock-up or cardboard modelling Layout and reach Cell design, workstation ergonomics
- Simulation earns its cost when it explores many alternatives cheaply -- comparing six buffer
- configurations in an afternoon -- or when the interaction between variation and queueing makes the
- outcome genuinely unpredictable by inspection. Its limitation is that it can only be as good as its
- input distributions and its assumptions, so a simulation result should be treated as a prediction to be
confirmed, exactly like a DOE model.
Designing the pilot
A pilot is an experiment, and it should be designed like one.
Define the acceptance criteria first , in the project's primary metric, with the practical threshold.
Size it. A pilot too short or too small to detect the improvement claimed proves nothing; use the
sample-size calculation, not a convenient duration.
- Cover the sources of variation the full process contains: all shifts, both material lots, the
- difficult product variants. A pilot run only on day shift with the best operator predicts nothing about
Sunday night.
Measure the consequential metrics too , so a gain bought at another metric's expense is visible.
Include a control where possible: an unchanged parallel line or the same line before and after with
the same measurement definition.
Plan the duration to cover at least one full cycle of the dominant time pattern.
- Evaluating pilot results to select the optimum solution
- Compare the pilot outcome against the acceptance criteria using a hypothesis test, not an eyeball
comparison of two averages. Then decide among four outcomes:
- Result Decision
- Meets acceptance criteria, no consequential metric degraded Proceed to full implementation
- Statistically significant but below the practical threshold Do not implement; the cost is not repaid
- Improves the primary metric but degrades a consequential metric Redesign; the solution moved the problem
- Inconclusive Extend the pilot or increase the sample; do not implement on an unconfirmed result
- Where several candidate solutions were piloted, select using the same weighted criteria that were agreed
- before the pilots -- effectiveness, cost, implementation time, risk, sustainability -- rather than
- re-weighting after seeing the results. Recording the criteria and weights in the charter is what makes
that discipline possible.