5-Step Improvement Method After 10 Years in Quality Management, to Save You Time and Effort
Step 1: Define the Problem, Don’t Rush to Conclusions
What do quality management professionals fear the most?
They fear that after working hard on an improvement plan, it fails to be implemented. Or even if it is implemented, the results are not significant, and the problem resurfaces a few months later.
I have seen too many quality professionals trapped in the vicious cycle of "identifying issues → issuing reports → driving improvements → issues resurfacing → re-identifying issues."
Today, I will share a proven 5-step improvement method, summarized from my practical experience across multiple industry projects. No beating around the bush, just the essential content.
Step 2: Root Cause Analysis, Use Tools Instead of Guesswork
Once the problem is clearly defined, the next step is to find the root cause.
A common pitfall is "empiricism" — senior engineers rely on their experience and say, "It must be the XXX issue," and the team follows suit.
Experience can provide direction, but it cannot replace verification.
I recommend three time-tested tools:
Fishbone Diagram (Ishikawa Diagram) Expand along the six dimensions of "people, machines, materials, methods, environment, and measurement" to ensure no potential root causes are overlooked. When drawing the diagram, each branch should be questioned to the third level to identify the true "root cause."
5 Whys Analysis Continuously ask "why" five times for a given issue. Note: 5 Whys does not necessarily mean asking exactly five times, but rather continuing until you find a "root cause that can be acted upon."
Hypothesis Verification Table For each potential root cause, answer: What data do I need to verify this hypothesis? If the verification fails, what is my alternative hypothesis?
A Real Case:
A certain electronics factory had a persistently high defect rate in PCBA welding. The team, based on experience, concluded it was a "soldering flux issue" and planned to change suppliers.
After using a fishbone diagram, they discovered that besides the soldering flux, "welding temperature profile" and "PCB incoming material storage conditions" were also potential root causes.
Further verification revealed that the true root cause was that the PCB incoming material was not used within the specified time after being opened.
Without systematic analysis, changing the soldering flux would not have solved the problem and would have unnecessarily increased costs.
Step 3: Develop Countermeasures, Design Error-Proofing Mechanisms
After identifying the root cause, a core principle in developing countermeasures is: error-proofing is better than inspection, and inspection is better than training.
What does this mean?
Let's illustrate with three real cases:
Case A: Relying on Training "Welders not following standard procedures → enhance training," Effect: Improved for two weeks after training, then reverted to the original state.
Case B: Relying on Inspection "Possible incorrect assembly of products → add a 100% inspection step," Effect: Identified missing parts, but increased rework costs.
Case C: Relying on Error-Proofing "Possible incorrect assembly of products → design a physical positioning structure to prevent incorrect assembly," Effect: Impossible to make a mistake.
This is the core concept of error-proofing (Poka-yoke).
When developing countermeasures, prioritize them as follows:
- Elimination — Remove the step that causes the problem
- Substitution — Replace with a more reliable process/material
- Error-Proofing — Design physical/logical mechanisms to prevent errors
- Simplification — Simplify operations to reduce the likelihood of errors
- Inspection — Add inspection steps
- Training — Use as a supplementary measure
In most cases, we tend to start from the 6th level. Experts start from the 1st level.
Step 4: Pilot Verification, Use Small Data to Prove Big Value
Once the countermeasures are developed, don't rush to implement them fully.
A principle: Pilot first, then roll out.
The purpose of piloting is to verify the effectiveness of the solution with the least cost.
Three Key Points for Piloting:
Select Representative Samples — Choose a shift, a production line, or a product model. Avoid selecting the best or worst cases; the samples should be representative.
Set Clear Acceptance Criteria — What are the comparison metrics before and after the improvement? What is the target value? When is the acceptance time point?
Record Execution Deviations — What execution deviations occurred during the pilot? Recording these deviations is very valuable for subsequent full-scale implementation.
Data Presentation:
I once helped a client optimize their incoming quality control (IQC) process. During the pilot phase, we selected Class A materials (accounting for 15% of total incoming materials), and the results were excellent — inspection efficiency improved by 40%, and the inspection omission rate decreased by 60%.
However, during full-scale implementation, we found that the conditions for Class B and C materials were entirely different from Class A and required adaptive adjustments. Without a pilot, the full-scale implementation would likely have failed.
Step 5: Standardization and Horizontal Expansion
After the improvement plan is verified to be effective, the most important and often overlooked step is standardization.
What is standardization?
It is not just writing a document and letting it gather dust on a server. Instead, it involves embedding the improved methods into formal work processes to ensure they are consistently executed.
Three Levels of Standardization:
Level 1: Documentation Update work instructions, inspection specifications, and process documents. Record the changes in the version updates.
Level 2: Training All relevant personnel must complete the training and pass the assessment. Training records for critical operations should be retained.
Level 3: Systemization Embed control requirements into the system. For example, set parameter lock ranges in the MES system, with automatic alerts for out-of-range values, rather than relying on operators to check them voluntarily.
After standardization, horizontally expand to other similar processes or products.
A common mistake to avoid: When expanding horizontally, don't copy the approach directly; make "adaptations" — different processes have different conditions and may require appropriate adjustments.
Summary: The Complete Map of the 5-Step Method
Step 1 [Define the Problem] → Describe the facts, don’t look for causes
↓
Step 2 [Root Cause Analysis] → Use tools to verify, don’t rely on experience
↓
Step 3 [Develop Countermeasures] → Prioritize error-proofing, use training as a fallback
↓
Step 4 [Pilot Verification] → Test in a small scope, let data speak
↓
Step 5 [Standardization] → Embed into processes, expand horizontally
This method is not complicated, but few people truly follow it through.
Because each step involves fighting human nature — we are eager to draw conclusions, lazy to verify, want to implement quickly, and neglect standardization.
However, quality management is precisely a field where "slow is fast." The more time spent on the first two steps, the fewer rework issues will arise later.
Next time you encounter a quality issue, make a commitment to yourself: clearly define the problem before taking action.
This is more important than any tool.
This article is original content. Please contact the author for reprints.