Quality is what the customer says it is, but customers rarely say it in a form you can measure. The voice of the customer is the discipline of gathering what customers want, in their words, and turning it into requirements a team can design to.
This guide covers the main sources of customer input, how to translate it into critical-to-quality characteristics, and the Kano model, which sorts features into must-be, performance, and attractive categories. A worked example classifies four features of a cordless tool from survey data.
Why the Voice of the Customer Matters
Quality Is Defined by the Customer
A product that meets every internal spec can still fail if it misses what customers actually value.
Requirements Are Rarely Stated Well
Customers say what they want in their own words. Someone has to turn those words into measurable requirements.
Features Are Not All Equal
Some features are expected and only noticed when missing, some raise satisfaction in proportion, and some delight. Kano's model tells them apart.
Prioritization Needs Evidence
Limited budgets mean choosing. Customer data keeps the choice from being the loudest opinion in the room.
Gathering the Voice of the Customer
| Source | What it gives you | Watch out for |
|---|---|---|
| Interviews and site visits | Deep understanding of context and unstated needs | Small samples; interviewer bias. |
| Surveys | Numbers across many customers | Leading questions; low response. |
| Complaints and returns | What fails in real use | Only unhappy customers who report. |
| Warranty and service data | Failure patterns | Lag between cause and data. |
| Observation (gemba) | What people actually do | Requires time and access. See the Gemba Walk Guide. |
Then translate what customers said into requirements you can measure. "It should not die in the middle of a job" becomes a Critical-to-Quality (CTQ) characteristic such as runtime per charge, with a target and a tolerance. See Voice of the Customer and Critical to Quality.
The Kano Model
Noriaki Kano's model (1984) classifies features by how they affect satisfaction:
| Category | If present | If absent | Example |
|---|---|---|---|
| Must-be (basic) | Nobody notices; it is expected | Strong dissatisfaction | A phone that makes calls |
| One-dimensional (performance) | More is better | Less is worse | Battery life |
| Attractive (delighter) | Delight | Nobody notices | A feature nobody expected |
| Indifferent | No effect | No effect | A feature nobody cares about |
| Reverse | Some customers dislike it | Some prefer without | Too many settings |
Over time, delighters become performance features and then must-be features, as expectations rise. That is why the survey must be repeated.
The Kano Survey
For each feature, ask two questions: how would you feel if the product had the feature (functional), and how would you feel if it did not (dysfunctional)? Each answer is one of: I like it, I expect it, I am neutral, I can live with it, I dislike it. Combine the two answers using the evaluation table:
| Functional \ Dysfunctional | Like | Expect | Neutral | Live with | Dislike |
|---|---|---|---|---|---|
| Like | Q | A | A | A | O |
| Expect | R | Q | I | I | M |
| Neutral | R | I | I | I | M |
| Live with | R | I | I | I | M |
| Dislike | R | R | R | R | Q |
M = must-be, O = one-dimensional, A = attractive, I = indifferent, R = reverse, Q = questionable (a contradictory answer). Count the categories for each feature across respondents.
Worked Example: Features of a Cordless Tool
A product team surveys 40 users on four candidate features. The counts are illustrative.
| Feature | M | O | A | I | R | Q | Category (most common) |
|---|---|---|---|---|---|---|---|
| A. Overheat shut-off | 28 | 6 | 2 | 3 | 0 | 1 | Must-be |
| B. Runtime per charge | 8 | 24 | 5 | 3 | 0 | 0 | Performance |
| C. Built-in work light | 2 | 8 | 22 | 8 | 0 | 0 | Attractive |
| D. Bluetooth app | 1 | 3 | 10 | 20 | 6 | 0 | Indifferent |
To rank them, use the satisfaction coefficients: Better = (A + O) / (A + O + M + I) and Worse = −(O + M) / (A + O + M + I).
| Feature | Better (satisfaction if present) | Worse (dissatisfaction if absent) |
|---|---|---|
| A. Overheat shut-off | 8 / 39 = 0.21 | −34 / 39 = −0.87 |
| B. Runtime per charge | 29 / 40 = 0.73 | −32 / 40 = −0.80 |
| C. Built-in work light | 30 / 40 = 0.75 | −10 / 40 = −0.25 |
| D. Bluetooth app | 13 / 34 = 0.38 | −4 / 34 = −0.12 |
Decisions. The overheat shut-off is non-negotiable: the product is unacceptable without it, but adding it wins little. Runtime is where competition happens, and improvement earns real satisfaction. The work light is cheap to add and delights, so it is a good differentiator. The Bluetooth app is expensive and most users do not care, and 6 of 40 dislike it, so it drops from the list, for now. The team also knows that today's delighter, the work light, may become expected, so it will re-run the survey in a year or two.
Analyze your own survey with the Kano Model Analyzer.
From Customer Words to Requirements
Raw customer comments are messy: they mix needs, complaints, solutions, and opinions. The value comes from turning them into clear, measurable requirements that design and operations can act on.
Capture needs, not solutions. “I want a bigger button” is a solution; the underlying need may be “I can operate it with gloves on.” Ask why until the need is clear, then record it in the customer's language.
Group and prioritize. An affinity diagram clusters similar needs. Importance ratings, or a simple vote, show which ones matter. The Kano classification adds something ratings miss: which needs are basic expectations, which are performance needs, and which delight.
Translate into requirements. For each priority need, agree a measure and a target, for example “changeover performed in under 10 minutes wearing gloves.” A critical-to-quality tree links the broad need to the specific characteristics the team can control. See the DMAIC Roadmap for where this fits in Define.
Pitfalls, and Keeping Kano Categories Current
A few patterns reduce the value of VOC work. Knowing them helps avoid wasted effort.
- Only hearing the loudest customers. Complaints come from the vocal few. Sample across segments, including those who left or never bought.
- Asking leading questions. Questions that suggest an answer produce agreement, not insight. Start with open questions about what the customer is trying to do.
- Treating stated importance as the whole story. Customers do not rate basic expectations as important until they are missing. Kano and observation fill the gap.
- Doing VOC once. Needs change. A delighter becomes a performance need and then a basic expectation as competitors copy it.
- Skipping the translation. A list of comments with no measures does not change the design.
Kano classes drift with time. Features once seen as novel, such as a phone that can take photos, became expected. Repeat the survey periodically, and track the share of customers in each class for your key features. A feature that once drew praise may now generate complaints when it is missing.
Use the result for decisions. Make sure basic expectations are all met first, because failing them cannot be offset by delighters. Invest in performance needs in proportion to their importance and your gap to competitors. Add delighters where the cost is low and the differentiation is real. The Quality Philosophy Foundations Guide shows how this customer focus connects to quality management more broadly.
Self-Assessment Questions
- Do we use more than one source for customer input?
- Have we translated customer words into measurable requirements?
- Do we know which features are basic expectations and which delight?
- Did we ask both functional and dysfunctional questions, with enough respondents?
- Do we repeat the survey as customer expectations change?
Common Mistakes
Asking Only What Customers Want
People rarely mention basic expectations or things they have never seen. Observe and ask the paired Kano questions.
Surveying the Wrong Customers
Use the customers you want to win, not only the ones who answer the phone.
Adding Every Feature Requested
Performance and delighter features cost money. Use the categories to decide what earns its place.
Treating Categories as Permanent
Yesterday's delighter is tomorrow's expectation. Refresh the study.
Voice of the Customer and the Kano Model: Frequently Asked Questions
What is the Kano model?
The Kano model, developed by Noriaki Kano in the 1980s, classifies product features by how they affect customer satisfaction. Must-be features are expected and cause dissatisfaction when absent, performance features raise satisfaction in proportion to how well they are delivered, and attractive features delight when present but are not missed when absent.
How do you run a Kano survey?
For each feature, ask how the customer would feel if the product had it (the functional question) and if it did not (the dysfunctional question), using the answers like, expect, neutral, live with, and dislike. Combine the pair using the Kano evaluation table, then count the categories across respondents to find the most common one.
What is a critical-to-quality (CTQ) characteristic?
A CTQ is a measurable product or process characteristic that reflects a customer requirement, with a target and tolerance. It is created by translating the customer's words into a specific, measurable requirement, for example turning "the battery should last a whole job" into runtime per charge of at least a stated number of minutes.
Sources and Further Reading
- Noriaki Kano and colleagues, "Attractive quality and must-be quality," Journal of the Japanese Society for Quality Control, 1984.
- Charles Berger and colleagues, "Kano's methods for understanding customer-defined quality," Center for Quality Management Journal, 1993.
- Thomas Pyzdek and Paul Keller, The Six Sigma Handbook, on voice of the customer and CTQ.
- ASQ Certified Six Sigma Black Belt Body of Knowledge, customer identification and requirements.