4.1 Voice of the Customer (VOC) & Critical-to-Quality (CTQ)

Voice of the Customer (VOC) & Critical-to-Quality (CTQ)

Quick Answer: The Voice of the Customer (VOC) captures qualitative needs and expectations from both internal downstream recipients and external end users. Teams gather VOC through proactive methods (surveys, interviews, Gemba walks) and reactive channels (complaint logs, warranty claims). Using the Kano Model, requirements are classified into Must-Be (baseline threshold needs), One-Dimensional (linear performance satisfiers), and Attractive (delighter) attributes. The Critical-to-Quality (CTQ) Tree then translates broad, qualitative customer statements into specific, measurable operational parameters with defined targets and specification tolerances. Independent CSSYB study guide by OpenExamPrep.

Defining the Customer: Internal vs. External Customers

In Six Sigma, quality is defined exclusively by the customer. A process may run with high technical efficiency, but if its deliverables fail to satisfy the recipient, the process generates waste, rework, and operational risk. Quality professionals distinguish two customer groups:

1. Internal Customers: Individuals, functional units, downstream workstations, or administrative departments within the enterprise that receive the output of an upstream activity. For example, an assembly technician is the internal customer of the fabrication department machining components; an attending physician is the internal customer of the laboratory running blood panels; and accounts payable is the internal customer of purchasing. Satisfying internal customer requirements is critical: upstream defects, data errors, and delays cascade downstream, compounding operational friction and inflating internal failure costs.
2. External Customers: The individuals, client organizations, end users, and regulatory bodies that purchase, consume, or regulate the final product or service. Examples include retail buyers purchasing electronics, patients receiving hospital treatment, commercial clients using enterprise software, and government agencies (such as the FAA or FDA) enforcing mandatory standards. External customers provide the revenue sustaining the organization. Meeting their expectations drives market share, customer retention, and brand equity.

---

VOC Data Collection: Proactive vs. Reactive Methodologies

The Voice of the Customer (VOC) represents the collective needs, expectations, and pain points voiced by customers. Gathering robust VOC data is a vital early task in the Six Sigma Define phase, utilizing two complementary methodologies:

Proactive Data Collection

Proactive data collection involves structured inquiries initiated by the organization to solicit feedback before defects, dissatisfaction, or defection occur:

• Customer Surveys: Questionnaires administered digitally, by mail, or phone to collect quantitative ratings across standardized scales (e.g., Likert scales or Net Promoter Scores), enabling statistical analysis across large populations.
• Contextual Customer Interviews: Semi-structured, one-on-one dialogues that allow interviewers to probe deeply into customer perceptions, unstated needs, and operational friction.
• Focus Groups: Guided discussions with small, representative samples of targeted customers (typically 6 to 10 participants) led by a facilitator to explore reactions to products and prospective features.
• Direct Observation and Gemba Walks: Visiting the customer's actual environment ("the Gemba") to observe how users interact with products or services, uncovering unvoiced latent needs.
• Advantage: Proactive methods capture balanced feedback from both satisfied and dissatisfied customers, revealing emerging expectations before issues escalate.

Reactive Data Collection

Reactive data collection captures unsolicited customer feedback triggered after an operational failure, defect, or service breakdown has occurred:

• Customer Complaints and Dispute Logs: Escalations submitted through call centers, helpdesks, or online portals regarding substandard quality or delivery failures.
• Product Returns and Warranty Claims: Tangible records documenting physical failures, defective components, and repair expenses during warranty coverage.
• Service Helpdesk Tickets: Technical tracking logs detailing system downtime, software glitches, or transaction errors.
• Social Media and Public Reviews: Public feedback highlighting sentiment and operational frustrations.
• Advantages & Limitations: Reactive data provides an immediate, low-cost map of acute process failure modes and directly highlights Cost of Poor Quality (COPQ). However, reactive channels capture only the vocal minority; most dissatisfied customers defect silently to competitors without filing formal complaints.

---

The Kano Model: Classifying Customer Requirements

Developed in the 1980s by Dr. Noriaki Kano, the Kano Model provides a structured framework for understanding how different product and service attributes impact customer satisfaction. The model plots customer satisfaction (from extreme dissatisfaction to high delight) on the vertical axis against the degree of execution (from absent to fully executed) on the horizontal axis.

