Study guide
16.2 Six Sigma DMAIC for Auditors
ASQ Certified Quality Auditor CQA
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
0.1 Current Exam Facts 0.2 Eligibility, Fees & Recertification 0.3 Case Studies & Study Strategy
2 Chapter 1: Types of Quality Audits
1.1 Product, Process, System, Hybrid & Remote Audits 1.2 First-, Second- & Third-Party Context 1.3 CAPA Verification, Risk-Based, Surveillance & For-Cause 1.4 Common Elements with Sustainability, EHS & Financial Audits
3 Chapter 2: Purpose, Scope & Audit Criteria
2.1 Elements of Purpose and Scope 2.2 Benefits of Audits (Effectiveness, Risk, Cyber) 2.3 Criteria: Standards, Contracts, Specs & QMS
4 Chapter 3: Roles, Ethics & Audit Credibility
3.1 Roles: Lead Auditor, Team, Client, Auditee, Observer 3.2 ASQ Code of Ethics, Due Care & Confidentiality 3.3 Legal Consequences of Improper Auditor Actions 3.4 Independence, Objectivity & Qualifications
5 Chapter 4: Audit Planning Fundamentals
4.1 Elements of the Audit Planning Process 4.2 Auditor Selection Criteria 4.3 Pre-Audit Documentation & Gap Assessments 4.4 Logistics: Safety, Escorts, Access & PPE
6 Chapter 5: Auditing Tools, Strategies & the Audit Plan
5.1 Sampling Plans, Checklists & Working Papers 5.2 Forward/Backward Tracing, Discovery & Observation 5.3 Creating and Distributing the Audit Plan
7 Chapter 6: Audit Performance Management
6.1 On-Site Management for the Auditor 6.2 On-Site Management for the Auditee 6.3 Opening Meeting
8 Chapter 7: Evidence Collection & Closing Meetings
7.1 Audit Data Collection and Analysis 7.2 Characteristics of Objective Evidence 7.3 Organizing Evidence by Risk and Significance 7.4 Exit and Closing Meetings
9 Chapter 8: Audit Reporting
8.1 Report Development and Content 8.2 Effective Reports: Summary, Findings & OFIs 8.3 Approvals, Distribution & Audit File Retention
10 Chapter 9: CAPA Follow-Up & Audit Closure
9.1 CAPA Process Elements & Root Cause 9.2 Reviewing and Negotiating CAPA Plans 9.3 Verifying CAPA Effectiveness 9.4 Ineffective CAPA Escalation & Audit Closure
11 Chapter 10: Auditor Characteristics, Resources & Conflict
10.1 Auditor and Lead Auditor Characteristics 10.2 On-Site Audit Resource Management 10.3 Conflict Resolution Techniques
12 Chapter 11: Communication, Interviewing & Team Dynamics
11.1 Communication and Presentation Techniques 11.2 Interviewing Techniques 11.3 Team Building, Facilitation & Development Stages
13 Chapter 12: Audit Program Management Core
12.1 Senior Management Support for the Audit Function 12.2 Staffing and Resource Management 12.3 Auditor Training and Development 12.4 Audit Program Evaluation Metrics
14 Chapter 13: Internal & External Audit Programs
13.1 Internal Audit Program Management 13.2 External / Supplier Audit Program Management 13.3 Standardizing Best Practices from Audit Results
15 Chapter 14: Risk, Management Review & Electronic Systems
14.1 Organizational Risk Management & Continuity 14.2 Management Review Input from the Audit Program 14.3 Electronic Records, Data Integrity & Cybersecurity
16 Chapter 15: Business & Financial Impact of Auditing
15.1 Auditing as a Management Tool 15.2 Interrelationships of Business Processes 15.3 Cost of Quality Principles
17 Chapter 16: Quality Tools & Process Improvement
16.1 Seven Basic Tools, Root Cause & PDCA 16.2 Six Sigma DMAIC for Auditors 16.3 Lean Principles and Tools
18 Chapter 17: Statistics & Process Variation
17.1 Mean, Median & Mode 17.2 Dispersion & Qualitative vs Quantitative Analysis 17.3 Common Cause vs Special Cause Variation 17.4 Process Capability Metrics & Outliers
19 Chapter 18: Sampling, Change Control, V&V & Risk Tools
18.1 Acceptance Sampling & Sampling Types (incl. MSA) 18.2 Consumer Risk, Producer Risk & Confidence 18.3 Change Control, Configuration Management, V&V 18.4 FMEA, HACCP, CTQ & SWOT
16.2 Six Sigma DMAIC for Auditors
Key Takeaways Explain This Topic AI
DMAIC is Define–Measure–Analyze–Improve–Control; CQA BoK V.B.1 is Apply-level literacy for auditors, not a requirement to run Black Belt projects.
Define sets measurable problem/goal, scope, SIPOC/VOC-CTQ, and ownership; Measure requires operational definitions, baseline metrics, and often MSA before analysis is trusted.
Analyze validates vital few causes with data and process insight; Improve implements cause-linked solutions (prefer pilots and error-proofing over detection-only fixes).
Control sustains gains via control plans, monitoring/SPC, standard work, training, response plans, and process-owner transfer—where many projects fail.
Auditors apply DMAIC by mapping CAPA and improvement evidence to phases, spotting skipped steps, and challenging “Six Sigma success” without Measure or Control proof.
Last updated: August 2026
16.2 Six Sigma DMAIC for Auditors (CQA BoK V.B.1 — Apply)
Quick Answer: DMAIC is Define–Measure–Analyze–Improve–Control. At Apply level, CQA candidates must recognize each phase’s purpose, typical deliverables, and how auditors encounter or use DMAIC evidence —not run belt projects themselves. Link DMAIC rigor to audit findings, CAPA quality, and management claims of “data-driven improvement.” Domain V ≈ 10% of scored items. Practice at /practice/cqa .
Six Sigma is a structured methodology for reducing process variation and defects, historically targeting extremely low defect rates when fully deployed. For quality auditors, the practical skill is DMAIC literacy : knowing what good project evidence looks like in each phase, where shortcuts appear, and how DMAIC artifacts support objective evidence of problem solving and control.
You will see DMAIC in:
- CAPA and major nonconformity investigations
- Customer complaint reduction and cost-of-quality projects
- Supplier development and process qualification stories
- Management review inputs claiming “Six Sigma results”
- Case-study exam items with phase-labeled exhibits
- DMAIC at a glance
Phase Core question Typical outputs auditors may sample
Define What problem, for whom, how big, who owns it? Project charter, problem/goal statements, SIPOC, VOC/CTQ, scope/in-out, stakeholders, timeline
Measure How do we quantify the problem reliably? Operational definitions, data collection plan, baseline sigma/defect metrics, MSA/gage study, process map as-is
Analyze What causes drive the problem? Root cause hypotheses, data analysis, process analysis, validated vital few causes
Improve What changes remove causes and work in practice? Solution selection, FMEA/risk of change, pilot results, implementation plan
Control How do we hold the gains? Control plan, SPC, standard work/docs, training, response plans, transfer to process owner
Related structure: DMADV / DFSS (Define–Measure–Analyze–Design–Verify) for designing new processes/products. Auditors should not confuse improve existing process (DMAIC) with design something new (DMADV) .
Define — set the problem correctly
Define prevents solving the wrong problem. Strong Define work is specific, customer-linked, scoped, and measurable .
Elements to recognize:
Problem statement: what is wrong, where, when, magnitude (not a disguised solution).
Goal statement: targeted improvement with metric and date (e.g., reduce late shipments from 8% to <2% by Q3).
Business case: why it matters (cost, risk, customer, compliance).
Scope: in/out boundaries; process start/stop.
SIPOC: Suppliers, Inputs, Process, Outputs, Customers—high-level context.
VOC → CTQ: Voice of Customer translated to Critical to Quality measures.
Team and sponsor: authority to change the process.
Audit / exam application:
Charter that already names the solution (“buy new software”) without baseline data → Define failure.
Goal of “improve quality” with no metric → not auditable.
Scope so wide it cannot finish → project theater risk.
When evaluating CAPA, weak problem definition is the same disease in different clothing.
Scenario — Define in a complaint project. Customers report “damaged packaging.” Define phase discovers three different codes mixed: transit damage, warehouse crush, and shipping wrong dunnage. Splitting the Y metric avoids a single vague project. An auditor reviewing the program asks whether complaint taxonomy supports meaningful Define work.
Measure — make the Y trustworthy
Measure establishes a credible baseline . Without measurement system integrity, Analyze and Improve are fiction.
Core practices:
- Practice Why auditors care
- Operational definition Same defect means the same thing across shifts and sites
- Data collection plan Who, what, when, how many, sampling method, forms/systems
- Baseline performance DPMO, % defective, yield, cycle time, Cpk—chosen to match the Y
- MSA / gage R&R Measurement variation not confused with process variation
- As-is process map Actual flow for later analysis
Sigma level literacy (conceptual): Higher sigma implies fewer defects relative to specifications/requirements, under stated assumptions. Exam items may reference defect metrics without requiring deep calculation. Focus on whether the metric matches the problem and whether data are reliable.
Scenario — Measure failure. A team claims 4.5σ performance using only weekly manager estimates of “good days.” No operational definition, no sampling plan, no MSA. Auditor treating this as objective evidence of capability would be wrong; the Measure phase is incomplete.
Link to audit fieldwork: Auditors apply Measure thinking when designing sampling plans, defining “nonconformity,” and ensuring checklists collect comparable data across team members.
Analyze — find validated causes
Analyze separates vital few root causes from noise using process analysis and data.
Common tools in Analyze (overlap with V.A and later statistics topics):
- Process maps, value-stream analysis, waste walks
- Pareto, histograms, box plots, scatter, multi-vari
- Cause-and-effect, 5 Whys, fault trees
- Hypothesis tests / regression (recognize purpose; deep calc is not the CQA focus)
- Stratification by machine, shift, supplier, material lot
Apply-level auditor stance:
Do stated causes explain the baseline problem and its stratification patterns?
Were causes tested against data (not only brainstormed)?
Is the team still open to disconfirming evidence?
Are human-error causes drilled to system design?
Scenario. Analyze shows defect spikes only on Line 2 after changeover, not Line 1. Root focus becomes changeover standard work and first-article verification—not plant-wide “quality awareness.” An auditor assessing CAPA would expect actions aligned with that stratification, not generic posters.
Improve — change the process deliberately
Improve selects and implements solutions that address validated causes, preferably with pilots before full rollout.
Hallmarks of solid Improve:
- Solution criteria linked to causes and CTQs (impact, cost, risk, speed)
- Error-proofing preferred over detection where feasible
- Risk analysis of the change (and update of FMEA/control plan as applicable)
- Pilot plan with success metrics and exit criteria
- Implementation: docs, training, equipment, IT, suppliers
- Resistance/change management considered
Auditor red flags:
- Jumping to Improve before Measure/Analyze (“we already knew”)
- Solutions that only add inspection without removing cause
- No pilot on high-risk changes
- “Training only” for systemic process design flaws
- Unauthorized process changes outside change control
Scenario — Improve with audit impact. A validated cause is wrong-component picks from look-alike bins. Improve implements poka-yoke (asymmetric connectors + barcode interlock) and revises pick face layout. Detection sampling decreases after proof of effectiveness. Audit trail: change control, validation of the interlock, updated WI, training records.
Control — sustain the gains
Control is where many projects die. Without Control, performance regresses and “Six Sigma success” is temporary.
Control phase elements:
- Element Audit evidence
- Control plan What is monitored, who reacts, limits/triggers, records
- SPC / dashboards Ongoing signals; reaction to special causes
- Standardization Controlled documents, standard work, visual standards
- Training & competence Affected roles trained; effectiveness considered
- Response / escalation plans What to do when metrics fail
- Owner transfer Process owner accepts monitoring; project team exits
- Audit / layered process audit Periodic verification that standards stick
Scenario — missing Control. A DMAIC project cut scrap 40% during the pilot quarter. Six months later scrap returned; temporary engineers left; temporary check sheet abandoned; no control plan in the QMS. Management still cites the project as success in reviews. An auditor applies DMAIC knowledge by sampling whether Control deliverables exist and whether metrics remain at goal—effectiveness, not trophy slides.
How auditors apply DMAIC without being Black Belts
Auditor activity DMAIC lens
Evaluating major CAPA Is there clear Y, baseline, cause validation, solution–cause link, sustain plan?
Management review Are improvement claims phase-complete or anecdote-only?
Supplier quality Do supplier “Six Sigma projects” show Measure/Control evidence?
Process audits Are control plans and SPC reactions actually followed?
Program improvement Can audit findings feed Define of improvement projects?
You do not need to: calculate complex DOE models, run Minitab, or hold a belt. You do need to: map evidence to phases, spot skipped phases, and judge whether conclusions are supported.
DMAIC vs PDCA vs CAPA (exam clarity)
- Framework Typical use Relation
- PDCA Universal improvement / learning cycle DMAIC is a rigorous project form of PDCA thinking
DMAIC Structured projects for complex, chronic, or high-impact problems Phases expand Plan/Do/Check/Act with tollgates
CAPA Formal response to nonconformity / potential nonconformity Good CAPA often mirrors Define→Control logic at smaller scale
Exam trap: treating DMAIC as mandatory for every tiny correction. Apply proportionality: depth scales with risk and complexity. Another trap: equating a belt certificate on the wall with effective Control in the process.
Tollgates and governance (what “Apply” looks like)
Mature deployments use tollgates between phases: sponsor reviews charter (Define), data quality (Measure), cause validation (Analyze), pilot results (Improve), and control plan ownership (Control). Auditors may sample tollgate records as evidence that improvement is managed—not ad hoc.
Scenario — governance audit. Quality manual claims a Six Sigma program. Sampling 5 closed projects finds 4 without control plans and 3 without MSA on critical gages. Finding is not “belts are bad”; it is that the stated methodology is not implemented as claimed—system nonconformity against the organization’s own requirements.
Integration with audit case studies
Case-study packets may include a partial charter, a Pareto, a fishbone, and a control chart. Work the packet like a mini-DMAIC review:
Is the problem in Define measurable and scoped?
Do Measure exhibits match the Y in the charter?
Does Analyze connect data patterns to stated root causes?
Do Improve actions attack those causes?
Does Control show how gains are held and who owns them?
That sequence is pure BoK V.B.1 Apply skill—and it transfers directly to field audits of improvement systems.
Practical auditor questions by phase
Define: What CTQ or requirement is harmed? What is in scope? Who sponsors?
Measure: How is the metric defined? Is the baseline current? Is the measurement system adequate?
Analyze: What evidence validates the vital few causes? What was ruled out?
Improve: Why this solution? What was piloted? What risks were assessed?
Control: What will detect regression? What is the reaction plan? Where is it documented?
Memorize the five phase names in order , the question each answers, and at least two artifacts per phase. That package answers most CQA DMAIC items without belt-level statistics.