How Can the Kano Model Turn Customer Voice (VOC) into Product Priorities?

Every product team hears customer feedback, but not all feedback is equal. Some features, when missing, cause fury; others, when added, cause delight. The Kano Model—developed by Professor Noriaki Kano in 1984—provides a structured way to analyze the Voice of the Customer (VOC) and classify needs so you can prioritize what truly matters.

What It Is

The Kano Model is a theory of product development and customer satisfaction. It categorizes customer requirements into five types, with three primary ones driving most decisions:

• Must-Be (Basic) Needs: Expected by default. If absent, customers are highly dissatisfied; if present, satisfaction does not increase. Example: a car's brakes.
• One-Dimensional (Performance) Needs: Satisfaction rises linearly with performance. More is better. Example: battery life on a smartphone.
• Attractive (Delight) Needs: Not expected, but their presence creates disproportionate satisfaction. Their absence causes no dissatisfaction. Example: a free upgrade to first class.

Two other categories—Indifferent (does not matter) and Reverse (some customers want it, others do not)—complete the framework.

The model is built on data captured through VOC activities: interviews, surveys, complaints, and social listening. It translates raw customer language into structured categories that guide design and resource allocation.

How It Works / Steps

The standard method uses a paired-question survey per feature:

1. Capture VOC: Collect raw customer statements about a product or service.
2. Translate into features: Turn each statement into a concrete, testable feature.
3. Design a Kano questionnaire: For each feature, ask two questions:

- Functional form: "How do you feel if this feature is present?"
- Dysfunctional form: "How do you feel if this feature is absent?"

1. Use a 5-point scale: Like it / Expect it / Neutral / Tolerate it / Dislike it.
2. Classify each response: Map the pair of answers onto the Kano evaluation table (see below).
3. Aggregate and decide: Count the majority category for each feature. If no clear majority, apply rules (e.g., Must-Be > One-Dimensional > Attractive > Indifferent) to resolve ties.

### Kano Evaluation Table (Classic)

Functional \ Dysfunctional | Like | Expect | Neutral | Tolerate | Dislike

• Like | Q | A | A | A | O
• Expect | R | I | I | I | M
• Neutral | R | I | I | I | M
• Tolerate | R | I | I | I | M
• Dislike | R | R | R | R | Q

Legend: A = Attractive, O = One-Dimensional, M = Must-Be, I = Indifferent, R = Reverse, Q = Questionable (contradictory answer).

A Worked Illustrative Example

Example data (illustrative only) — Suppose you survey 100 users on a mobile banking app about the feature "biometric login."

Category | Count

• Must-Be (M) | 55
• One-Dimensional (O) | 20
• Attractive (A) | 10
• Indifferent (I) | 10
• Reverse (R) | 3
• Questionable (Q) | 2

The majority is Must-Be (55%). Interpretation: Users expect biometric login as a basic security feature. Adding extra polish to it will not increase satisfaction; you must simply ensure it works flawlessly.

Now compare with a second feature, "personalized spending insights":

Category | Count

• Attractive (A) | 60
• One-Dimensional (O) | 15
• Indifferent (I) | 20
• Must-Be (M) | 5

Here the majority is Attractive (60%). This feature is a differentiator—investing here can create delight, but only after all Must-Be items are solid.

Decision rule: Fix Must-Be first, improve One-Dimensional next, and invest in Attractive features for competitive advantage.

Common Pitfalls

• Confusing Must-Be with Attractive: A feature that is "nice to have" for you may be "expected" by your users. Always rely on survey data, not intuition.
• Ignoring the Reverse category: If a feature shows high Reverse scores, consider offering it as an option rather than a default.
• Small sample sizes: Kano classification requires a representative sample. With fewer than 30 responses, the majority category may be unstable.
• Over-surveying: Asking too many paired questions causes respondent fatigue and unreliable answers.

---

To apply the Kano Model to your own VOC data quickly, use the free, structured tool at https://www.6sq.com/tools/kano_voc/ — it handles the classification table and aggregation for you, letting you focus on the product decisions.