Kano classifies customer requirements into three primary categories:

1. Must-Be / Basic Quality (Dissatisfiers): Non-negotiable threshold attributes that customers expect as an absolute minimum baseline. They are frequently unstated because their presence is taken for granted.
   • Behavior: If missing or poorly executed, customers experience severe dissatisfaction. However, executing a must-be attribute flawlessly does not generate satisfaction—it merely brings the customer to a neutral state.
   • Examples: Working brakes on an automobile, clean linens in a hotel room, accurate billing invoices, and secure SSL encryption during online banking.
2. One-Dimensional / Performance Attributes (Satisfiers): Explicit requirements where customer satisfaction is directly and linearly proportional to the level of performance achieved. More is better; less is worse.
   • Behavior: High performance increases satisfaction proportionally, while poor performance decreases it. These attributes are commonly voiced in customer surveys and competitive comparisons.
   • Examples: Fuel economy in an automobile (miles per gallon), smartphone battery life, call center speed of answer, and internet bandwidth.
3. Attractive / Delighter Attributes (Exciters): Unexpected innovations or latent features that surprise and delight the customer.
   • Behavior: Because customers do not anticipate these features, their absence causes no dissatisfaction. When present, they produce disproportionately high delight, customer loyalty, and positive brand advocacy.
   • Examples: Free heated seats in a rental car, automated instant claim approval without paperwork, or a windshield that clears ice instantly.

Kano Decay: Evolving Expectations

Customer expectations are dynamic and change over time through Kano decay. Innovations that originate as delighters gradually become standard performance features as competitors adopt them. Eventually, market familiarity transforms them into mandatory must-be baselines. For example, remote keyless entry and rearview backup cameras were once luxury delighters; today, they are mandatory basic requirements expected in every passenger vehicle.

---

The Critical-to-Quality (CTQ) Tree

Raw customer feedback collected through VOC activities is almost always subjective, ambiguous, and emotional (e.g., "The service is too slow," "The app is hard to use"). A Six Sigma team cannot design a data-driven measurement plan around qualitative phrases. The team must translate the Voice of the Customer into actionable, quantifiable technical parameters using a Critical-to-Quality (CTQ) Tree.

A CTQ Tree is a hierarchical decomposition tool structured across three progressive levels:

1. Level 1: Customer Need (The Broad Voice): The high-level, qualitative statement representing the customer's overarching goal or desired outcome.
2. Level 2: Quality Drivers: The operational dimensions, functional performance categories, or structural conditions that must be present to satisfy the customer need.
3. Level 3: Critical-to-Quality (CTQ) Metrics: The specific, quantifiable technical parameters that can be tracked with numerical data. Each CTQ metric must include an unambiguous operational definition, a designated target value, and precise specification limits (Upper Specification Limit [USL] and/or Lower Specification Limit [LSL]).

Worked Example: Food Service Delivery

Consider a restaurant chain translating customer delivery expectations into measurable specifications:

• Level 1: Customer Need: "Prompt, hot, and accurate dinner delivery."
• Level 2: Quality Driver 1 (Delivery Turnaround Speed): The order must reach the customer rapidly and predictably.
  • CTQ Metric 1.1: Total elapsed delivery time from digital order confirmation to doorstep arrival.
  • Target & Specification: Target = 25 minutes; Upper Specification Limit (USL) = 30 minutes. Deliveries exceeding 30 minutes constitute a defect.
• Level 2: Quality Driver 2 (Thermal Retention): The food must arrive at an appetizing, safe temperature.
  • CTQ Metric 2.1: Core food temperature at handoff.
  • Target & Specification: Target = 155°F; Lower Specification Limit (LSL) = 140°F. Temperatures below 140°F constitute a thermal defect.
• Level 2: Quality Driver 3 (Order Accuracy): The physical items delivered must match the order exactly.
  • CTQ Metric 3.1: Order item concordance percentage.
  • Target & Specification: Target = 100%; LSL = 100%. Any missing or incorrect item constitutes an accuracy defect.