Study guide
DFSS Road Maps: DMADV & IDOV
ASQ Certified Six Sigma Green Belt CSSGB
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
CSSGB Exam Facts & Logistics How to Study for an Open-Book ASQ Exam
2 Six Sigma Foundations
Value of Six Sigma & Quality Leaders Organizational Goals & Six Sigma Projects Organizational Drivers, KPIs & Scorecards
3 Lean Principles in the Organization
Lean Concepts Value Stream Mapping & Waste
4 Design for Six Sigma
DFSS Road Maps: DMADV & IDOV FMEA Basics & Risk Priority Number Design FMEA vs Process FMEA
5 Define: Project Identification
Project Selection & DMAIC Fit Process Elements & Boundaries Benchmarking Types SIPOC & Process Inputs/Outputs
6 Stakeholders & Voice of the Customer
Owners & Stakeholders Customer Identification Customer Data Collection CTQ, QFD & Kano
7 Project Management Core
Agile & Top-Down Project Methods Project Charter & Problem Statements Project Scope Tools Primary & Consequential Metrics
8 Planning, Risk & Closure
WBS, Gantt, CPM, PERT & Tollgates Project Documentation Project Risk Analysis & Management Project Closure & Lessons Learned
9 Management Tools & Business Results
Eight Management & Planning Tools DPU, RTY, CoPQ, DPMO & Sigma Level Organizational Communication
10 Team Dynamics & Performance
Team Stages & Negative Dynamics Six Sigma Roles & RACI Brainstorming, NGT & Multivoting Team Communication
11 Measure: Process & Probability
Process Maps & Documentation Basic Probability Concepts Central Limit Theorem
12 Distributions & Data Collection
Statistical Distributions Data Types & Measurement Scales Sampling & Data Collection Plans Descriptive Statistics
13 Graphical Methods & MSA
Graphical Methods Measurement System Analysis & Gage R&R Bias, Linearity, Stability & P/T
14 Process & Performance Capability
Process Performance vs Specifications Process Capability Studies Cp, Cpk, Pp, Ppk & Cpm Short-Term vs Long-Term Capability & Sigma Shift
15 Analyze: Exploratory Data Analysis
Multi-Vari Studies Correlation & Linear Regression
16 Hypothesis Testing
Hypothesis Testing Basics Tests for Means, Variances & Proportions
17 Gap & Root Cause Analysis
Gap Analysis Root Cause Analysis Tools
18 Design of Experiments
DoE Basic Terms Main Effects & Interaction Plots
19 Implementation Planning & Lean Tools
Implementation Planning & Pilots Waste Elimination Tools Cycle-Time Reduction & SMED Kaizen & Kaizen Blitz
20 Statistical Process Control
SPC Basics: Common vs Special Cause Rational Subgrouping Control Chart Selection & Construction
21 Sustaining Improvements & Lean Control
Control Plans Document Control, Training & Audits Plan-Do-Check-Act (PDCA) TPM & Visual Factory
DFSS Road Maps: DMADV & IDOV
Key Takeaways Explain This Topic AI
Design for Six Sigma (DFSS) builds quality into new products, services, or processes instead of fixing defects after launch.
DMADV is Define, Measure, Analyze, Design, Verify; IDOV is Identify, Design, Optimize, Verify—both are design roadmaps, not DMAIC.
Use DMAIC when an existing process has measurable defects; use DFSS when no stable process exists or redesign must replace patching.
Verification checks that the design meets specified requirements; validation confirms the result satisfies real customer use and business goals.
Green Belts often support DFSS projects led by Black Belts or design teams, translating VOC and CTQs into measurable design inputs.
Last updated: July 2026
DFSS Road Maps: DMADV & IDOV (CSSGB BoK I.C.1 — Understand)
Quick Answer: Design for Six Sigma (DFSS) designs quality into new products, services, or processes from the start. Two common roadmaps are DMADV (Define, Measure, Analyze, Design, Verify) and IDOV (Identify, Design, Optimize, Verify). Use DFSS when you are creating something new or when incremental DMAIC improvement cannot close the performance gap; use DMAIC to improve an existing process that already has data and a defined flow.
Design for Six Sigma (DFSS) is the Six Sigma approach for creating products, services, and processes so they meet critical-to-quality (CTQ) requirements with low defect rates from day one. DMAIC is powerful for fixing what already runs. DFSS answers a different question: How do we design it right so we do not inherit chronic defects later?
On the CSSGB exam, I.C.1 is at the Understand level. You should recognize DFSS roadmaps, contrast them with DMAIC, and know when a project belongs in design versus improvement.
Why DFSS Exists
Many quality problems are designed in . Wrong tolerances, untestable features, handoffs that create rework, and processes that cannot hold capability all show up after launch as scrap, warranty, long cycle times, or customer complaints. Fixing those with endless DMAIC projects is expensive. DFSS invests earlier—in requirements, concept selection, robustness, and verification—so variation and failure modes are reduced before scale-up.
Typical DFSS goals include:
Translate Voice of the Customer (VOC) into measurable design requirements and CTQs.
Predict and prevent failure modes rather than detect them late in production or service.
Build robustness so performance stays stable despite noise (environment, user variation, supplier variation).
Prove capability before full release through prototypes, pilot runs, and verification evidence.
DMADV: Define → Measure → Analyze → Design → Verify
DMADV is the best-known DFSS roadmap. It parallels DMAIC in structure but ends in design and verification, not improve-and-control of an existing baseline.
- Phase Focus Typical outputs
- Define Business case, customers, scope, goals Project charter, VOC plan, high-level requirements
Measure Quantify needs and current market/process baselines CTQ list, measurement methods, competitive or baseline data
Analyze Concepts, CTQ drivers, risk, capability targets Concept selection, transfer functions, risk assessment, target specs
- Design Detailed product/process design Drawings, process maps, control strategies, FMEA, prototypes
- Verify Prove the design meets goals Pilot results, capability studies, verification tests, launch readiness
Define frames the opportunity: who the customer is, what problem the design solves, and what success looks like financially and operationally. Measure turns soft VOC into hard metrics—response time, strength, accuracy, cost per unit—and establishes how those metrics will be measured. Analyze compares design concepts, links design parameters (X’s) to CTQs (Y’s), and sets targets and tolerances. Design builds the detailed solution, often iterating with simulation, Design of Experiments (DOE), and FMEA. Verify demonstrates that the built design meets the defined requirements under realistic conditions.
Memory cue: DMADV designs and verifies ; DMAIC improves and controls .
IDOV: Identify → Design → Optimize → Verify
IDOV is another widely taught DFSS roadmap. Organizations may prefer IDOV wording, but the intent is the same: start from customer needs, design, optimize, and prove the result.
- Phase Focus
- Identify Customers, CTQs, requirements, business targets, concept framing
- Design Functional architecture, detailed design, risk analysis, initial prototypes
- Optimize Robustness, DOE, tolerance design, cost/performance trade-offs
- Verify Confirmation that CTQs and business goals are met before full launch
Compared with DMADV, Identify compresses much of Define/Measure into one front-end phase. Optimize makes the robustness and parameter-setting work explicit as its own phase rather than folding it only into Design/Analyze. On the exam, do not treat IDOV and DMADV as enemies—recognize both as DFSS roadmaps used to create or redesign offerings, not as DMAIC variants for routine process fixing.
DFSS vs DMAIC: Choosing the Right Path
- Question Prefer DMAIC Prefer DFSS
- Does a stable process already exist? Yes—map, measure, improve it No—or it is only a weak prototype
- Can incremental change hit the goal? Yes No—targets require a new design
- Primary work product Improved process + control plan New product/service/process design
- Typical end state Controlled existing process Verified design ready for launch
Use DMAIC when the process runs today, defects or delays are measurable, and root-cause improvement can close the gap. Use DFSS when you are launching a new product line, designing a new service channel, or when the current process is so fundamentally wrong that redesign is cheaper than perpetual firefighting.
Green Belts most often lead DMAIC projects. In DFSS, Green Belts frequently support Black Belts, design engineers, or cross-functional teams by collecting VOC, measuring CTQs, running basic analyses, documenting FMEA inputs, and supporting pilot verification. Understanding DFSS still matters: exam questions test whether you pick the right methodology for a scenario.
Verification vs Validation
DFSS ends with evidence. Two related terms appear in design and quality work:
Verification asks: Did we build the design to the specified requirements? It checks conformance to stated specs, drawings, process capability targets, and test criteria—often through inspections, tests, simulations, and pilot capability studies.
Validation asks: Does the design actually meet the real customer need and intended use? It confirms fitness for purpose in the real environment—user trials, field pilots, clinical or regulatory validation where required, and confirmation against business goals (cost, cycle time, market requirements).
A product can pass verification (meets the written spec) and still fail validation (customers hate it, or the use case was wrong). Conversely, validation without verification risks an unrepeatable “happy pilot.” Strong DFSS programs do both: verify against CTQ specs and validate against customer and business goals before full-scale launch.
Green Belt Takeaway
For CSSGB, master the labels and the decision rule. DMAIC improves existing processes. DFSS (DMADV or IDOV) designs new or radically redesigned processes and products. Verification proves the design matches requirements; validation proves it satisfies real goals. If a question describes a brand-new offering or a clean-sheet process, think DFSS. If it describes scrap, cycle time, or defects in a running process, think DMAIC.