Study guide
Customer Data Collection
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
Customer Data Collection
Key Takeaways Explain This Topic AI
Common VOC collection methods include surveys, focus groups, interviews, and direct observation (Gemba); each has strengths for breadth, depth, or real behavior.
Good questions are specific, unambiguous, and unbiased—avoid leading, double-barreled, loaded, or vague items that produce unusable data.
Match the method to the decision: interviews and observation for deep insight; surveys for quantified breadth; focus groups for interaction and language of the customer.
Eliminate measurement noise in VOC the same way you would in process data: clear operational definitions, consistent scripts, and trained collectors.
Reactive data (complaints, returns) and proactive data (structured VOC studies) both inform CTQs; do not rely on complaints alone.
Last updated: July 2026
Customer Data Collection (CSSGB BoK II.B.2 — Apply)
Quick Answer: Collect the Voice of the Customer with surveys , focus groups , interviews , and observation . Choose methods for the insight you need, then write questions that are specific, single-purpose, and neutral —free of vagueness, ambiguity, and bias—so VOC can become measurable CTQs.
Once you know who the customers are (II.B.1), you must hear them accurately . BoK II.B.2 is Apply : select methods and critique or improve question quality.
VOC Data: Reactive vs Proactive
Source type Examples Strength Risk if used alone
Reactive Complaints, returns, warranty, tickets, social rants Real pain, often severe Silent majority unheard; only failure voices
Proactive Planned surveys, interviews, focus groups, ethnography Broader and designed sample Poor questions still yield garbage
Operational proxies On-time %, defect escapes, call handle time Continuous, process-linked May not match what customers value
Best practice blends reactive signals (what is already broken) with proactive VOC (structured listening) and process data.
- Core Collection Methods
- Surveys
Surveys gather structured responses from many people via web, email, phone, or paper.
- Strengths: breadth, quantification, trend tracking, segmentation
- Weaknesses: low response bias, shallow “why,” poor design yields misleading scores
- Green Belt use: baseline satisfaction, prioritize themes, track post-improve scores
Use Likert scales , rankings, or closed choices for analysis; include a few open comments for language—not 40 open essays no one will code.
Focus groups
Focus groups are moderated small-group discussions (often 6–10 participants).
- Strengths: customer language, interaction that surfaces issues individuals forget, rapid theme generation
- Weaknesses: groupthink, dominant voices, not statistically representative
- Green Belt use: explore needs early; clarify survey wording; probe emotional drivers (Kano “delight” clues)
- Interviews
Interviews are one-on-one (or one-on-two) conversations, structured, semi-structured, or open.
- Strengths: depth, follow-up probes, confidential candor, B2B multi-role listening
- Weaknesses: time cost, interviewer bias, small samples
- Green Belt use: critical external accounts, internal customer handoff pain, CTQ drafting from stories
- Observation (including Gemba)
Observation watches real use of the product or process—customer sites, call listening, ride-alongs, time-and-motion at the receiver’s workplace.
- Strengths: reveals what people do , not only what they say ; catches workarounds
- Weaknesses: Hawthorne effect if intrusive; needs skilled observers; may miss latent needs
- Green Belt use: validate survey claims (“easy to use” vs 12 clicks observed); map internal customer struggle
- Method Best for Weak for
- Survey Quantifying themes across many customers Deep causal stories
- Focus group Language, ideas, reactions to concepts Precise population estimates
- Interview Depth, B2B, sensitive topics Cheap mass sampling
- Observation Actual behavior and environment Stated preferences and attitudes alone
Triangulation: when survey scores, interview stories, and observation agree, confidence in CTQs rises.
Writing Questions: Kill Vagueness, Ambiguity, and Bias
Garbage in, garbage out applies to VOC as much as to gage R&R. Train yourself to spot bad items.
Vagueness
Vague questions invite inconsistent interpretation.
Weak Stronger
“Are you satisfied with service?” “How satisfied are you with the time from ticket open to first human response on your last support contact?”
“Is quality good?” “In the last 90 days, how many delivered orders had a wrong item or quantity?”
Define who, what, when, and the scale . Operationally define terms like “on time” (by confirmed ship date? by customer dock date?).
Ambiguity and double-barreled items
Double-barreled questions ask two things at once:
Bad: “Was the product affordable and reliable?”
Fix: Split into separate affordability and reliability items.
Ambiguous pronouns and time windows also fail: “Did they fix it quickly?” — who is they , what is it , what is quickly ?
Bias: leading, loaded, and socially desirable items
Bias type Example Problem Fix
Leading “How excellent was our award-winning support?” Pushes positive answer Neutral wording: “Rate support on [scale]”
Loaded “Do you agree management wastes money on unnecessary inspections?” Emotional framing Neutral fact or balanced scale
- Assumptive “What did you enjoy most about our app?” Assumes enjoyment Filter: “Did you use the app? If yes…”
- Unbalanced scale Excellent / Good / Fair (no poor) Skews high Symmetric scales
- Jargon “Rate CTQ achievement of RTY” Customer does not share your acronyms Customer language
Also watch order bias (early questions prime later ones) and sampling bias (only happy email subscribers surveyed).
- Worked rewrite
- Original survey item: “Don’t you think our new portal is better and easier than before?”
Problems: leading (“Don’t you think”), double-barreled (better and easier), vague (“better”), biased toward yes.
Improved pair:
“Compared with the previous portal, completing a routine address change in the new portal is: Much harder / Somewhat harder / About the same / Somewhat easier / Much easier / Not applicable — I have not used both.”
- Optional open: “What, if anything, made the address-change task harder or easier?”
- Designing a Minimal VOC Collection Plan
Purpose: What decision will the data support (prioritize CTQs, validate charter Y, check improve)?
Customers: Segments from II.B.1 (internal vs external, primary vs secondary).
Methods: e.g., 12 internal handoff interviews + observation of 10 transactions + short external survey n≥100 if breadth needed.
Instruments: Scripted interview guide; survey with defined scales; observation checklist.
Sampling: Who is in/out; time period; how you avoid only angry or only loyal voices.
Bias control: Pilot the survey on 5 people; revise ambiguous items; train interviewers; record coding rules for open text.
Analysis path: Affinity themes → frequency/severity → candidates for CTQ trees (II.B.3).
Exam Application Patterns
Choose observation when stated satisfaction conflicts with field failures or when customers cannot articulate workarounds.
Choose interviews for few strategic B2B accounts or complex internal customers.
Choose surveys when you need comparable scores across segments.
Choose focus groups to explore language before a large survey.
Reject options that use leading or double-barreled questions as “good VOC design.”
Prefer specific, measurable phrasing that later becomes a CTQ measure.
Open-book tip: You rarely need to memorize survey software. You do need to diagnose bad questions and match method to purpose . That is the Apply skill ASQ is testing in II.B.2.
Collect VOC like a measurement system: clear definitions, controlled method, and minimal bias—so Define-phase requirements rest on evidence, not anecdotes from the loudest meeting.