Voice of Customer Analysis
Also known as: VoC Analysis, Voice of the Customer, Customer-Needs Elicitation, VoC for Quality Function Deployment
Voice of Customer (VoC) analysis is a structured method for hearing what customers actually need, in their own words, and turning that into a prioritized, organized set of requirements for product development. Abbie Griffin and John Hauser established its modern foundations in their 1993 Marketing Science article, which examined the customer-needs component of Quality Function Deployment and answered practical questions: how many customers to interview, how to extract needs from verbatims, how to structure them, and whether one-on-one interviews or focus groups are more efficient. Their key empirical findings — that needs accumulate toward saturation, that a modest number of interviews uncovers most needs, and that one-on-one interviews are at least as productive per dollar as focus groups — turned VoC from an art into a repeatable research process. The method distills raw customer statements into solution-free need statements, organizes them into a primary-secondary-tertiary hierarchy through customer sorting, and assigns importance weights using survey priorities, an idea closely tied to importance-performance thinking. Those weighted, structured needs then feed Quality Function Deployment, where they are mapped onto engineering attributes to drive design decisions.
Key highlights
- Captures customer needs in customers' own language and solution-free, preventing premature commitment to features.
- Provides empirically grounded guidance on sample size, showing needs reach saturation so research effort can be bounded.
- Yields a customer-sorted hierarchy of needs that reflects buyers' mental models, improving requirement validity.
- Delivers prioritized requirements that plug directly into Quality Function Deployment to drive engineering decisions.
Intuition
This section is available to Pro members. Upgrade to Pro
How it works
This section is available to Pro members. Upgrade to Pro
When to use it
Use Voice of Customer analysis at the front end of product or service development, when you need a valid, prioritized set of customer requirements to guide design, and especially when you intend to feed Quality Function Deployment or a similar requirements-to-engineering process. It fits new-product concept work, redesigns, service-experience improvement, and any situation where capturing what customers truly need — in their own words and free of premature solutions — is essential. It is most valuable when the category is complex enough that needs are not obvious and when cross-functional teams must align around a shared, evidence-based requirement list. VoC is less suited to late-stage optimization where requirements are already fixed, to settings where quantitative trade-off measurement (such as conjoint analysis) is the actual question, or to situations needing statistical estimation of demand rather than qualitative needs elicitation. It is a needs-discovery and prioritization method, complementary to, not a substitute for, choice modeling and the Kano classification of need types.
Strengths & limitations
- Captures customer needs in customers' own language and solution-free, preventing premature commitment to features.
- Provides empirically grounded guidance on sample size, showing needs reach saturation so research effort can be bounded.
- Yields a customer-sorted hierarchy of needs that reflects buyers' mental models, improving requirement validity.
- Delivers prioritized requirements that plug directly into Quality Function Deployment to drive engineering decisions.
- Heavily dependent on interview and analyst skill; poor probing or biased distillation produces an invalid need set.
- Articulated needs may miss latent or unanticipated needs that customers cannot yet express.
- Importance weights from stated surveys can be flat or biased, and may diverge from derived or revealed importance.
- Qualitative and labor-intensive, providing no demand estimates, trade-offs, or willingness-to-pay on its own.
Common pitfalls
This section is available to Pro members. Upgrade to Pro
Applications
This section is available to Pro members. Upgrade to Pro
Frequently asked
How many customers do I need to interview for a VoC study?
Griffin and Hauser studied exactly this and found that customer needs accumulate toward a saturation point: early interviews surface many new needs, but each additional interview yields fewer, until new needs nearly stop appearing. Their analysis suggested that a moderate number of well-conducted one-on-one interviews — on the order of twenty to thirty for a single relatively homogeneous segment — uncovers the large majority of needs, with diminishing returns thereafter. The practical rule is to continue interviewing until you reach saturation rather than fixing the count in advance, and to add interviews when you have distinct customer segments whose needs may differ.
Are one-on-one interviews or focus groups better for collecting the voice of the customer?
Griffin and Hauser compared the two and found one-on-one interviews at least as effective per identified need, and at least as cost-effective, as focus groups for eliciting customer needs. One-on-one interviews also avoid the group-dynamic problems of focus groups, where dominant participants or social conformity can suppress or distort needs. Focus groups still have uses — for example, observing interaction or generating discussion — but for the core task of comprehensively eliciting needs, the evidence favors a series of in-depth individual interviews. This finding reshaped VoC practice toward interview-based elicitation.
Why must need statements be 'solution-free,' and how does VoC connect to QFD?
Keeping needs solution-free preserves the full design space: 'I want longer battery life' presupposes a battery, whereas 'I need my device to last all day' could be met by a bigger battery, lower power draw, or fast charging. Capturing the underlying need lets engineers find the best solution rather than locking in the customer's first guess. VoC then feeds Quality Function Deployment directly: the prioritized, structured needs become the customer-requirement rows of the House of Quality, where a relationship matrix links each need to engineering attributes and importance weights propagate to technical priorities. Griffin and Hauser framed VoC as exactly this front end, which is why the analysis is only complete when the voice is translated into design targets.
Sources
- 1.Griffin, A., & Hauser, J. R. (1993). The Voice of the Customer. Marketing Science, 12(1), 1-27.
- 2.Martilla, J. A., & James, J. C. (1977). Importance-Performance Analysis. Journal of Marketing, 41(1), 77-79.
You have read it. What now?
Cite this page
ScholarGate. (2026, June 23). Voice of Customer Analysis. ScholarGate. https://scholargate.app/marketing-science/voice-of-customer-analysis