2.7 Customer Relations & Customer Value

Customer Relations & Customer Value

In Quality Engineering, quality is ultimately defined by the customer. According to Joseph Juran, quality is "fitness for use," while W. Edwards Deming emphasized meeting and exceeding customer expectations over the full product lifecycle. Section 2.7 explores how organizations systematically capture the Voice of the Customer (VoC), evaluate customer perception using Kano analysis and Net Promoter Score (NPS), and maintain rigorous closed-loop customer complaint resolution workflows governed by ISO 10002.

---

1. Voice of the Customer (VoC) Gathering & CTQ Translation

The Voice of the Customer (VoC) represents the collective explicit and implicit requirements, expectations, preferences, and feedback articulated by internal and external customers.

VoC Data Collection Methodologies:

• Direct / Reactive Methods: Customer complaints, warranty claim filings, tech support tickets, return material authorizations (RMA), field service reports.
• Direct / Proactive Methods: Focus groups, contextual customer interviews, broad customer satisfaction surveys, ethnographic observation of product usage.
• Indirect / Digital Methods: Social media sentiment mining, online review aggregation, customer usage telemetry, market research panels.

Translating VoC into Critical-to-Quality (CTQ) Metrics:

Raw customer statements are often qualitative, subjective, and ambiguous (e.g., "The handheld drill feels too heavy and awkward"). Quality engineers must systematically translate qualitative VoC statements into measurable, actionable engineering specifications called Critical-to-Quality (CTQ) parameters using Quality Function Deployment (QFD) and the House of Quality.

Raw Customer Voice (VoC) ──> Customer Need ──> Measureable CTQ Specification ──> Engineering Tolerance
"The battery runs out too fast" ──> Long battery life ──> Continuous operating runtime ──> ≥ 8.5 Hours @ 12V Nominal

---

2. Kano Model of Customer Satisfaction

Developed by Professor Noriaki Kano in 1984, the Kano Model maps product features against customer satisfaction and degree of execution. It categorizes quality attributes into three primary classes (plus two secondary classes):

Satisfaction (High)
      ▲               Attractive (Delighters)
      │              /
      │             /   Performance (One-Dimensional)
      │            /   /
      │           /   /
 ─────┼──────────/───/────────────────► Execution / Fulfillment (High)
      │         /   /
      │        /   /  Must-Be (Basic)
      │       /   /  /
      ▼      /   /  /
Dissatisfaction (Low)

Primary Kano Attribute Categories:

1. Must-Be / Basic Attributes (Dissatisfiers): Requirements that customers take for granted. If fulfilled, customer satisfaction remains neutral (does not increase). However, if absent or failing, severe customer dissatisfaction occurs. Example: Brakes on a commercial vehicle or clean bedsheets in a hotel.
2. Performance / One-Dimensional Attributes: Attributes where customer satisfaction is linearly proportional to the level of performance delivered. More is better. Example: Fuel efficiency (miles per gallon) or internet download speed.
3. Attractive / Excitement Attributes (Delighters): Unexpected, innovative features that provide intense delight if present, but cause zero dissatisfaction if absent because customers did not anticipate them. Example: Free high-speed Wi-Fi on airlines when first introduced.

Secondary Categories:

• Indifferent Attributes: Features that customers simply do not care about regardless of implementation.
• Reverse Attributes: Features that actively cause dissatisfaction for some customers when present (e.g., overly complex software menus).

Kano Attribute Decay Law: Over time, customer expectations shift. Features that begin as Attractive Delighters (e.g., touchscreen displays in automobiles) inevitably migrate into Performance Attributes, and eventually decay into mandatory Must-Be Attributes. Quality engineers must continuously innovate to replenish attractive features.

---

3. Net Promoter Score (NPS) Methodology & Analytics

The Net Promoter Score (NPS), formulated by Fred Reichheld, is a widely adopted metric assessing customer loyalty and brand advocacy based on a single core question:

"On a scale of 0 to 10, how likely are you to recommend our product or service to a friend or colleague?"

Respondent Categorization (11-Point Scale):

• Promoters (Score 9–10): Loyal, enthusiastic advocates who drive organic growth through repeat purchases and referrals.
• Passives (Score 7–8): Satisfied but unenthusiastic customers vulnerable to competitive offerings. Excluded from the NPS equation percentage calculation.
• Detractors (Score 0–6): Unhappy customers who can damage brand reputation through negative word-of-mouth and high support costs.

Mathematical NPS Formula:

$\text{NPS} = \% \text{Promoters} - \% \text{Detractors}$

The Net Promoter Score is expressed as an integer between -100 (where 100% of respondents are Detractors) and +100 (where 100% of respondents are Promoters).

Quantitative NPS Worked Example Scenario:

A medical device manufacturer surveys 1,200 clinical users regarding a new ultrasound scanner. Survey results yield the following score breakdown:

• Scores 9–10 (Promoters): 660 respondents
• Scores 7–8 (Passives): 360 respondents
• Scores 0–6 (Detractors): 180 respondents

1. Calculate % Promoters: $\% \text{Promoters} = \left( \frac{660}{1,200} \right) \times 100\% = 55.0\%$
2. Calculate % Detractors: $\% \text{Detractors} = \left( \frac{180}{1,200} \right) \times 100\% = 15.0\%$
3. Compute Net Promoter Score: $\text{NPS} = 55.0\% - 15.0\% = +40$

An NPS of +40 indicates strong customer advocacy, though failure analysis must be performed on the 180 Detractors to isolate specific hardware or software friction points.

---

4. Closed-Loop Customer Complaint Resolution Workflows

Customer complaint management is governed internationally by ISO 10002:2018. An effective quality system treats complaints not as administrative burdens, but as vital, free quality audit data.

Closed-Loop ISO 10002 Complaint Resolution Workflow:

1. Receipt & Logging: Log complaint into Customer Relationship Management (CRM) / Quality Management System within 24 hours. Assign unique tracking ID.
2. Acknowledgment & Initial Response: Provide formal receipt acknowledgment to the customer detailing escalation pathways and contact contacts.
3. Triage & Containment: Assess defect severity (Safety Risk vs. Functional Failure vs. Cosmetic). Issue immediate containment (RMA, advance replacement, safety hold notice).
4. Technical Root Cause Investigation: Quality Engineering performs failure analysis (FA) on returned components using 8D methodology, 5 Whys, and scanning electron microscopy (SEM) or teardown labs.
5. Corrective Action Implementation (CAPA): Deploy permanent process/design fixes to eliminate defect root causes in production.
6. Customer Communication & Closure: Provide the customer with an executive summary 8D report detailing corrective actions taken. Verify customer satisfaction before formal closure.
7. Management Review & Trend Analysis: Aggregate complaint data into Pareto charts to track Mean Time to Resolve (MTTR) and drive continuous improvement.

---

5. Summary of Customer Value & Kano Frameworks