Kano Model: Must-Haves, Performance or Wow?
In an economic environment where offerings are becoming increasingly easy to compare, competitive pressure is rising. As a result, customer satisfaction is gaining strategic importance for companies. It influences not only how an offering is perceived in the moment, but also whether customers remain loyal, speak positively about a brand and choose the same company again in the future. This makes it all the more important to understand which features primarily prevent dissatisfaction, which actively increase satisfaction and which can create genuine delight.
A look at the hotel industry makes this logic easy to understand: a working shower, a clean room or a smooth check-in are simply expected by guests. If these features are missing, dissatisfaction arises immediately; if they are fulfilled well, however, they hardly create delight. Features such as location, breakfast quality or the friendliness of the service work differently: here, satisfaction generally increases with perceived quality. The better these features are, the more positively the stay is rated. Then there are details that go beyond what is expected: a small upgrade, a personal welcome note or particularly attentive service. Such features can noticeably enhance a stay and remain memorable. The Kano Model helps to systematically understand these different effects.
Where does the model come from?
The Kano Model goes back to the Japanese quality researcher Noriaki Kano, who published it in 1984 together with Nobuhiko Seraku, Fumio Takahashi and Shin-ichi Tsuji in the paper Attractive Quality and Must-Be Quality. What makes the model particularly interesting is that Kano turned conventional quality thinking on its head. Quality was no longer understood merely as being “as error-free as possible”, but as something that has very different effects depending on customers’ expectations. One and the same feature can therefore be taken for granted, directly compared with alternatives or perceived as surprisingly delightful. It is precisely this shift in perspective that makes the model so useful to this day for product development, service design and brand management.
How the Kano Model works
The Kano Model shows how differently individual features affect customer satisfaction. The x-axis shows the extent to which expectations regarding a feature are fulfilled or not fulfilled; the y-axis shows the resulting dissatisfaction or satisfaction. Depending on the type of feature, three different relationships emerge: must-be features, performance features and delighters.
Must-be features are taken for granted by customers. If they are not fulfilled, dissatisfaction quickly arises. Improvements have the strongest effect when a previously insufficient must-be feature is brought up to an acceptable level, but this effect levels off as expectations are increasingly fulfilled. Once must-be features are met, they are usually not perceived as particularly positive; their main contribution lies in preventing dissatisfaction.
Performance features follow a linear logic: the better they fulfil customers’ expectations, the higher satisfaction tends to be. Satisfaction therefore increases approximately in proportion to the degree of expectation fulfilment. Conversely, it decreases when performance falls short of expectations. Unlike must-be features, performance features do not become relevant only when they are missing; they are evaluated across their entire range of performance. They are therefore the area in which quality and perceived benefit have a particularly direct impact on satisfaction.
Delighters are not taken for granted by customers. If they are not fulfilled or are missing entirely, this usually does not lead to dissatisfaction. If they are present, however, they can increase satisfaction disproportionately. Unlike must-be and performance features, they do not primarily work by fulfilling an expectation, but through positive surprise. This is precisely where their potential lies: they can make a product particularly attractive in direct comparison and create a noticeable differentiation effect.
.png)
What this means in practice
- First, secure the must-be features
Before thinking about differentiation, you need to clarify which features the market simply expects today. In a hotel context, these are primarily the basics that must work smoothly during the stay: a clean room, a functioning shower, a comfortable bed, an uncomplicated check-in and an overall reliable standard of hygiene and comfort. If these features are missing, dissatisfaction arises immediately. If they are fulfilled, however, they hardly create additional satisfaction, because guests expect them as a matter of course.
- Then prioritise the performance features
The next step is to deliberately strengthen those features where guests directly notice and compare differences between offerings. In a hotel context, this includes aspects such as location, breakfast quality, the friendliness and attentiveness of the service, the size and equipment of the rooms, or the quality of shared areas such as the lobby. Unlike with must-be features, the aim here is not merely to meet expectations, but to meet them better than competing offerings. Where exactly guests experience differences often only becomes visible through structured observation, for example through an activity study. For a hotel, this means focusing on those performance features that are particularly relevant to the target group and where a difference is actually noticeable to guests. Anyone who is merely average everywhere remains interchangeable. Those who clearly stand out in selected areas, on the other hand, create relevance in direct comparison.
- Use delighters selectively
Only once the basics are in place and the relevant performance features are convincing can delighters unfold their full value. In a hotel context, these are the aspects that are not necessarily expected, but can shape a stay in a particularly positive way. This might be a small upgrade, a personal welcome note, exceptionally attentive service or an unexpected detail that makes the stay more individual and pleasant. What matters is not offering as many extras as possible, but deliberately creating those features that positively surprise guests and fit the profile of the hotel. They give the stay a special touch, remain memorable and lift a hotel out of direct comparability.
How is the Kano Model applied in market research?
Whether a feature delights, is expected or is simply irrelevant is not decided by the company, but by the market. And this market is dynamic: expectations change, and target groups differ. What delights one group may leave another cold or even put them off. This is exactly why market research is needed. In the Kano Model, consumers are asked two standard questions for each feature: one functional and one dysfunctional question.
- How would you react if the feature were present?
- How would you react if the feature were not present?
Both questions are answered using the same five response options: from “I would be delighted” to “I expect that”, “I am indifferent”, “I could accept that” and “I would be bothered by that”.
Only the combination of both answers shows how a feature should be classified. In addition to must-be features, performance features and delighters, indifferent features may also become visible (features that have little influence on perception), as well as reverse features (meaning features that are evaluated negatively by customers).
.png)
The Kano Model is therefore not a one-off exercise. Those who listen systematically, for example through a continuously maintained customer panel, recognise earlier where minimum standards are emerging, where performance is being compared and where genuine delight is possible. Especially in dynamic markets, this is a decisive advantage. Expectations shift, markets evolve, and what delights today may already be a basic requirement tomorrow. Companies that recognise these changes early create a better foundation for developing their offerings in a targeted way and for not leaving customer satisfaction to chance.
Where the Kano Model reaches its limits
When applying the model, it is worth keeping three points in mind. First, the result depends strongly on how a feature is described in the survey: the same function can be classified differently depending on the wording. Second, the questionnaire quickly becomes long because each feature requires two questions, which tests respondents’ patience. Third, the model shows the effect of a feature, but not the effort and cost of implementing it. The classification is therefore a starting point for prioritisation, not the final decision.
For companies, the real value therefore lies not only in the Kano classification itself, but in translating it into clear priorities. Flybridge supports this process: from the precise formulation of features and the appropriate survey logic through to the interpretation of the results. In this way, the model becomes a basis for decision-making: what needs to work reliably, where differentiation is worthwhile and which details can create genuine delight.
One of the strengths of the Kano Model is that it does not stop at products and services. Jobs can also be viewed through this lens: which features are now taken for granted, which are actively compared and which can truly delight employees? Anyone looking to promote employee satisfaction will also find the Kano Model an exciting approach for HR. 💡
The Kano Model provides the direction, the market provides the answer, and Flybridge turns both into strategy. 🧭
Kano Model: the most important questions answered briefly
What is the Kano Model? The Kano Model is a market research tool that describes how different product or service features affect customer satisfaction. It was developed in the 1980s by the Japanese quality researcher Noriaki Kano. The model distinguishes between features according to whether they prevent dissatisfaction, increase satisfaction or create genuine delight.
Which feature types does the Kano Model distinguish between? The Kano Model distinguishes between three central types: must-be features are expected and primarily prevent dissatisfaction; performance features increase satisfaction approximately in proportion to fulfilment; and delighters create disproportionate satisfaction through positive surprise. In addition, there are indifferent features with no noticeable effect and reverse features that are evaluated negatively.
An example makes this tangible. Imagine a hotel asks its guests about Wi-Fi. To the functional question “How would you react if Wi-Fi were available?”, most answer “I expect that.” To the dysfunctional question “How would you react if Wi-Fi were not available?”, they answer “I would be very bothered by that.” Expected when present and annoying when absent: this pattern characterises a must-be feature.
It is different with a personal welcome note. If it is there, guests are pleased; if it is missing, they do not mind. Pleasure when fulfilled and no annoyance when absent: this is what a delighter looks like.
How is the Kano Model assessed in practice? For each feature, customers are asked two questions: a functional question “How would you react if the feature were present?” and a dysfunctional question “How would you react if it were not present?” Only the combination of both answers shows whether a feature acts as a must-be feature, a performance feature or a delighter.
Why does the classification of features change overtime? Customer expectations are dynamic. What delights today can become tomorrow’s basic requirement as markets evolve and standards shift. For this reason, the Kano Model is not a one-off exercise, but should be repeated regularly.
Can the Kano Model also be applied beyond products? Yes. The logic of must-be features, performance features and delighters can also be transferred to other areas, such as employer attractiveness. In HR, the model helps identify which aspects of a job are taken for granted, which are actively compared and which can truly delight employees.
Source
Kano,N., Seraku, N., Takahashi, F., & Tsuji, S. (1984). Attractive quality and must-be quality. Journal of the Japanese Society for Quality Control, 14(2), 39–48.
