Kano Model
Also known as: Kano Analysis, Attractive-Performance-Basic Model
The Kano Model is a framework for categorizing product or service features based on their impact on customer satisfaction. Developed by Noriaki Kano, this model distinguishes three types of features: basic (must-have) features that satisfy minimally but cause significant dissatisfaction if absent; performance features that increase satisfaction proportionally with their level; and attractive (delightful) features that exceed expectations and generate disproportionate satisfaction. By classifying features using the Kano Model, product teams prioritize development efforts, balance risk and innovation, and design experiences that delight rather than merely satisfy.
Key highlights
- Provides clear framework for feature prioritization; distinguishes high-impact from low-impact improvements.
- Captures non-linear satisfaction dynamics; explains why some features matter more than others.
- Informs strategic product decisions: where to invest limited resources for maximum satisfaction and differentiation.
- Applicable across domains: physical products, software, services.
Intuition
This section is available to Pro members. Upgrade to Pro
How it works
This section is available to Pro members. Upgrade to Pro
When to use it
Use Kano Model to prioritize product features and understand customer satisfaction drivers. Most valuable during strategy and planning phases to balance feature investment. Useful for competitive positioning (what delighters differentiate you from competitors?) and lifecycle management (as markets mature, today's delighters become basic). Do not use for detailed interaction design; combine with other methods for that.
Strengths & limitations
- Provides clear framework for feature prioritization; distinguishes high-impact from low-impact improvements.
- Captures non-linear satisfaction dynamics; explains why some features matter more than others.
- Informs strategic product decisions: where to invest limited resources for maximum satisfaction and differentiation.
- Applicable across domains: physical products, software, services.
- Classification is context- and time-dependent; a basic feature in one market may be attractive in another, and changes over product lifecycle.
- Does not address feature interaction; presence of one feature may change how customers perceive others.
- Sample size must be adequate (20–50+ participants) to identify categories; small samples produce unreliable classifications.
- Questionnaire design is critical; poorly worded questions or scales produce misleading categorizations.
Common pitfalls
This section is available to Pro members. Upgrade to Pro
Applications
This section is available to Pro members. Upgrade to Pro
Frequently asked
How do I write Kano questions to avoid leading responses?
Ask both positive and negative: 'If this feature were present, how would you feel?' and 'If this feature were absent, how would you feel?' Use consistent scales (like/expect/neutral/tolerate/dislike). Pilot test questions with small group to ensure clarity.
How many features should I evaluate in a single Kano study?
5–15 is typical. Beyond 20, fatigue reduces response quality. Prioritize strategically important features over minor ones. Run multiple focused studies if covering many features.
What if feature classifications disagree with my team's intuition?
Trust the data; customers may categorize features differently than internal teams. Disagreement is valuable: it surfaces false assumptions. Investigate: interview customers who classified differently to understand reasoning.
Sources
- 1.Kano, N., Seraku, N., Takahashi, F., & Tsjui, S. (1984). Attractive quality and must-be quality. Journal of the Japanese Society for Quality Control, 14(2), 147–156.
- 2.Cohen, L. (2007). Quality function deployment and six sigma. Pearson Education.ISBN 0-13-513338-2
You have read it. What now?
Cite this page
ScholarGate. (2026, June 3). Kano Model. ScholarGate. https://scholargate.app/human-computer-interaction/kano-model