Correct Usage of the PDCA Cycle
1. Core Definition and Value of the PDCA Cycle
The PDCA Cycle (also known as the Deming Cycle) was proposed by Edwards Deming. It is a continuous improvement methodology that follows the sequence of "Plan-Do-Check-Act." The core of PDCA is to achieve problem-solving and capability enhancement through closed-loop management, making it applicable to all scenarios that require continuous improvement, such as quality management, process optimization, and personal development.
Core Value: Addressing the Issue of "Doing Without Summarizing, Changing Without Persisting"
The core value of PDCA is to transform improvements from "one-time actions" into a "continuous cycle system." According to statistics, companies that implement the PDCA cycle see a reduction in problem recurrence of over 60%.
PDCA is not a one-way sequence of "Plan → Do → Check → Act," but a spiraling cycle—each cycle resolves a batch of issues, standardizes the results, and then initiates the next cycle based on new objectives, achieving continuous iteration.
2. Key Actions and Practical Points of the Four Stages of the PDCA Cycle
Table of Key Actions and Practical Points
| Stage | Key Actions | Key Tools | Practical Standards |
|---|---|---|---|
| Plan (Plan) | 1. Identify problems/goals; 2. Analyze root causes; 3. Develop a plan (5W2H); 4. Set verification metrics | Fishbone diagram, 5 Whys, 5W2H, SMART principle | The plan must clearly define "what to do, who will do it, when to complete it, and how to verify it" |
| Do (Do) | 1. Training and communication; 2. Pilot implementation; 3. Record process data; 4. Timely adjustment of execution deviations | Gantt chart, execution record sheet, on-site inspection | Prioritize pilot implementation (small scale) to avoid risks associated with full-scale promotion |
| Check (Check) | 1. Compare actual results with targets; 2. Analyze deviation causes; 3. Verify improvement effectiveness; 4. Identify new issues | Data comparison sheet, Pareto chart, deviation analysis report | Use data to speak, avoid "subjective judgment of improvement effectiveness" |
| Act (Act) | 1. Standardize effective results; 2. Transfer unresolved issues to the next PDCA cycle; 3. Review and summarize experiences | SOP, standardization documents, review report | Effective results must be institutionalized to prevent regression |
1. Plan (Plan): Accurately Identify Problems to Avoid Blind Actions
Planning is the core of PDCA. 80% of improvement failures are due to "unclear problem identification and inadequate root cause analysis" in the planning stage.
(1) Problem Identification: Use "Specific Data" Instead of "Vague Descriptions"
- Incorrect statement: "Low product pass rate."
- Correct statement: "In January 2026, the pass rate of injection-molded parts was 85%, below the target of 95%, with the primary defect being surface scratches (60% of defects)."
(2) Root Cause Analysis: Use 5 Whys to Find the Fundamental Cause
Example: 5 Whys analysis for "surface scratches on injection-molded parts":
- Why1: Surface scratches → Friction during mold ejection.
- Why2: Friction during mold ejection → Lack of lubrication on the mold surface.
- Why3: Lack of lubrication → Operators did not apply the mold release agent as required.
- Why4: Not applying as required → No inspection checklist, relying solely on experience.
- Why5: No inspection checklist → Lack of standardized work procedures.
(3) Develop a Plan: Use 5W2H to Clarify All Details
5W2H: What (what to do), Why (why to do it), Who (who will do it), When (when to complete it), Where (where to do it), How (how to do it), How much (how much resource to invest).
2. Do (Do): Pilot Implementation to Reduce Execution Risks
Avoid "all-at-once implementation" in the execution stage. Prioritize 1-2 production lines or 1 team for pilot implementation, focusing on "recording the process and timely correction of deviations."
Common Mistake: Full-Scale Promotion Without Piloting
A common mistake is to directly promote the plan across the entire workshop after it is developed. This can lead to issues that are difficult to quickly adjust, resulting in improvement failure.
3. Check (Check): Use Data to Verify Improvement Effectiveness
The core of the check stage is to "compare target values with actual values." For example, after the pilot, the pass rate of injection-molded parts increased from 85% to 96%, and the defect rate for surface scratches decreased from 60% to 5%, proving the effectiveness of the improvement.
4. Act (Act): Standardize Results to Prevent Regression
This is the most easily overlooked stage of PDCA. If effective results are not standardized, problems will quickly reoccur after the pilot ends. For example, include the "mold release agent application inspection checklist" in the SOP, requiring operators to inspect every 2 hours and supervisors to check daily.
3. Eight Common Misunderstandings of the PDCA Cycle
Misunderstanding 1: Skipping the Plan Stage and Directly Moving to Do
Seeing a problem and immediately taking action, such as "increasing inspection personnel due to low pass rates," without analyzing the root cause, can lead to superficial improvements.
Misunderstanding 2: Setting Goals in the Plan Stage Without Analyzing Root Causes
Setting only a "pass rate improvement to 95%" goal without analyzing "why the pass rate is low" results in a lack of targeted planning.
Misunderstanding 3: Full-Scale Promotion in the Do Stage Without Piloting
This approach is high-risk and costly to adjust. Once issues with the plan are discovered, the losses are irreparable.
Misunderstanding 4: Subjective Judgment in the Check Stage Without Using Data
"Feeling that the improvement is effective" or "everyone gives good feedback" without data support cannot verify the real effectiveness.
Misunderstanding 5: Summarizing Only in the Act Stage Without Standardizing
Improvement results remain as "verbal experiences" without being institutionalized into processes or systems, leading to problem recurrence.
Misunderstanding 6: Ending the PDCA Cycle After One Cycle Without Continuity
Thinking that "one PDCA cycle solves all problems" ignores the core logic that "unresolved issues need to be transferred to the next cycle."
Misunderstanding 7: Insufficient Participation, Only a Few People Driving
PDCA is a tool for all employees to improve. Relying solely on the quality department to drive it, without the involvement of frontline employees, results in poor execution.
Misunderstanding 8: Pursuing a "Perfect Plan" and Delaying Execution
Over-focusing on the details of the plan can lead to "3 months of planning, 1 day of execution," missing the opportunity for improvement.
4. Cross-Scenario Application Cases of the PDCA Cycle
Case 1: Production Quality Improvement (Manufacturing)
An electronics factory had a 10% defect rate for solder joints. Through the PDCA cycle:
- Plan: The main cause of defects was unstable soldering iron temperatures. A "soldering iron temperature inspection checklist" was developed, with a target defect rate of 2%.
- Do: Piloted on 2 production lines, with temperature inspections and records every hour.
- Check: After a week of piloting, the defect rate dropped to 1.8%, meeting the target.
- Act: The temperature inspection was incorporated into the SOP and promoted across the workshop. The "occasional cold soldering" issue was transferred to the next PDCA cycle.
Case 2: Process Optimization (Service)
A customer service center had response times exceeding 5 minutes. Through the PDCA cycle:
- Plan: The root cause was "no standard answers for common issues, requiring repeated queries." A "script library for common issues" was developed, with a target response time of ≤3 minutes.
- Do: Trained 10 customer service representatives to pilot the use of the script library.
- Check: After the pilot, response times decreased to 2.5 minutes, and customer satisfaction increased by 20%.
- Act: The script library was standardized and used by the entire team, with regular updates to the content.
Case 3: Personal Capability Enhancement (General)
A personal goal of "reading 2 books per month" was not met. Through the PDCA cycle:
- Plan: The root cause was "no fixed reading time, wasting fragmented time." A plan was developed to read "from 20:00 to 21:00 every day," with a target of 2 books per month.
- Do: Executed for 2 weeks, recording daily reading times.
- Check: Read 1 book in 2 weeks, meeting the target, with only 1 day missed due to overtime.
- Act: Fixed the reading time to "20:00 to 21:00," and read the next day if overtime occurs, forming a personal reading habit.
5. Practical Tool Kit for the PDCA Cycle (Downloadable)
To help quickly implement PDCA, a set of standardized templates has been compiled:
- PDCA Cycle Plan Form (5W2H Version)
- 5 Whys Root Cause Analysis Template (Excel Version)
- PDCA Check Stage Data Comparison Form
- PDCA Improvement Results Standardization SOP Template
- PDCA Cycle Review Report Template
Download PDCA Practical Tool Kit
6. Summary
The core of the PDCA cycle is not just "following the steps once," but "establishing a mindset of continuous improvement"—precise planning, steady execution, objective checking, and solidification in the action stage, all of which are essential.
For companies, PDCA is the "underlying logic" of quality management, adaptable to all scenarios including production, service, and management. For individuals, PDCA is an "effective method" for self-improvement, making goals achievable and actions traceable.
Remember: The value of PDCA lies in the "cycle." Each cycle resolves a batch of issues, and continuous cycling leads to continuous progress. This is the true significance of the Deming Cycle.