What is voice of the customer?
Voice of the customer (VOC) is a structured way to hear what customers need and turn it into requirements. Customers rarely speak in specifications: they say "release dates slip without warning" or "I have to email three people to find out where my order is". VOC keeps those words, groups them into a short list of needs, and then translates each need into a measurable critical customer requirement (CCR) that a team can design for, measure and improve.
VOC is the first step in many quality methods: the Define phase of DMAIC, the Measure phase of design for Six Sigma, and the left wall of the house of quality.
VOC sources
| Source | Type | Good for |
|---|---|---|
| Interviews and visits | Proactive | Depth: why a need matters, unspoken needs |
| Surveys | Proactive | Breadth: how many customers share a need, by segment |
| Complaints and returns | Reactive | What hurts today; often the must-be needs |
| Support calls | Reactive | Usability and information gaps |
| Customer audits | Reactive | Compliance and documentation expectations |
| Sales and account teams | Indirect | Lost deals, requests, competitor comparisons |
From verbatims to CCRs
- Verbatim: what the customer said, unedited. "Our QA spends days on queries about missing signatures."
- Need: the underlying need, in the customer's terms. "Batch records right first time."
- CCR: the measurable requirement. "≤ 2 review queries per batch record."
A good CCR has a metric, a direction or limit, and is something the customer would recognise as success. If the need is broad, break it down with a CTQ tree first.
Voice of the customer example
A contract manufacturer reviews 19 customer statements from interviews, surveys, complaints, customer audits and the account team. Grouped into five needs, batches delivered when promised comes up most (5 statements, from all three customer segments) and becomes the CCR "≥ 95% of batches released by the agreed date". Fast, open handling of deviations and right-first-time batch records follow with four statements each; the bars show that deviation handling is raised mostly through complaints, and batch record quality mostly in customer audits. Flexibility for small order changes has no measurable requirement yet, and one statement about invoices is not assigned to any need, so the tool flags both.
Tips
- Keep the customer's words. Paraphrasing too early loses the meaning and the emotion behind a need.
- Ask "why?" behind requests for solutions: "a status portal" is a solution; "know where my order is" is the need.
- Cover every segment and both happy and unhappy customers.
- Mentions are not importance. Rate importance separately; some critical needs are rarely mentioned because they are taken for granted. A Kano survey reveals them.
- Group many statements first with an affinity diagram.
How to use this Voice of the Customer tool
- Name the study. Describe which customers and which period the VOC covers.
- Record the statements. Enter what customers said word for word, with the source and the customer segment, or paste many at once.
- Group into needs. Click + on the chart to add a need, and assign each statement to the need it expresses.
- Rate importance. Click a need to set how important it is to customers (1–5).
- Write the CCR. For each need, write the critical customer requirement: a measurable target or limit.
- Export. Export the VOC translation table and chart to PDF or Excel.
Frequently asked questions
What is voice of the customer (VOC)?
Voice of the customer is the process of capturing what customers say about their needs, expectations and frustrations, in their own words, and translating it into requirements the organization can design, measure and improve against. It is the starting point of Six Sigma, QFD and design for Six Sigma projects.
What are the main VOC sources?
Reactive sources arrive on their own: complaints, support calls, returns, warranty claims and reviews. Proactive sources are ones you go after: interviews, surveys, focus groups, customer visits and audits, observation of customers using the product, and feedback from the sales and account teams. Good VOC combines both, because complaints only show what went wrong.
What is a critical customer requirement (CCR)?
A CCR is a customer need restated as a specific, measurable requirement, for example "Delivered on time" becomes "95% of orders delivered by the date promised at order entry". CCRs connect what the customer says with what the process must achieve, and become the CTQs of an improvement or design project.
How do I translate VOC into requirements?
Collect verbatim statements, group them into needs (an affinity diagram helps), and for each need ask "what would the customer measure to judge this?". Write that as a CCR with a metric, a target and a limit. A CTQ tree then breaks the need into drivers and measurable CTQs.
How many customers should I talk to?
For interviews, a classic study by Griffin and Hauser found that 20 to 30 one-to-one interviews per segment reveal roughly 90% of the needs. For surveys, use enough responses per segment to compare segments. More important than the number is covering every segment and both satisfied and dissatisfied customers.
What is the difference between VOC and a Kano analysis?
VOC finds and quantifies the needs. A Kano analysis then asks how each need or feature affects satisfaction: whether it is expected (must-be), whether more is better (performance) or whether it delights. Use VOC first, Kano to prioritise.