You have a list of twenty features to implement in the next version of your product and a budget sufficient for four. Which ones will genuinely increase user satisfaction, and which will be taken for granted, with no one thanking you for them? The Kano model and Kano-based feature research make it possible to answer this question not on the basis of the team’s intuition, but on the basis of how customers respond to the presence and absence of each feature individually.<\/p>\n
The Kano model is a method for categorizing product features developed in the 1980s by Japanese researcher Noriaki Kano. It is based on the observation that the relationship between the presence of a given feature and user satisfaction is not linear. In other words, not every feature you add increases satisfaction to the same extent, and some do not increase it at all – they simply prevent frustration.<\/p>\n
In Kano feature research, features are organized into several categories that answer two questions at the same time: how a customer will respond when a feature is present and how they will respond when it is absent. This distinction is crucial because a standard question such as “How important is this feature to you?” does not capture the asymmetry of responses. A customer may declare that something is very important, yet the presence of that feature alone will not delight them because they consider it a market standard.<\/p>\n
The basic categories in Kano analysis are:<\/p>\n
Kano feature research makes sense when the list of potential improvements is longer than the resources available to implement them and when the team does not agree on what to implement first. If the priority map is obvious, a dedicated study may be unnecessary. Kano demonstrates its value precisely where intuition ends and disagreement over roadmap sequencing begins.<\/p>\n
The core of the method is a pair of questions asked for each feature being studied. The first is a functional question (“How would you feel if the product had this feature?”), while the second is a dysfunctional question (“How would you feel if the product did not have this feature?”). Respondents answer both versions using a scale covering five typical responses: I like it, I expect it, I am indifferent, I can accept it, I dislike it.<\/p>\n
Cross-tabulating the responses to both questions makes it possible to assign each feature to one of the Kano categories at the individual respondent level. The results are then aggregated across the full sample to determine which category dominates for a given feature. The process consists of several stages:<\/p>\n
It is worth remembering that product feature categorization does not remain constant over time. What is a delighter today becomes a must-be tomorrow when competitors make a given feature widespread. The camera in a mobile phone has gone through this entire journey – from a delightful feature to an absolute standard.<\/p>\n
As Hume’s Institute experts point out, not every feature a customer praises in a conversation deserves a place in the development budget. Kano makes it possible to separate stated enthusiasm from actual impact on satisfaction – showing what will genuinely increase user satisfaction and what users will simply consider obvious, without even noticing its presence. This distinction has direct implications for where the product team should allocate its resources.<\/p>\n
In many projects, it is useful to combine the classic Kano table with CS (Customer Satisfaction) and DS (Dissatisfaction) coefficients. The satisfaction coefficient indicates how strongly the presence of a feature increases satisfaction, while the dissatisfaction coefficient indicates how strongly its absence reduces it. Must-be features are characterized by a high absolute dissatisfaction coefficient and a low satisfaction coefficient, while delighters show the opposite pattern. This makes it possible to rank features within the same category.<\/p>\n
The most common pitfall is confusing Kano analysis with a simple feature importance ranking. An importance survey collects one stated assessment per feature and ranks features from most to least important. The problem is that users generally rate highly everything that sounds reasonable, and the method does not capture the asymmetry between must-be features and delighters. Kano feature research addresses this precisely through the pair of functional and dysfunctional questions.<\/p>\n
The most common mistakes in designing a Kano study include:<\/p>\n
The method also has natural limitations. Kano indicates which category a feature belongs to, but it does not show how much a user is willing to pay for it or how features interact with one another. When there is a trade-off between price and the feature set, conjoint analysis<\/a>, which models choices between complete product configurations, is often more precise. In practice, the two approaches often complement each other: Kano is used for the initial selection of features worth further research, while conjoint analysis is used to quantify their importance in real purchase scenarios.<\/p>\n