Voice of the Customer, Explained

Voice of the Customer, or VOC, is the discipline of capturing what customers actually need — in their own words — and translating those words into measurable requirements a process can be judged against. It is the raw material of the Define phase: every CTQ, every defect definition, and every specification limit should trace back to it.

How it’s used

VOC arrives through several channels: interviews, surveys, complaint logs, support tickets, reviews, and direct observation of customers using the product or service. Each channel distorts differently — surveys tend to reach the satisfied, complaint logs reach the furious, and observation catches what people do rather than what they say — so careful teams combine at least two. The gathered statements are grouped into themes, and each theme is translated into a requirement with a measure and a limit.

The translation step is where VOC earns its keep. A raw statement cannot drive a project; a requirement can.

VOC is also a hedge against the most common failure in improvement work: building a project around what the organization finds annoying rather than what the customer finds unacceptable. Internal irritations are real, but a chartered Six Sigma project earns its cost by moving something a customer can feel. VOC is how the team checks, before committing months of work, that it is aiming at one of those.

A worked mini-example

An illustrative software company reviews three months of support tickets and finds a recurring theme expressed in different words: customers do not know the status of their open issues. Nobody wrote the phrase status update, but the pattern is unmistakable — repeated check-in emails, escalations arriving days after the frustration began. The team translates the theme into a requirement: every open ticket receives a status update on a defined cadence, measurable directly from the ticket system. A vague unhappiness has become a checkable standard, and a project can now be chartered against it.

• Record the customer’s actual words first; interpret second — summaries erase evidence
• Complaint logs are a VOC channel you already pay for; mine them before commissioning surveys
• Watch customers use the product when you can; behavior contradicts self-report
• Translate every theme into a measurable requirement, or it will be forgotten
• Refresh VOC periodically — expectations move, and old translations expire

The customer speaks in frustrations. Your job is to translate them into limits a process can be held to.

VOC methods and the translation to CTQs appear early in our curriculum: Yellow Belt covers the channels and the translation step, and Green Belt applies them in the Define phase of its simulated project, where the requirements you write drive the rest of the work.