Kano Model: Customer-Centric Feature Prioritization
Kano Model is a customer research methodology that categorizes features based on their relationship to customer satisfaction—distinguishing between Must-be basics, Performance attributes, and Attractive delighters.
What Is It?
The Kano Model was developed by Professor Noriaki Kano in 1984 as a theory of product development and customer satisfaction. It categorizes features based on their relationship to customer satisfaction, recognizing that not all features are equal in how they affect customer perception.
The model identifies five categories of customer preferences: Must-be (Basic), One-dimensional (Performance), Attractive (Delighters), Indifferent, and Reverse. Understanding which category a feature falls into helps teams make strategic decisions about where to invest.
Kano analysis requires customer research through structured surveys, making it more rigorous but also more time-consuming than simpler methods.
Quick Reference
Core Features
- Must-be: Expected features that cause dissatisfaction if absent
- One-dimensional: Features where satisfaction scales with delivery
- Attractive: Unexpected delighters that create disproportionate satisfaction
- Indifferent: Features customers don't care about either way
- Reverse: Features some customers actively dislike
- Based on actual customer research data
- Uses structured questionnaire methodology
When to Use
- Developing new products for competitive markets
- Understanding what drives customer satisfaction (more rigorous than ICED's delight estimates)
- Identifying differentiation opportunities
- Investment decisions for mature products
- Strategic product roadmap planning
- When customer input should drive decisions (unlike team-based RICE or MoSCoW)
- Validating assumptions about customer needs
When NOT to Use
- Rapid iteration with no time for research (use RICE or MoSCoW instead)
- Internal tools where user surveys aren't feasible
- Very early stage products with no existing users
- When technical constraints override customer preferences
- Emergency fixes or critical bug resolution (use Priority Matrix)
Key Strengths
- Based on real customer data, not assumptions
- Identifies true differentiators (Attractive features)
- Prevents over-investment in expected features
- Strategic insight into competitive positioning
- Reveals features customers don't actually want
Key Weaknesses
How It Works
| 1 Primary Input | Feature list and access to customers for surveys |
|---|---|
| 2 Data You Need | Customer survey responses using Kano questionnaire format |
| 3 Primary Output | Feature categorization (Must-be, Performance, Attractive, Indifferent, Reverse) |
Comparison with Related Frameworks
Kano Model is unique in requiring customer research. Here's how it compares to team-based frameworks:
Kano vs RICE
RICE Score uses team estimates while Kano uses customer research data. Use Kano when customer insights should drive strategy, RICE when you need faster team-based prioritization with existing data.
Kano vs ICED
ICED Prioritization includes a "Delight" factor based on team estimates, while Kano's "Attractive" category is research-validated. Use Kano for rigorous customer insight, ICED for quicker delight-inclusive scoring.