Voice of Customer (VOC) Analysis
Capture what customers actually need and turn it into something you can measure. Collect and organize the Voice of the Customer, translate raw statements into Critical-to-Quality requirements, and prioritize them for the rest of your project.
Start VOC Analysis →What is Voice of Customer Analysis?
Voice of the Customer (VOC) analysis is the structured process of gathering customers' stated and unstated needs and translating them into clear, measurable requirements. It ensures a project improves what customers actually value rather than what the team assumes they value.
Raw VOC data, complaints, interviews, surveys, support logs, is usually vague and emotional ("it takes too long", "the fit is off"). VOC analysis translates these statements into specific, measurable Critical-to-Quality (CTQ) characteristics that can be targeted and tracked, such as "order-to-delivery time under 48 hours."
VOC is central to the early phases of an improvement project. It defines what "good" means from the customer's perspective and feeds directly into tools such as the CTQ tree, the Kano model and the House of Quality, which prioritize and deploy those requirements into the design and process.
In plain terms: Customers tell you what's wrong in their own words, which are often vague. VOC analysis is the discipline of listening systematically, then converting fuzzy statements like 'it's too slow' into a hard target like 'ships within 48 hours' that you can actually measure and improve.
The VOC Workflow
Collect
Gather VOC from multiple sources: interviews, surveys, complaints, reviews, support tickets and observation. Different sources reveal stated and unstated needs.
Translate to CTQs
Convert each need into a specific, measurable requirement with a target. "Reliable" becomes a defined uptime or defect-rate target.
Prioritize
Rank requirements by importance to the customer, often using survey weighting or the Kano model, so effort focuses on what matters most.
Key Formulas
Turning VOC into Action
A good CTQ is specific, measurable, and tied to a customer need. If you cannot state how you would measure it, the translation is not finished. Each CTQ should trace back clearly to the customer statement that produced it.
Prioritization prevents the common failure of treating every stated need as equally important. Combining an importance rating with the current performance gap highlights the requirements where improvement will move customer satisfaction the most.
Assumptions & Validation
Representative Sources
VOC is gathered from a representative range of customers, not just the loudest voices.
If violated: Broaden sampling; a few vocal complaints can bias priorities.
Faithful Translation
CTQs must preserve the customer's actual intent, not the team's convenience.
If violated: Validate translated CTQs back with customers where possible.
Measurability
Each CTQ must be defined so it can be measured objectively.
If violated: Add an operational definition and a data source for each CTQ.
⚠️ Check assumptions first
The main risk in VOC work is substituting the team's assumptions for the customer's actual voice. Translating a need into a CTQ that is convenient to measure but no longer reflects what the customer meant produces a project that hits its targets while missing the point. Trace every CTQ back to a real customer statement, and validate the translation with customers whenever you can.
When NOT to Use Voice of Customer (VOC) Analysis
Internal Process Metrics Only
For purely internal efficiency work with no external customer dimension, VOC may add little; use process data directly.
Requirements Already Well Defined
If measurable customer requirements already exist and are validated, move straight to CTQ deployment tools.
Statistical Testing
VOC structures qualitative needs; it does not test hypotheses. Use statistical tests for that.
Industry Applications
New Product Definition
Translate market and customer research into measurable design requirements before development begins.
Service Improvement
Convert complaint and survey themes into measurable service-level targets.
Six Sigma Define Phase
Establish the customer-facing CTQs that a DMAIC project will target and measure.
Requirement Prioritization
Rank competing customer needs to focus limited development and improvement resources.
Frequently Asked Questions
What is the difference between VOC and CTQs?
The Voice of the Customer is the raw, often qualitative expression of customer needs in their own words, such as it takes too long or it feels cheap. Critical-to-Quality characteristics are the measurable requirements those needs translate into, such as delivery within 48 hours or a defined material thickness. VOC is the input; CTQs are the measurable output you can target.
How do I translate a vague customer need into a CTQ?
Identify the underlying requirement behind the statement, then define a specific characteristic, a way to measure it, a target value, and acceptable limits. For example, the complaint the coffee is never hot enough becomes serving temperature between 65 and 70 degrees Celsius. The test of a good translation is whether you can measure it objectively.
What sources should I use to collect VOC?
Use a mix of reactive and proactive sources. Reactive sources include complaints, returns, warranty claims and support logs, which surface problems. Proactive sources include interviews, surveys, focus groups and direct observation, which reveal needs customers may not volunteer. Combining sources reduces the bias of relying only on the loudest voices.
How does the Kano model fit into VOC analysis?
After translating needs into CTQs, the Kano model classifies them by their effect on satisfaction: basic needs that cause dissatisfaction if missing, performance needs where more is better, and excitement needs that delight when present. This classification helps prioritize CTQs, since basic needs must be met before performance and excitement features add value.
Why is prioritizing VOC important?
Treating every stated need as equally important spreads effort thinly and often improves things customers do not care much about. Prioritization, typically by combining an importance rating with the current performance gap, focuses resources on the requirements where improvement will most raise satisfaction, which is essential when time and budget are limited.
Where does VOC fit in a Six Sigma project?
VOC anchors the Define phase. It establishes what quality means from the customer's perspective and produces the CTQs the project will measure and improve. Those CTQs then flow into tools such as the CTQ tree, the House of Quality and the data collection plan, keeping the entire project aligned with genuine customer requirements.
Turn Customer Needs Into Measurable Targets
Collect VOC, translate it into CTQs, and prioritize what matters. Free during Beta.
Start VOC Analysis →