Study guide
11.2 Plan-Do-Check-Act (PDCA) & Solution Selection
ASQ Certified Six Sigma Yellow Belt CSSYB
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About the ASQ CSSYB Exam How to Use This Study Guide
2 Chapter 1: Six Sigma & Lean Fundamentals
1.1 Six Sigma Foundations, Principles & History 1.2 Lean Foundations, Principles & The 8 Wastes 1.3 Six Sigma Roles & Responsibilities
3 Chapter 2: Team Basics & Dynamics
2.1 Team Types & Stages of Team Evolution 2.2 Team Decision-Making & Idea Generation Tools 2.3 Communication Methods & Meeting Management
4 Chapter 3: Quality Tools & Six Sigma Metrics
3.1 The 7 Basic Quality Tools 3.2 Six Sigma Process Performance Metrics & COPQ
5 Chapter 4: Define Phase — Project Identification & Scope
4.1 Voice of the Customer (VOC) & Critical-to-Quality (CTQ) 4.2 Project Selection & Stakeholder Analysis 4.3 Process Definition with SIPOC & Supply Chain Basics
6 Chapter 5: Define Phase — Project Management Basics
5.1 The Project Charter & Problem Statements 5.2 Project Planning: WBS, Gantt Charts & Communication Plans 5.3 Project Management Tools & Tollgate Reviews
7 Chapter 6: Measure Phase — Data Collection & Statistics
6.1 Basic Statistics: Central Tendency & Dispersion 6.2 Data Types & Classification 6.3 Data Collection Plans, Operational Definitions & Sampling 6.4 Data Collection Techniques: Check Sheets, Checklists, Surveys & Interviews
8 Chapter 7: Measure Phase — Measurement System Analysis
7.1 Measurement System Fundamentals: Precision, Accuracy & Bias 7.2 Gauge Repeatability & Reproducibility (GR&R)
9 Chapter 8: Analyze Phase — Process & Root Cause Analysis
8.1 Process Analysis: 5S & Value Analysis 8.2 Failure Mode and Effects Analysis (FMEA) 8.3 Root Cause Analysis: 5 Whys, Process Mapping, 8D, Force-Field & Matrix Charts
10 Chapter 9: Analyze Phase — Corrective Action & Variation
9.1 Corrective & Preventive Action Processes 9.2 Common Cause vs Special Cause Variation 9.3 Basic Distribution Types: Normal, Binomial & Poisson
11 Chapter 10: Analyze Phase — Relationships & Hypothesis Testing
10.1 Correlation & Scatter Plots 10.2 Simple Linear Regression & Prediction 10.3 Hypothesis Testing Concepts: Hypotheses, Errors & P-Values
12 Chapter 11: Improve Phase — Implementation Techniques
11.1 Kaizen & Kaizen Blitz Events 11.2 Plan-Do-Check-Act (PDCA) & Solution Selection 11.3 Cost-Benefit Analysis & Financial Validation
13 Chapter 12: Control Phase — Sustaining Improvements
12.1 Control Plans & Process Monitoring 12.2 Statistical Process Control: X-bar & R Charts 12.3 Document Control, Standard Operating Procedures & Project Hand-off
11.2 Plan-Do-Check-Act (PDCA) & Solution Selection
Key Takeaways Explain This Topic AI
The Plan-Do-Check-Act (PDCA) cycle, formulated by Walter Shewhart and popularized by W. Edwards Deming, provides an iterative scientific framework for testing and implementing process solutions.
The 'Do' stage specifically mandates small-scale pilot testing or prototyping to collect empirical data without introducing enterprise-wide operational risk.
Solution Selection Matrices evaluate candidate countermeasures using weighted operational criteria such as CTQ impact, implementation cost, feasibility, and time to deploy.
Controlled pilots allow project teams to validate operational performance, uncover unintended downstream consequences, and refine Standard Operating Procedures prior to broad rollout.
The 'Act' stage standardizes verified improvements across the enterprise through updated documentation, mistake-proofing, and workforce training, or iterates if targets are missed.
Last updated: September 2026
Plan-Do-Check-Act (PDCA) & Solution Selection
Quick Answer: The Plan-Do-Check-Act (PDCA) cycle, also known as the Deming wheel or Shewhart cycle, is an iterative scientific four-stage management method for continuous process improvement. In the Improve phase, teams brainstorm countermeasures addressing root causes verified in Analyze, evaluate them using weighted Solution Selection Matrices, and test selected solutions via controlled small-scale pilots during the "Do" stage. Results are evaluated against baseline data in "Check/Study", and verified improvements are standardized and scaled in "Act". Independent CSSYB study guide by ExamFinch.
Foundations of the PDCA / PDSA Cycle
The Plan-Do-Check-Act (PDCA) cycle provides the scientific foundation for structured quality improvement. The framework traces to Dr. Walter A. Shewhart , the Bell Telephone Laboratories statistician who pioneered statistical process control and, in 1939, described quality control as a cycle of specification, production, and inspection. Dr. W. Edwards Deming taught a four-step version of that cycle to Japanese managers in 1950, and Japanese practitioners turned it into the Plan-Do-Check-Act cycle.
Deming frequently termed the model PDSA (Plan-Do-Study-Act) , deliberately substituting "Study" for "Check." Deming argued that "check" implied a passive inspection, whereas "study" emphasized active statistical analysis, reflection on empirical findings, and understanding the root mechanisms of process behavior. In Six Sigma, PDCA serves as the operational engine of the Improve phase , moving teams from diagnostic hypotheses to verified, scalable solutions.
Rather than a closed circle, PDCA operates as an upward spiral of continuous learning . Each cycle deepens process understanding, eliminates operational variation, and elevates the baseline standard for future performance.
The Four Stages of PDCA in the Improve Phase
Applying PDCA during solution implementation requires disciplined execution across four sequential stages:
Plan: The team reviews the vital few input variables ( X X X ) confirmed during the Analyze phase and establishes clear, quantifiable SMART improvement targets. Members generate candidate countermeasures and design a detailed pilot implementation plan, including sample sizes, trial durations, and control metrics.
Do: The team executes the selected countermeasures on a small, controlled scale (such as a single workstation, one operating shift, or an isolated pilot cell). Running a limited pilot allows the team to observe real-world performance and collect empirical data without introducing enterprise-wide operational risk.
Check (Study): The team collects pilot performance data and evaluates it against pre-improvement baselines. Members assess capability gains ( C p , C p k C_p, C_{pk} C p , C p k ), defect reductions (DPMO), and cycle time changes. The team also checks for unintended consequences, such as bottleneck migrations or operator ergonomics issues.
Act: If the pilot achieves performance goals, the team standardizes the countermeasure enterprise-wide by updating Standard Operating Procedures (SOPs), installing mistake-proofing (Poka-Yoke), and training staff across all shifts. If the pilot falls short, the team analyzes the gaps, adjusts hypotheses, and initiates the next iterative PDCA cycle.
Solution Generation & Brainstorming Countermeasures
During the Analyze phase, teams isolate the root causes that drive quality variation. In the Improve phase, focus shifts to generating innovative countermeasures that eliminate or control those root causes.
To avoid premature convergence on obvious or biased fixes, teams utilize structured ideation techniques:
Brainwriting (6-3-5 Method): Six participants write three ideas on worksheets within five minutes, passing them silently across six rounds. This produces 108 distinct ideas while eliminating loud-voice domination and executive bias.
Nominal Group Technique (NGT): Participants silently generate ideas, post them to a visual board, discuss each concept for clarity, and vote silently using weighted scoring to prioritize top candidates.
Benchmarking & Analogy Thinking: Teams examine how analogous industries solve similar handling or assembly challenges, adapting proven concepts to their operational environment.
The Solution Selection Matrix (Prioritization Matrix)
When multiple candidate countermeasures emerge, unstructured debates often lead to political compromise or executive preference. A Solution Selection Matrix (or Prioritization Matrix) establishes mathematical objectivity by evaluating alternative solutions against weighted operational criteria.
Evaluation Criteria and Weightings
A balanced matrix evaluates both customer-facing quality gains and organizational constraints:
Impact on Critical-to-Quality (CTQ) / Defect Reduction (30% - 40%): Degree to which the solution eliminates the verified root cause and reduces process defects.
Implementation Cost / Capital Expense (20% - 30%): Total capital expense, tooling costs, software licenses, and physical installation labor.
Technical & Operational Feasibility (15% - 25%): Ease of operating and maintaining the solution using existing staff and equipment.
Time to Implement / Speed to Value (15% - 25%): Duration required to design, procure, test, and fully deploy the solution.
Each solution receives a score (typically 1 to 5) per criterion. The weighted composite score is calculated using the formula: Composite Score = ∑ ( Rating i × Weight i ) \text{Composite Score} = \sum (\text{Rating}_i \times \text{Weight}_i) Composite Score = ∑ ( Rating i × Weight i )
Worked Example: Packaging Line Countermeasures
Consider three candidate solutions designed to eliminate missing product manuals:
Solution A: Two-person manual inspection checklist.
Solution B: Inline optical barcode scanner with automated diverter gate.
Solution C: Fully automated robotic packaging cell.
Evaluation Criteria Weight Solution A: Manual Checklist (1-5) Solution A: Weighted Solution B: Barcode Gate (1-5) Solution B: Weighted Solution C: Robotic Cell (1-5) Solution C: Weighted
CTQ Defect Reduction 0.35 2 (Human error persists) 0.70 5 (100% automated check) 1.75 5 (100% automated check) 1.75
Implementation Cost 0.25 5 (Negligible cost) 1.25 4 (Low sensor cost) 1.00 1 (Very high capital outlay) 0.25
Operational Feasibility 0.20 4 (Simple to mandate) 0.80 4 (Easily mounted) 0.80 2 (Complex factory rework) 0.40
Implementation Speed 0.20 5 (Implemented in 1 day) 1.00 4 (Installed in 2 weeks) 0.80 1 (Requires 9-month delivery) 0.20
Total Composite Score 1.00 -- 3.75 -- 4.35 -- 2.60
Analysis: Solution A is inexpensive but fails to reliably eliminate defects. Solution C provides perfect quality but carries excessive capital costs and lengthy lead times. Solution B achieves the highest composite score (4.35) , balancing superior defect prevention with affordable cost and rapid execution.
Pilot Testing: Controlled Deployment & Risk Mitigation
Before committing capital and organizational resources to full-scale deployment, teams execute a controlled pilot test during the "Do" stage. A pilot test is a small-scale implementation conducted in an operational sandbox—such as a single production line, one shift, or a designated customer segment.
Strategic Objectives of a Pilot Test
Empirical Verification: Proves that the solution reduces defects under real operating conditions, including shift changes, raw material lots, and operator variation.
Uncovering Side Effects: Identifies unforeseen bottlenecks, ergonomic friction, or software latency before they disrupt plant-wide operations.
Refining Standard Work: Exposes ambiguities in draft work instructions, allowing teams to clarify procedures and refine visual controls based on operator feedback.
Building Frontline Champions: Pilot operators become credible peer advocates, easing cultural resistance when the change rolls out across the broader organization.