VOC and Customer Journey — From "What the Customer Says" to "What We Do"
Abstract: VOC (Voice of Customer, customer voice) is not just about filling out a satisfaction survey. Truly valuable VOC comes from systematic collection at various touchpoints of the customer journey and can be translated into CTQ (Critical to Quality) to drive design and process control. This article discusses methods for collecting VOC, mapping the customer journey, and the basic path from VOC to QFD (Quality Function Deployment) to specification implementation.
1. A Lesson: Doing What the Customer Didn’t Want
A certain industrial equipment manufacturer invested 2 million yuan in upgrading the UI interface, which was internally reviewed as "grand and beautiful." However, sales were mediocre after the product launch—post-sales follow-up revealed that customers were most concerned about fault diagnosis speed, spare parts delivery within 48 hours, and the clarity of on-site maintenance manuals, rather than the interface's aesthetics.
The demand research only asked "Are you satisfied?" without inquiring about the scenarios in which customers encounter pain points—the dimensions for VOC collection were incorrect.
2. What is VOC?
VOC is the structured expression of customer demands, expectations, complaints, and preferences regarding products/services. Sources include:
- Contracts and CSR (Customer Special Requirements)
- Tender technical specifications
- After-sales warranty, complaints, NPS surveys
- On-site service, audits, joint improvement meetings
- Industry benchmarks, regulatory standards
The goal of VOC is not to "record the exact words," but to identify measurable requirements for design, process, and quality decision-making.
3. Customer Journey: The Map for VOC Collection
Customer Journey (Customer Journey) describes the stages of interaction between the customer and the product/service in chronological order. In a typical B2B manufacturing scenario:
| Stage | Touchpoint Examples | Possible VOC |
|---|---|---|
| Pre-sales | Selection, quotation, technical exchange | Delivery cycle, certification qualifications |
| Order | Contract, change, production scheduling confirmation | Delivery commitment, order visibility |
| Incoming/Production | (As a supplier) audit, PPAP | Document completeness, batch traceability |
| Delivery | Logistics, packaging, unpacking | Cargo damage, labeling, accompanying documents |
| Usage | Installation, commissioning, operation | Usability, reliability, documentation |
| After-sales | Warranty, claims, upgrades | Response time, first-time fix rate |
Mapping Steps:
- Select target customer segments/product families
- List stages and touchpoints
- Collect VOC at each touchpoint (quantitative + qualitative)
- Annotate the emotional curve (satisfaction/pain points/surprises)
- Prioritize (optional use of Kano model)
4. From VOC to CTQ
CTQ (Critical to Quality) are measurable and specifiable key characteristics.
Translation Examples:
| VOC (Original Words) | CTQ |
|---|---|
| "Don't keep breaking down" | MTBF ≥ X hours; warranty period PPM ≤ Y |
| "Changeover is too slow" | Changeover time ≤ 30 min |
| "Dimensions are unstable" | Cpk ≥ 1.33 |
| "Need quick response when problems arise" | 8-hour on-site response, 24-hour temporary countermeasures |
Tool: QFD (Quality Function Deployment) maps VOC to design characteristics, process parameters, and inspection methods—see DFSS/DMADV series (6.1.2).
5. VOC Management Process
Collection → Categorization → Prioritization → Conversion to Specifications/Targets → Verification and Closure → Update
Organizational Recommendations:
- VOC Owner (often quality or product) coordinates cross-departmental efforts
- Interface with CSR Management (10.1.1)—contract requirements enter the VOC database
- Interface with Complaint Analysis (1.3.2)—complaints are strong signals of VOC
- Regular (quarterly) VOC Review Meetings—participation from sales, service, R&D, and quality
6. Common Misconceptions
Misconception One: VOC = Whatever the Customer Says. It is necessary to distinguish between basic, performance, and excitement requirements (Kano)—doing everything will lead to cost overruns.
Misconception Two: Collecting Without Closure. Customer feedback requires a mechanism for acceptance/rejection and reasons.
Misconception Three: VOC is Only Used in New Product Stages. CSR changes and claims trends in mass production stages are also inputs for VOC.
7. Conclusion
VOC and the customer journey are the starting points for translating market language into engineering language—VOC without a map is scattered, and VOC without CTQ is just slogans.
Hearing the customer is essential, but understanding the context, quantifying the requirements, and closing the loop for verification—this is the fundamental skill in the 1.3 Customer and Market segment of quality strategy.
Knowledge code: 1.3.1
Version: v20260523
Author: Quality Think Tank