Study guide

CTQ, QFD & Kano

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

CTQ, QFD & Kano

Key Takeaways Explain This Topic AI

Critical to Quality (CTQ) and broader Critical to X (cost, safety, delivery, etc.) convert vague VOC into measurable requirements tied to process Y’s.

A CTQ tree decomposes customer need → drivers → measurable CTQ specifications the process can control.

QFD (House of Quality) links customer requirements to technical features/measures and supports prioritization and tradeoffs.

The Kano model classifies needs as basic (must-be), performance (more-is-better), or delighters—and shows how satisfaction responds to fulfillment.

Weighting methods (pairwise comparison, frequency×severity, analytic scoring) prioritize which CTQs the Green Belt project should attack first.

Last updated: July 2026

CTQ, QFD & Kano (CSSGB BoK II.B.3 — Apply)

Quick Answer: Turn Voice of the Customer into measurable requirements using CTQ trees , Critical to X thinking, QFD (House of Quality) , and the Kano model . Weight and prioritize CTQs so the project Y and Improve actions focus on what matters most—not every comment equally.

Hearing customers (II.B.2) is not enough. Green Belts must translate “faster,” “safer,” and “easier” into specs a process can hit and a control plan can monitor. BoK II.B.3 is Apply .

From VOC to Requirements

  • Stage Output Example
  • VOC statement Customer language “I need my loan decision quickly.”
  • Need / requirement Clarified need Fast credit decision with clear status

CTQ Measurable Y Decision time ≤ 4 business hours for complete files; status visible within 15 minutes of submission

Process metric What you chart Median decision time; % decisions ≤ 4 hours

Critical to Quality (CTQ) characteristics are the measurable product or process features that determine whether the customer’s quality need is met. Broader Critical to X (CTX) language includes:

  • CTX Focus
  • CTQ Quality, defects, performance to spec
  • CTC Cost (often Critical to Cost)
  • CTS Safety
  • CTD Delivery / schedule
  • CTP Process parameters critical to the output

Exam stems may say Critical to Quality even when the measurable is delivery time; recognize the pattern : customer need → measurable characteristic → specification or target.

CTQ Tree — Structure and Worked Example

A CTQ tree (need hierarchy) breaks a broad need into drivers and then into measurable CTQs .

Levels (typical):

  • Need (customer voice, still broad)
  • Drivers (dimensions of the need)
  • CTQ requirements (measurable, with units and targets when known)
  • Worked example — online pharmacy delivery
  • VOC: “I want my prescriptions delivered reliably.” Need: Reliable prescription delivery
  • ├── Driver: On-time arrival
  • │ ├── CTQ: % of orders delivered by promised window ≥ 98%
  • │ └── CTQ: Promise-date accuracy (promised date − actual) median ≤ 0 days late
  • ├── Driver: Order correctness
  • │ ├── CTQ: Wrong-item rate ≤ 500 DPPM
  • │ └── CTQ: Missing-cold-pack rate for refrigerated SKUs = 0
  • └── Driver: Communication
  • ├── CTQ: Tracking update latency ≤ 30 minutes after scan events
  • └── CTQ: Proactive delay notice sent before promise window ends (yes/no ≥ 95% of delay events)

How to use it on a project:

Pick one or few primary CTQs as project Y(s) for the charter (e.g., on-time % and wrong-item rate).

Ensure each CTQ has an operational definition and data source (Measure phase).

Do not leave the tree as slogans—“reliable” without numbers is not yet a CTQ.

Specification tips: Prefer customer-relevant units; separate target from specification limits when both exist; note if the official limit is unknown and must be baselined.

QFD — Quality Function Deployment

Quality Function Deployment (QFD) is a structured method to deploy customer requirements into design and process characteristics. The classic first matrix is the House of Quality :

  • House room Contents
  • Left wall Customer requirements (WHATs), often weighted
  • Ceiling Technical / process characteristics (HOWs)
  • Center Relationship matrix (strong/medium/weak links)
  • Roof Correlations among technical characteristics (tradeoffs)
  • Right side Competitive or importance ratings
  • Foundation Targets for technical measures

