A production line has a quality problem.
The natural reaction is often:
“We know what is causing it. Let’s fix the machine.”
Sometimes that works.
Sometimes the defect returns two weeks later because the team corrected the symptom rather than the real cause.
Six Sigma takes a more disciplined approach. Instead of starting with a solution, it starts with evidence.
The standard improvement sequence is:
- Define
- Measure
- Analyze
- Improve
- Control
This is known as DMAIC. ASQ describes DMAIC as a data-driven approach for improving existing processes that are not meeting performance standards or customer expectations. ISO 13053-1 also defines DMAIC as the primary Six Sigma process-improvement methodology.
What Is Six Sigma Quality Improvement?
Six Sigma focuses on reducing defects and unwanted process variation using structured problem solving and data.
It can be applied to problems such as:
- dimensional rejection;
- assembly defects;
- excessive scrap;
- inconsistent cycle times;
- customer complaints;
- coating variation;
- packaging defects;
- repeated rework.
The important point is that Six Sigma is not simply a collection of statistical tools.
The tools support a structured improvement process.
DMAIC Stage |
Main Question |
|---|---|
Define |
What problem are we solving? |
Measure |
How is the process performing now? |
Analyze |
What is actually causing the problem? |
Improve |
Which solution removes the cause? |
Control |
How do we prevent the problem returning? |
Implementation Steps and Best Practices
Step 1: Define the Problem Clearly
Start with a specific problem.
Avoid statements such as:
“Quality is poor.”
Use something measurable:
“Diameter-related rejection on CNC Line 2 increased during production of Product A.”
Then define:
- project scope;
- customer requirement;
- affected process;
- improvement objective;
- project team;
- expected business impact.
ASQ recommends creating a project charter during the Define phase and identifying customer requirements through approaches such as Voice of the Customer.
Keep the project manageable.
Trying to “improve quality across the whole factory” is too broad for a useful DMAIC project.
Step 2: Measure the Current Process
Do not begin changing the process yet.
First establish what is actually happening.
Collect data such as:
- defect quantity;
- defect type;
- machine;
- product;
- shift;
- operator;
- material batch;
- process setting;
- measurement result.
Suppose a factory produces 10,000 components and 600 require rework.
The baseline rework rate is:
600 ÷ 10,000 × 100 = 6%
Now the team has a starting point that can later be compared with the improved process.
But there is another important question:
Can the measurement itself be trusted?
ASQ includes validation of the measurement system within the Measure phase. NIST’s measurement guidance likewise emphasizes repeatability, reproducibility and stability when characterizing measurement processes.
If two inspectors measure the same part differently, the team may be analyzing measurement variation rather than manufacturing variation.
Step 3: Analyze the Root Cause
This is where Six Sigma teams need discipline.
Do not jump from:
“Defects are high”
to:
“The machine needs replacement.”
Break the problem down.
Useful tools include:
- Pareto charts;
- cause-and-effect diagrams;
- 5 Whys;
- process maps;
- FMEA;
- scatter plots;
- statistical analysis.
ASQ recommends root-cause analysis and FMEA among the tools available during the Analyze phase.
Imagine a machining defect.
Possible causes may include:
- Machine
- spindle condition
- Method
- incorrect setting
- Material
- hardness variation
- Tool
- excessive wear
- Measurement
- gauge variation
- People
- inconsistent setup
Now test these possibilities against actual data.
Do not select the most convenient explanation.
Select the cause supported by evidence.
Step 4: Improve the Process
Once the important cause is understood, develop countermeasures.
Suppose analysis shows that most dimensional variation appears after a cutting tool reaches a certain wear condition.
Potential improvements might include:
- revised tool-change criteria;
- tool-condition monitoring;
- improved setup procedure;
- mistake-proofing;
- parameter adjustment.
Do not immediately roll the change across the entire factory.
Test it.
ASQ’s DMAIC guidance recommends evaluating potential solutions and using tools such as designed experiments when several factors may influence the outcome.
Compare:
Before Improvement
versus
After Improvement
using the same measurement method.
The question is not whether everyone likes the new solution.
The question is:
Did the process performance actually improve?
Step 5: Control the Improved Process
This is where many improvement projects become weak.
The team solves the problem, celebrates, and moves to another project.
Three months later, the defect returns.
Control means making the improved condition part of normal operation.
Possible controls include:
- standardized work;
- control plans;
- operator training;
- preventive checks;
- mistake-proofing;
- visual controls;
- statistical process control;
- clear reaction plans.
NIST explains that control charts are used to monitor process characteristics over time and determine whether process behavior remains stable.
For example:
- Normal condition
- continue production
- Warning signal
- investigate
- Out-of-control condition
- stop, contain and follow reaction plan
The exact response depends on the process and risk.
Process Stability Comes Before Capability
There is one technical point engineers should not overlook.
A process may produce parts inside specification today while still behaving unpredictably.
NIST states that process stability should be established before meaningful process-capability assessment. Process capability compares the performance of a stable process with specification limits.
In simple terms:
First make the process predictable.
Then determine whether that predictable process is good enough to meet requirements.
That distinction prevents teams from relying blindly on capability numbers from an unstable process.
Common Six Sigma Implementation Mistakes
Avoid:
- selecting projects that are too broad;
- jumping directly to solutions;
- collecting data without validating measurement;
- confusing correlation with root cause;
- using complicated statistics when simpler analysis is enough;
- implementing changes without a pilot;
- failing to update standardized work;
- closing the project without a control plan.
A useful rule is:
Do not use a statistical tool simply because Six Sigma says statistics are important.
Use the simplest valid method capable of answering the engineering question.
Conclusion
Successful Six Sigma quality improvement follows a disciplined sequence:
- Define the Problem
- Measure Reality
- Analyze Root Cause
- Improve the Cause
- Control the New Process
The most important part is not the terminology.
It is the discipline of not deciding on the solution before understanding the evidence.
A factory does not become better because it completes a DMAIC presentation.
It improves when the project leaves behind a process that is more stable, more predictable and less likely to create the same defect again.