What is Kano Model?
A customer satisfaction framework that categorises product features as Must-Be, Performance, or Attractive based on functional and dysfunctional survey responses.
The Kano Model is a customer satisfaction framework developed by Professor Noriaki Kano that categorises product features based on how they affect satisfaction relative to their level of implementation. Features fall into five categories: Must-Be (expected basics), Performance (linear satisfaction), Attractive (delighters), Indifferent (no effect), and Reverse (actively disliked by some users). The model challenges the assumption that more features always equal more satisfaction.
Formula
Categorised via paired functional/dysfunctional survey questions per featureFor each feature, ask two questions: (1) Functional: "How do you feel if this feature IS present?" (2) Dysfunctional: "How do you feel if this feature is NOT present?" Response options: I like it / I expect it / I am neutral / I can tolerate it / I dislike it. Cross-reference answers in the Kano evaluation table to assign each feature to a category. Satisfaction coefficient and dissatisfaction coefficient can be calculated to quantify impact.
Industry Benchmarks
- Must-Be features: absence causes strong dissatisfaction, presence is taken for granted
- Performance features: each improvement linearly increases satisfaction (speed, storage)
- Attractive features: unexpected delighters that create disproportionate satisfaction when present
- Indifferent features: no impact on satisfaction whether present or absent - candidates for removal
- Features shift categories over time: yesterday's Attractive becomes tomorrow's Must-Be
When to Use Kano Model
- Feature prioritization for a major product release to distinguish table-stakes from differentiators
- Evaluating a feature backlog to identify Indifferent items that should be removed to reduce complexity
- Competitive positioning: understanding which Attractive features from competitors are becoming Must-Be expectations
- Designing user research to reveal hidden needs (Attractive features) before competitors discover them
- Running Kano surveys with too small a sample - you need at least 30 responses per segment for reliable category assignments
- Treating Kano categories as permanent when they evolve as markets mature and expectations rise
- Using Kano in isolation without combining it with RICE or ICE to estimate implementation effort
- Run Kano analysis by customer segment separately - an Attractive feature for enterprise users might be a Must-Be for SMB users
- Focus roadmap investment on Attractive features that competitors have not yet replicated for maximum differentiation
- Schedule a Kano re-survey annually to track how feature expectations evolve in your market
Related Terms
Free Kano Model Calculator
Skip the spreadsheet. Enter your numbers in the free Kano Calculator and get a benchmarked Kano Model result in seconds.