Kano Model
Classify your features by their real impact on customer satisfaction. The Kano Model reveals what delights, what is expected and what leaves people indifferent.
Description
The Kano Model is an analytical framework developed in 1984 by Noriaki Kano (Tokyo University of Science) that classifies product attributes into five categories (Must-be, Performance, Attractive, Indifferent, Reverse) based on their asymmetric impact on customer satisfaction. Its purpose: reveal that not all features are created equal, and that some create disproportionate value where others are simply expected. Most product teams treat their backlog as a flat list where every feature has the same status. The Kano Model shatters this illusion by demonstrating that satisfaction and dissatisfaction are not symmetric opposites. A "Must-be" feature (basic quality) generates no satisfaction when present but causes massive dissatisfaction when missing. Like electricity in a hotel: nobody leaves a five-star review because the lights work, but everyone complains if the power goes out. Conversely, an "Attractive" feature creates an unexpected "Wow" effect without its absence being noticed. Noriaki Kano drew inspiration from Frederick Herzberg's two-factor theory (1959), which distinguished motivation factors from hygiene factors in job satisfaction, to transpose this asymmetry to the domain of product quality. The Kano method relies on a structured questionnaire composed of functional and dysfunctional question pairs whose cross-referencing in an evaluation table determines each feature's category. The resulting Kano diagram gives decision-makers a clear map: invest heavily in Attractive attributes to differentiate, guarantee Must-be attributes to prevent attrition, and measure Performance attributes to stay competitive. An often-overlooked phenomenon completes the analysis: the temporal degradation of categories, where a feature that is Attractive today migrates toward Must-be over time as the market normalizes it.
Objectives
- Prioritize features
- Understand users
- Ensure strategic alignment
Used by
- -Toyota (integration of the Kano model into its product quality processes, in continuity with the Toyota Production System)
- -Apple (uses attractive quality principles to design "Wow" features that define new product categories)
- -Amazon (applies Kano analysis to prioritize features for its AWS services and e-commerce experience)
Advantages
- Reveals asymmetric feature impact. You discover that some highly requested features won't increase satisfaction (Indifferent), while other unrequested ones will create the "Wow" effect (Attractive).
- Prioritization based on customer perception, not internal intuition. The Kano questionnaire provides empirical data, not meeting room opinions.
- Competitive differentiation. By identifying your Attractive features, you invest where your competitors are not looking yet.
- Common language between product, design and business. The Must-be, Performance, Attractive categories are understandable by all stakeholders without technical training.
Limitations
- The questionnaire can seem strange to respondents. The functional/dysfunctional format is unusual and can generate inconsistent answers if poorly explained.
- Does not capture technical feasibility. The Kano model measures user-side desirability but completely ignores development effort. Combine it with a framework like RICE or ICE for effort estimation.
- Categories degrade over time. An Attractive feature migrates to Must-be when the market normalizes it, requiring regular re-analysis.
- Minimum sample required. With fewer than 30 respondents, results are statistically fragile. If your user base is small, qualitative interviews will be more reliable.
How to apply Kano Model
- 1
Identify the features to evaluate
List 10-20 candidate features from your backlog, customer requests, or competitive benchmarking. Mix existing features with new ideas. Too many features make the questionnaire exhausting for respondents. Output: a prioritized list of 10-20 features to test.
- 2
Build the Kano questionnaire
For each feature, write two questions. The functional question: "If this feature is present, how do you feel?" The dysfunctional question: "If this feature is absent, how do you feel?" Answers follow a 5-point scale: I like it, I expect it, I am neutral, I can tolerate it, I dislike it. Output: a questionnaire with 2 questions per feature.
- 3
Distribute the questionnaire to your users
Send the questionnaire to 30-100 users representative of your target segments. The larger the sample, the more reliable the results. Use a survey tool (Typeform, Google Forms, SurveyMonkey) or integrate the questions into your user interviews. Output: responses collected from a representative sample.
- 4
Classify responses in the Kano evaluation table
For each feature and each respondent, cross-reference the functional response (row) with the dysfunctional response (column) in Kano's 5x5 matrix. The intersection yields a category: A (Attractive), O (One-dimensional/Performance), M (Must-be), I (Indifferent), R (Reverse), or Q (Questionable). Output: each feature classified by dominant category.
- 5
Calculate satisfaction and dissatisfaction coefficients
For each feature, calculate the satisfaction coefficient (percentage A+O over total) and the dissatisfaction coefficient (percentage O+M over total, as a negative value). These coefficients quantify each feature's satisfaction potential and dissatisfaction risk. Output: a table with both coefficients per feature.
- 6
Plot the Kano diagram
Place each feature on a chart with the satisfaction coefficient on the y-axis and the dissatisfaction coefficient on the x-axis. Features in the upper left are your "Wow features" (Attractive). Those in the lower right are your "Must-haves" (Must-be). Those in the center are linear Performance features. Output: a visual diagram showing the distribution of your features.
- 7
Prioritize your roadmap based on categories
Apply the Kano prioritization rule: first the Must-be (eliminate dissatisfaction), then Performance (stay competitive), and finally Attractive (differentiate). Ignore Indifferent and eliminate Reverse. A product that neglects its Must-be features to invest in Attractive ones is building on sand. Output: roadmap prioritized by Kano category with justifications.
- 8
Reassess every 6-12 months
Kano categories are not fixed. What delighted your users a year ago may have become a prerequisite today. GPS on smartphones was Attractive in 2008; it has been Must-be since 2015. Re-run the questionnaire regularly to detect these migrations. Output: comparative analysis of categories over time.