In 1984, Noriaki Kano, a Japanese professor, chose an unusual approach for an academic: instead of staying in the laboratory to elaborate theories, he went directly to talk to customers. This choice radically changed the way companies deal with product development.
His basic intuition is that not all the characteristics of a product generate the same satisfaction. Some, if absent, trigger strong dissatisfaction; others, if present, leave the customer indifferent; and some, defined as “attractive,” surprise the customer because he did not wait for them, stirring enthusiasm.
Toyota, Apple and Booking.com are just some of the companies that have adopted Kano’s model to guide their development choices. This model helps you focus your budget and energy on the features that really matter.
Real problem
How to decide what features of a product develop when resources are limited and customers’ expectations vary? How to avoid investing in features that do not really improve satisfaction or even can damage the experience?
Conceptual model
Kano has identified five product attributes categories:
- Must-Be (Basic Requirements): characteristics given for granted by the customer. Their absence causes dissatisfaction, their presence is considered normal. 2. **Performance (linear requirements):**the more present and performing the characteristic, the greater the satisfaction. 3. Attractive (Delight): unexpected features that generate great satisfaction if present, but do not cause dissatisfaction if absent. 4. Indifferent (Indifferent): characteristics that do not affect satisfaction. 5. Reverse (Inverses): characteristics that some customers appreciate and others loathe.
Strict formalisation
To classify a feature, Kano suggests a questionnaire with two questions for each:
- How would you feel if the product had this feature?, How would you feel if the product didn’t have this feature?
The answers, combined according to a matrix, define the category of the feature. For example, a positive response to the presence and negative to the absence indicates a Must-Be; an enthusiastic response to the presence and indifferent to the absence indicates an Attractive.
The classification matrix is:
| Functional \ Disfunctional | I like it. | I expect it. | Indifferent | I’d take it. | I don’t like it. |
|---|---|---|---|---|---|
| I like it. | Questionable | Attractive | Attractive | Attractive | Performance |
| I expect it. | Reverse | Indifferent | Indifferent | Indifferent | Must-be |
| Indifferent | Reverse | Indifferent | Indifferent | Indifferent | Must-be |
| I’d take it. | Reverse | Indifferent | Indifferent | Indifferent | Must-be |
| I don’t like it. | Reverse | Reverse | Reverse | Reverse | Questionable |
Example or case study
An Italian e-commerce of natural cosmetics applied the Kano method with a questionnaire on 300 customers. Some features planned proved to be Indifferent to the majority, while an unplanned feature, free personalized samples, was highly Attractive.
This led to a re-allocation of the budget, eliminating unnecessary investments and focusing on features that generate real value and loyalty, with a ROI of more than 600% in 18 months.
Lab / exercise
Basic level: Identify at least 5 features of your product and try to classify them according to the Kano model, based on informal customer feedback.
Intermediate Level: Build a Kano questionnaire with functional and dysfunctional questions for at least 10 features and collect at least 100 answers.
Research-grade level: Analyze the collected data by calculating the satisfaction and dissatisfaction coefficients for each feature and integrates results with priority framework such as RICE.
Datasets and recommended materials: Use Google sheets to collect and analyze data, and consult the module on fundamental metrics to deepen prioritization.
Typical error to avoid
Many Italian SMEs invest almost the entire budget on feature Performance, neglecting the Must-Be already satisfied and ignoring the Attractive. The result is a technically valid product but without differentiation and word of mouth.
Quiz or checkpoint
- What category of features generates dissatisfaction if absent but not satisfaction if present?, How do you classify the features that positively surprise the customer?, Why is it important to consider the Reverse features in the roadmap?
The kano method point teaches that the real challenge is to understand what the customer considers important, not what we think. must-be features are invisible in the survey because they are taken for granted, attractives are often unknown to the customer himself. only by digging beyond appearances and applying a rigorous method can effective development decisions be made under conditions of uncertainty.
In a competitive market, it is not enough to add functionality: you have to choose the right ones, those that create “wow” and really trust. Kano’s model offers concrete discipline for this challenge.