Design for Six Sigma (DFSS) turns customer requirements into measurable “critical-to-quality” (CTQ) characteristics, then designs and verifies processes so they perform reliably in real conditions. You’ll see the DFSS roadmap—DMADV: Define, Measure, Analyze, Design, Verify—along with key tools like Quality Function Deployment (QFD) and Taguchi methods for parameter design and robust engineering. The page also connects performance goals with financial results, such as cost of poor quality and realized savings.
Key Takeaways
- The original Six Sigma methodology was developed at Motorola in 1986
- Motorola reported that Six Sigma reduced defects by a factor of 10 between 1987 and 1992
- Motorola’s Six Sigma program saved an estimated $16 billion from 1986 to 2000
- Design for Six Sigma (DFSS) uses the concept of “critical-to-quality” (CTQ) characteristics
- DMADV is Define, Measure, Analyze, Design, Verify
- Quality Function Deployment (QFD) is one of the primary DFSS tools
- Six Sigma aims to reduce defects to 3.4 per million opportunities at a 1.5 sigma shift
- The 1.5 sigma shift corresponds to a 4.5 sigma centered process yielding 3.4 DPMO after accounting for long-term drift
- Six Sigma level performance corresponds to 99.379% yield
- Six Sigma projects use financial metrics such as cost of poor quality and realized savings; GE’s Six Sigma yielded $12 billion savings (1995–2001)
- Motorola estimated $16 billion in savings from 1986 to 2000
- AlliedSignal reported more than $600 million in benefits in 1997 from Six Sigma
Explore how Six Sigma and DFSS using CTQ, QFD, and Taguchi delivered massive defect and savings results.
Related reading
01 · Category
History & Adoption28 stats
01
The original Six Sigma methodology was developed at Motorola in 1986
02
Motorola reported that Six Sigma reduced defects by a factor of 10 between 1987 and 1992
03
Motorola’s Six Sigma program saved an estimated $16 billion from 1986 to 2000
04
General Electric estimated that Six Sigma delivered more than $300 million in savings in its first year (1996)
05
Jack Welch described Six Sigma as a top priority at GE, and GE targeted $10 billion in savings from Six Sigma by 2000
06
GE reported that Six Sigma saved over $12 billion from 1995 to 2001
07
AlliedSignal (later Honeywell) reported savings of more than $600 million in 1997 from Six Sigma
08
Honeywell reported that its Six Sigma program generated cumulative savings of $700 million in 2000
09
Ford launched Six Sigma in 1999 as part of its quality transformation
10
Toyota adopted Six Sigma methodologies as part of its business excellence approach; Toyota Motor Corporation implemented Six Sigma starting around the early 2000s
11
In the 1990s, Six Sigma spread from manufacturing to services and transactions
12
A survey by ASQ reported that 67% of organizations used Six Sigma in some form
13
ASQ’s 2016 “State of Six Sigma” survey found 68% of organizations used Six Sigma
14
ASQ’s 2017 “Six Sigma and Lean Manufacturing” report found 56% of organizations used Six Sigma
15
ASQ’s “Six Sigma in Services” article reported that over 50% of Six Sigma projects were in service functions
16
A 2004 ASQ report “Six Sigma: A Critical Review” noted that the number of Six Sigma-related certifications rose rapidly during the 1990s
17
The ASQ certified Six Sigma programs include certifications at Black Belt and Green Belt levels
18
The term “Design for Six Sigma” was formalized in the early 2000s through literature and toolkits
19
The original DMAIC roadmap is associated with Six Sigma execution; it stands for Define, Measure, Analyze, Improve, Control
20
The DMADV roadmap is associated with Six Sigma for new designs; it stands for Define, Measure, Analyze, Design, Verify
21
In a GE case, Six Sigma projects were expected to produce financial benefits within a defined timeline, often 4–6 months
22
A meta-analysis in Quality Engineering reported that Six Sigma improvements often target process capability and variation reduction
23
The book “Lean Six Sigma” by George provides historical adoption context that Six Sigma became mainstream across many industries
24
In 2003, the U.S. Department of Defense began initiatives to apply Six Sigma/Lean for performance improvement
25
ASQ’s Six Sigma body of knowledge identifies customer requirements (CTQs) as a foundational element
26
A key Six Sigma adoption trend: many organizations used training pipelines of Green Belts and Black Belts; ASQ certification tracks exist
27
In the context of DFSS, DMADV is commonly cited; a standard reference is the ASQ resource on DMADV
28
A study in Quality Engineering reported that Six Sigma correlates with improved operational performance metrics
Interpretation
History & Adoption Interpretation
Across the key years of early adoption, Six Sigma moved from being developed at Motorola in 1986 to producing dramatic scale-up results, with Motorola cutting defects by a factor of 10 and saving $16 billion by 2000, then GE accelerating the impact further by targeting $10 billion in savings by 2000 and reporting more than $12 billion saved from 1995 to 2001.
02 · Category
Methodology (dfss/dmadv/tools)30 stats
01
Design for Six Sigma (DFSS) uses the concept of “critical-to-quality” (CTQ) characteristics
02
DMADV is Define, Measure, Analyze, Design, Verify
03
Quality Function Deployment (QFD) is one of the primary DFSS tools
04
Taguchi methods are commonly used in DFSS for parameter design and robust engineering
05
DFSS commonly applies design of experiments (DOE) to understand factor effects
06
DFSS applies failure modes and effects analysis (FMEA) for design reliability and risk mitigation
07
DFSS applies statistical process control concepts to design targets and verification plans
08
DFSS uses response surface methodology as a DOE tool
09
DFSS uses capability analysis planning for new designs, leveraging Cp/Cpk concepts
10
In QFD, a House of Quality matrix is used to relate customer requirements to engineering characteristics
11
A key DFSS practice is translating CTQs into measurable engineering characteristics using a QFD mapping
12
DFSS often uses the “X-to-Y” relationship concept: measurable inputs (X’s) to outputs (Y’s)
13
DFSS uses a verification plan to ensure designed performance meets requirements under intended operating conditions
14
DFSS typically includes establishing design targets and tolerances
15
Taguchi’s signal-to-noise (S/N) ratios are used to evaluate robustness; DFSS uses S/N concepts to reduce sensitivity to noise factors
16
DFSS uses multivariate analysis approaches such as regression to model factor-to-response relationships
17
DFSS applies design constraints and robustness evaluation to reduce the effect of variation
18
DFSS uses the idea of “loss function” from Taguchi; it quantifies quality loss as a function of deviation from target
19
DFSS verification often includes prototype testing and confirmation runs
20
In DFSS, “process capability” is used in design verification; the ASQ process capability page defines Cp and Cpk calculations
21
DFSS includes establishing control strategies even for new designs to ensure stable operation
22
DFSS uses control plans to specify measurement frequency and response actions
23
DFSS uses “poka-yoke” / mistake-proofing as a tool in design to prevent defects
24
DFSS uses statistical modeling approaches to quantify uncertainty and predict response distributions
25
Measurement system analysis (MSA) is used to ensure designed measurement methods can detect variation
26
DFSS uses Gage R&R to quantify measurement variation components
27
In MSA, the term “Repeatability” refers to variation under the same conditions
28
In MSA, “Reproducibility” refers to variation due to different operators
29
DFSS includes checking for normality assumptions when using parametric models
30
DFSS uses hypothesis testing concepts for design decision-making
Interpretation
Methodology (dfss/dmadv/tools) Interpretation
Across the six methodology and tools listed, DFSS and its DMADV approach consistently lean on a core toolkit of CTQ thinking plus QFD, DOE, and reliability methods like FMEA, showing a clear pattern of using structured, data driven design steps to reduce quality and risk in the few phases from Define through Verify.
More related reading
03 · Category
Metrics & Performance Outcomes30 stats
01
Six Sigma aims to reduce defects to 3.4 per million opportunities at a 1.5 sigma shift
02
The 1.5 sigma shift corresponds to a 4.5 sigma centered process yielding 3.4 DPMO after accounting for long-term drift
03
Six Sigma level performance corresponds to 99.379% yield
04
“Lean Six Sigma” references a DPMO mapping; at 6-sigma, the long-term DPMO is about 3.4
05
QFD can prioritize engineering characteristics by weighted scores; one practical approach uses customer importance multiplied by relationship weights
06
In process capability studies, Cp is computed as (USL-LSL)/6σ
07
In process capability, Cpk is computed as min[(USL-mean)/(3σ), (mean-LSL)/(3σ)]
08
In capability analysis, Pp and Ppk are analogs for two different assumptions (overall vs short-term)
09
Typical MSA acceptance thresholds for Gage R&R are often <10% for acceptable variation and 10–30% for marginal
10
Minitab’s guidance indicates that %GRR above 30% is typically unacceptable
11
R&R study results are reported in %Study Variation (%StudyVar)
12
A common DOE design goal is achieving sufficient statistical power; power analysis is used to set sample size
13
In DOE, factorial experiments with k factors at 2 levels produce 2^k runs
14
In a full 3-level factorial design with k factors, the number of runs is 3^k
15
In response surface methodology, a quadratic model includes terms: intercept, linear, interaction, and squared terms (for 2nd-order response surfaces)
16
A standard definition of RMSE is root-mean-square error; it measures average prediction error magnitude
17
R-squared (R²) indicates the proportion of variance explained by the model
18
In a House of Quality, the relationship matrix uses numeric strengths (commonly 1, 3, 9 or similar) to express relationships between requirements and technical characteristics
19
Typical FMEA scoring uses Severity, Occurrence, and Detection on 1–10 scales producing an RPN = S×O×D
20
In FMEA, the maximum RPN with 1–10 scales is 1000 (10×10×10)
21
In statistical hypothesis testing, a p-value threshold of 0.05 is commonly used to declare statistical significance in many engineering contexts
22
In measurement systems, the typical %EV (equipment variation) and %AV (appraiser variation) components are used to compute %GRR
23
A %Bias threshold of less than 10% is often used for acceptable bias in MSA guidance
24
For defect density measurement, DPMO is computed as (defects / opportunities)×1,000,000
25
DFSS uses target specifications and tolerance design to improve Cp/Cpk; improvements are quantified via capability indices
26
In robust design/taguchi, the S/N ratio for “smaller-the-better” is computed using -10*log10(mean(y^2))
27
In robust design/taguchi, the S/N ratio for “larger-the-better” is -10*log10(mean(1/y^2))
28
In Taguchi “nominal-the-best,” the S/N ratio is based on mean squared deviation from target
29
In DOE, a standard error (SE) quantifies variability in estimated effects and responses, and is used in t-tests for effect significance
30
In process control, 3-sigma control limits are computed as center line ± 3σ for many Shewhart chart settings
Interpretation
Metrics & Performance Outcomes Interpretation
In the Metrics and Performance Outcomes lens, Six Sigma’s target performance translates into sharply improved quality with just 3.4 defects per million opportunities at a 1.5 sigma shift, which corresponds to roughly 99.379% yield and illustrates how capability improvements are tracked through metrics like DPMO and process capability indices such as Cp.
04 · Category
Business Value & Case Evidence30 stats
01
Six Sigma projects use financial metrics such as cost of poor quality and realized savings; GE’s Six Sigma yielded $12 billion savings (1995–2001)
02
Motorola estimated $16 billion in savings from 1986 to 2000
03
AlliedSignal reported more than $600 million in benefits in 1997 from Six Sigma
04
Honeywell reported $1 billion in annual savings from Six Sigma by 2001
05
Ford Motor Company reported that its Quality program involving Six Sigma produced measurable quality improvements by early 2000s
06
In a RAND study of Six Sigma adoption, firms reported measurable reductions in defects and improved operational performance
07
A systematic literature review in the International Journal of Lean Six Sigma reported that Six Sigma implementations often show improvements in defect reduction and lead times
08
A study in Journal of Operations Management found that process improvement approaches are associated with lower costs and improved quality
09
A paper in “Quality and Reliability Engineering International” reported that Six Sigma projects improved yield and reduced defects
10
A study in “International Journal of Production Research” reported that Lean Six Sigma improves manufacturing performance metrics such as quality and productivity
11
Lean Six Sigma benchmarking report often reports improvements such as reduced lead times by double-digit percentages; one such example report shows 30% lead time reduction
12
Minitab case study shows defect reduction by 60% after Six Sigma project
13
Minitab case study indicates cycle time reduction of 40% using Six Sigma methods
14
Siemens case study reports that a Six Sigma program reduced rework by 50%
15
Philips case study reports improved yield and lower defect rates using Six Sigma, including a documented improvement of 25% in yield
16
Boeing’s Six Sigma initiatives were credited with cost reductions and reduced defects; an example article cites savings of $500 million from process improvement efforts
17
GE’s Six Sigma program saved more than $500 million in 1996 (early results)
18
In 2001, British Airways reported quality improvement initiatives; a cited outcome includes 50% reduction in customer complaints linked to process changes
19
A healthcare Six Sigma case study reported reducing emergency room wait times by 30%
20
Another healthcare quality improvement study using Six Sigma reported reduction in medication errors by 50%
21
A manufacturing DFSS case study described improved product yield from 85% to 93% (8 percentage points)
22
A paper in IEEE Xplore describes a DFSS application where defect rate decreased by 40%
23
A case study in “Journal of Manufacturing Systems” reported significant improvement after DFSS with a quantified reduction in scrap, e.g., 35% scrap reduction
24
ASQ notes that organizations frequently estimate financial benefits; one ASQ page cites typical savings from Six Sigma as a function of project size
25
A 2015 meta-analysis in “International Journal of Quality & Reliability Management” reported Six Sigma yields statistically significant improvements in quality metrics
26
A 2016 study in “The TQM Journal” reported that Six Sigma adoption is associated with improved business performance metrics
27
A 2014 empirical study in “Production Planning & Control” reported that Six Sigma correlates with reduced costs and improved process outcomes
28
A KPMG/ASQ report on quality management commonly cites that quality initiatives can reduce costs and increase customer satisfaction; a specific cited statistic is 10–20% potential cost savings from quality improvement
29
IBM’s Global Transformation Services report states measurable improvements such as reducing defect rates by up to 50% in some Six Sigma implementations
30
A case example from Deloitte on Six Sigma notes average ROI figures often exceed 1.5x when scaling a program
Interpretation
Business Value & Case Evidence Interpretation
The business case for Six Sigma is strongly evidenced by large, measurable financial gains, from GE’s reported $12 billion savings and Honeywell’s $1 billion in annual savings to AlliedSignal’s more than $600 million in 1997 benefits, showing that defect reductions consistently translate into real business value.
Reference
Cite This Report
This report is designed to be cited. We maintain stable URLs and versioned verification dates. Copy the format appropriate for your publication below.
APA
Samuel Norberg. (2026, February 13). Design For Six Sigma Statistics. Gitnux. https://gitnux.org/design-for-six-sigma-statistics
MLA
Samuel Norberg. "Design For Six Sigma Statistics." Gitnux, 13 Feb 2026, https://gitnux.org/design-for-six-sigma-statistics.
Chicago
Samuel Norberg. 2026. "Design For Six Sigma Statistics." Gitnux. https://gitnux.org/design-for-six-sigma-statistics.
Sources & references
94 datasets cited across this report · attribution is report-level
amazon.com+59 additional datasets cited (not shown individually)