The Kano Model: Improving Customer Satisfaction
Actualizado: 2026-05-03
The Kano model answers a question product teams ask constantly: which product features have the most impact on customer satisfaction? The answer is not always intuitive, and Noriaki Kano’s framework offers a structure for separating what customers expect in silence, what they value explicitly, and what delights them unexpectedly.
Key takeaways
- Kano classifies product features into three categories: basic (threshold), performance (linear), and emotional (delighters).
- Basic features do not generate satisfaction — only their absence generates dissatisfaction.
- Emotional features cannot be identified by directly asking the customer — they require observation and testing.
- An emotional feature today can become a basic one tomorrow as the industry adopts it.
- The model is most useful at the start of product design rather than as a late validation tool.
The Three Need Categories
Basic needs (Must-be / Threshold) Features the customer takes for granted. Their presence generates no satisfaction — the customer does not mention them because they are assumed. Their absence, however, generates strong dissatisfaction.
Example: a banking app not losing transactions, a hotel having hot water, e-commerce software processing payments correctly.
Performance needs (One-dimensional) Features where more investment equals more satisfaction, linearly. Customers mention these explicitly in surveys and comparisons. They are the competitive battleground.
Example: web page load speed, mobile battery life, classification model accuracy, SaaS service pricing.
Emotional needs (Attractive / Delighters) Features the customer does not expect but that, when present, produce disproportionate satisfaction. Their absence generates no dissatisfaction — the customer did not know they needed them. They are sources of differentiation and positive word of mouth.
Example: unexpectedly good offline mode in an app, surprising product packaging, unlimited undo in an editor.
The Visual Model
The horizontal axis represents the degree of feature implementation (from absent to fully implemented). The vertical axis represents customer satisfaction (from frustration to delight). The three curves show how each type of need responds differently to the same investment axis.
How to Run a Kano Survey
The standard process combines two questions per feature:
- Functional question: “If the product has this feature, how do you feel?” (options: I love it / I expect it / I am neutral / I can accept it / I dislike it)
- Dysfunctional question: “If the product does not have this feature, how do you feel?” (same options)
The combination of answers allows classifying each feature using the Kano classification table.
Temporal Dynamics: Features That Age
One of Kano’s most relevant observations is that categories are not static. An emotional feature today tends to become basic tomorrow as competitors adopt it and the market normalises it.
Historical examples: – GPS in smartphones started as a delighter (iPhone 2007), became performance (accuracy comparisons), and is now basic (no user mentions GPS as a purchase reason). – HTTPS on websites went from differentiator to basic in under five years.
Conclusion
The Kano model shifts the question from “what does the customer want?” to “how does the customer respond to each type of feature?” — a distinction with direct consequences for how the roadmap is prioritised. Protecting basics is the cost of entry. Improving performance features is the daily competitive battle. Finding and executing emotional features is where real differentiation lives — and the reason some products generate fans, not just users.
