In one line: The disciplined practice of capturing customers’ needs in their own words, structuring and prioritizing them, and carrying them all the way into engineering decisions.
Core idea
“Voice of the customer” entered general use with a landmark study by Abbie Griffin and John Hauser [1]. They asked practical questions that product teams still face: how many customers you need to interview, whether interviews or focus groups work better, how to group needs, and how to measure their importance. Their answers turned customer research from an art into a repeatable method that feeds directly into quality tools like the House of Quality.
How it works
- Diminishing returns. A relatively small number of well-run interviews uncovers most needs; each additional interview adds less. Several analysts reading the same transcripts find more needs than one.
- One-on-one interviews proved about as effective as focus groups per customer, and far more efficient.
- Customer-sorted hierarchies, where customers group the needs themselves, better reflect how they think than groupings imposed by engineers.
- Importance and satisfaction can be measured with surveys and compared with competitors, revealing where improvement matters most.
- Stories, not just statements. A related reading argues that customer stories, told in their own words about real experiences, carry context and emotion that checklists lose, and that organizations should deliberately collect and share them [2].
In practice
In engineering organizations the “customer” may be a program office, a system integrator or an internal user, and their voice often arrives filtered through requirements documents. VOC practice asks for direct contact: sit with the operator, read the field-service reports, listen to how people describe the problem. Bringing a customer story into a design review in the customer’s own words is often more persuasive than any summary chart.
Questions to ask yourself
- When did my team last hear a customer describe a problem in their own words?
- How many perspectives are hidden behind our requirements document?
- Which customer story would change how we prioritize?
Connections
- The method: Identifying Customer Needs. Where the voice goes next: House of Quality.
- The fuzzy front end it informs: Product Development Funnel. Why stories persuade: Storytelling as Leadership.
- Capabilities exercised: Inquiry, Communicating and Advocacy.
Sources
- Griffin and Hauser (1993) The Voice of the Customer [1]
- Gorry and Westbrook (2011) Can You Hear Me Now [2]