The Voice of the Customer: How to Translate Needs into Requirements
Every Lean Six Sigma project begins with a question: what does quality look like from the customer's perspective? It sounds straightforward. In practice, it is one of the most demanding analytical challenges in process improvement. Customers describe what frustrates them, not what would delight them. They refer to symptoms rather than causes. They accept constraints they have lived with so long that they no longer think to mention them. The Voice of the Customer methodology exists to navigate this gap — to move from the noise of customer feedback to a precise, measurable understanding of what the process must deliver.
The three layers of customer need
A useful framework distinguishes three kinds of customer need that any VOC programme must uncover.
Stated needs. What customers say when you ask them directly. "I want faster delivery." "The invoice should be accurate." Stated needs are the starting point, but they are rarely the complete picture. Customers describe outcomes in the language of their own experience, which may not map cleanly onto the process variables you can actually control.
Real needs. What customers actually mean beneath the stated need. "Faster delivery" often means "reliable delivery" — customers can plan around a consistent four-day lead time more easily than an unreliable two-day average. Interviews that probe for context — "What happens when that doesn't work?" "What are you doing when you most need this?" — reliably surface the real need beneath the stated one.
Latent needs. What customers have not yet articulated — because they have accepted the limitation as inevitable, or because they cannot conceive of a better alternative. Latent needs are the hardest to uncover through direct questioning and the most likely source of genuine competitive differentiation when an improvement programme surfaces and addresses them.
VOC data collection methods
No single method captures all three layers of need. Effective VOC programmes use a combination of approaches whose outputs are synthesised rather than treated as independent data sets.
Surveys. Surveys provide breadth: they allow you to collect structured data from a large sample and quantify the relative importance of different requirements. Their limitation is that they are constrained by the questions you thought to ask. A survey cannot surface the latent need you did not know existed.
Interviews. One-on-one interviews provide depth. A skilled interviewer using open-ended questions and active listening will consistently surface needs — and the contexts that give them meaning — that no survey would have captured. Interviews are resource-intensive but essential for understanding the "why" behind stated requirements.
Focus groups. Focus groups surface group dynamics: they reveal how customers talk about needs in relation to each other, which requirements they regard as shared versus personal, and how they rank priorities when trade-offs are made explicit. The risk is social desirability — vocal participants can anchor the group and suppress minority views that may represent important segments.
Complaint analysis. Customer complaints are failure signals. They are a biased sample — most customers who are dissatisfied do not complain, they simply leave — but the complaints you do receive identify the pain points severe enough to generate a response. Complaints are particularly valuable for anchoring the Define phase because they name the harms the improvement project must eliminate.
Ethnographic observation. Observing customers in their actual environment as they interact with your product or service reveals needs that customers themselves cannot articulate because the behaviour is habitual and invisible to them. Workarounds — the informal solutions customers have built around limitations in your current offering — are among the most reliable signals of unmet latent needs.
From VOC to Critical to Quality characteristics
Raw VOC data — interview transcripts, survey results, complaint logs — cannot directly drive process improvement. The data must be translated into Critical to Quality (CTQ) characteristics: specific, measurable process or product attributes whose performance directly determines customer satisfaction. The translation process typically involves affinity mapping (grouping related customer statements into themes), followed by a structured translation from customer language ("the invoice takes too long to arrive") to a measurable CTQ ("invoice issued within 48 hours of service delivery"). The CTQ is the bridge between the qualitative richness of VOC data and the quantitative rigour of DMAIC Measure and Analyse.
The Kano model: not all CTQs are equal
The Kano model, developed by Noriaki Kano in the 1980s, provides a framework for prioritising customer requirements by classifying them according to the relationship between performance and satisfaction. Must-be requirements (threshold requirements) cause dissatisfaction when absent but generate no additional satisfaction when exceeded — they are table stakes. Performance requirements generate satisfaction proportional to performance: faster is better, more accurate is better. Attractive requirements (delighters) are the latent needs: customers do not expect them, so their absence causes no dissatisfaction, but their presence generates disproportionate satisfaction. Knowing which category a CTQ falls into determines where improvement investment will generate the most customer impact. Exceeding a must-be requirement wastes resources; delivering a delighter creates competitive advantage.
If your improvement programme is generating projects but not the customer satisfaction gains you expected, XNM's strategic advisory services can help you assess whether your VOC process is capturing the right requirements and whether your CTQs are measuring what customers actually care about.