Green Belt application (practical, not full DFSS craft):

List prioritized customer CTQs (from trees + weighting).

List candidate process/product features or measures.

Mark which features drive which CTQs.

Spot conflicts on the roof (e.g., thicker packaging improves damage CTQ but hurts cost and sustainability CTC).

Set technical targets that flow into Improve and Control.

QFD prevents “we improved a metric nobody asked for.” It is common in DFSS but appears in CSSGB Define when translating VOC to features/measures.

Kano Model

The Kano model classifies how fulfillment of a need maps to customer satisfaction :

Kano category If absent / poor If present / excellent Example

Basic / Must-be Strong dissatisfaction Little extra delight (expected) Brakes that work; correct medication; encrypted login

Performance / One-dimensional Dissatisfaction scales with gap Satisfaction scales with better performance Faster quote turnaround; longer battery life

Delighter / Attractive No penalty if absent (not expected) Disproportionate delight Unexpected proactive refund; brilliant packaging unboxing

  • Indifferent Little effect either way Do not over-invest
  • Reverse Some segments dislike the “feature” Segment carefully

Implications for Green Belts:

Fixing basics stops defections but may not raise NPS much—still mandatory.

Performance CTQs are classic DMAIC Y’s (time, defects, cost).

Delighters can differentiate but should not replace broken basics.

Over time, delighters decay into basics (what delighted in 2018 is expected in 2026).

Kano surveys ask paired questions (“How do you feel if this feature is present?” / “if absent?”) to classify needs; on the exam, focus on category behavior , not survey form design minutiae.

Weighting and Prioritization Methods

When VOC produces many CTQs, weight them:

  • Method How it works Use when
  • Frequency × severity How often mentioned × impact if failed Complaint and interview themes
  • Customer ranking / allocation Customers distribute 100 points across needs Direct stated priority
  • Pairwise comparison Compare needs two at a time; tally wins Small expert or customer panels
  • Analytic / AHP-style scoring Structured multi-criteria weights Complex tradeoffs with sponsor input
  • Strategy alignment Boost weights tied to OKRs / risk / regulation Basics and safety CTS

Worked mini-weighting: Three CTQs from interviews (n mentions) and severity 1–5:

  • CTQ Mentions Severity Score (f×s) Rank
  • On-time delivery 40 5 200 1
  • Correct items 25 5 125 2
  • Fancy tracking animations 15 2 30 3

Project charter Y → on-time and correctness; tracking polish is a later delighter, not the Green Belt’s primary Y.

Putting It Together — Translation Workflow

Identify customers (II.B.1).

Collect VOC with sound methods and clean questions (II.B.2).

Affinity-group statements into needs.

Build CTQ trees → measurable CTQs / CTX.

Classify with Kano (basic vs performance vs delighter).

Weight CTQs; align with sponsor strategy and regulations.

Optionally map through QFD to process features and targets.

Place primary CTQs into the charter metrics and Measure operational definitions.

  • Exam scenario cues
  • “Customer says ‘easy to use’ → tree to clicks, error rate, time-to-complete” → CTQ tree
  • “Matrix of customer wants vs design specs” → QFD / House of Quality
  • “No one notices when present, fury when missing” → Basic/must-be (Kano)
  • “Satisfaction rises linearly as speed improves” → Performance (Kano)
  • “Unexpected feature creates buzz” → Delighter (Kano)
  • “Which CTQ first?” → weighting + strategy , not the loudest single anecdote

Common trap: Treating every VOC quote as equal or jumping to a solution feature before a measurable CTQ exists. Another trap: optimizing a delighter while basics fail—Kano says customers still leave.

Master the translation chain— VOC → CTQ tree → prioritized measurable Y → QFD features → process control —and Define-phase requirement questions become systematic rather than essay-like guesswork.