Kano Model is not enough for creating Delight
What is great and less great about Kano Model
There’s certainly a benefit to generating several ideas. The question here is “How can I ensure that the solution is delightful and contributes to creating emotional connection with the users?”
Kano Model is is nice tool to think about this question. Before diving into the details of this technique, it’s important to clarify that Kano is not a prioritization method. Instead, it is a categorization technique designed to help you classify features based on their impact. By using it, you gain a clearer understanding of how each feature contributes to the overall experience, making it easier to assess their potential impact before prioritizing them effectively.
The Kano Model
The Kano model is a framework developed in the 1980s by Noriaki Kano, a Japanese professor and researcher. This framework helps categorize product features based on the impact they have on customer satisfaction. Kano created this model to help businesses understand what truly delights customers rather than just meeting their basic expectations, allowing teams to build products that drive emotional connection and loyalty.
The idea is you determine which category every solution or feature fits into based on its value proposition for your user.
Kano identified that not all features contribute to satisfaction in the same way. He separated them into five main categories.
Kano Model Categories
The five categories in the Kano model are must-have, performance, delighters, indifferent, and reverse.
Must-Have
Must-haves are features that customers expect to exist in the product. If a must-have feature is in your product, it doesn’t bring any additional satisfaction for the user. However, if a product doesn’t have a must-have feature, it causes frustration and negative emotions.
For example, if you’re staying in a hotel, you expect your room to have hot water. If your room has hot water, you’re probably not going to feel highly satisfied. However, if there’s no hot water, you can bet you’re going to say something to the front desk and write a scathing review.
Performance
The more performance features your product has, the more satisfied users are. These features impact satisfaction proportionally. The same situation happens if the feature isn’t there.
In the hotel example, you can think of the size and thickness of the mattress as a performance feature. The better the mattress is, the better the performance and the more satisfied customers are.
Delighters
Delighters are unexpected features. So if delighters are there, that presence is a pleasant surprise. Since these features aren’t expected, there’s no dissatisfaction if they aren’t there.
In the hotel example, a voucher for a spa or a cocktail in the room may be a delight. And if there’s some personalization, the satisfaction can be even higher. I remember once my family and I went to Madera and, as soon as we got into the room, we found two teddy bears, one for each of my kids. That was a nice piece of personalization because it showed they knew we had two kids traveling with us.
Indifferent
Indifferent features don’t bring satisfaction whether they’re there or they aren't. Sometimes indifferent features have to be there because they’re related to the technical performance of the product, but it’s not necessarily related to satisfaction.
In the hotel example, a rug on the floor may be something that doesn’t necessarily make any change in the satisfaction of the users.
Reverse
The more reverse features that are in your product, the more dissatisfaction they cause. These are features that have to happen due to security, legal, or financial reasons. It’s important to remember that reverse features aren’t necessarily bad, but you should know why you’re implementing a feature you’ve categorized as reverse.
For example, consider ads in Chrome, or any other browser; most people don’t like ads. In fact, the more ads you introduce into a product, the more user satisfaction declines. This is an example of a “reverse feature”.
Choosing Among the Different Categories
Every time I talk about the Kano model, people ask me “Should we always prioritize must-haves over performance features and delighters?” My answer? Not always.
Of course, a product exists because of its must-have features, they’re nonnegotiable. However, the risk of focusing only on must-haves is that you end up with a backlog filled with purely functional improvements, making the product feel utilitarian and devoid of emotional connection.
The best product backlogs strike a balance between all categories. A great example? McDonald’s Happy Meal.
The Must-Have: The food, without it, there’s no product.
The Performance Factors: The quality and quantity of the food.
The Delight: The playful packaging, the toys, and the books.
Sure, McDonald’s could have prioritized better food quality or larger portions to improve performance. But instead, they invested in delight, offering a fun and large variety of gifts, creative designs, and an engaging experience. Why? Because for Happy Meal users, delight is the real driver of choice.
This is why balancing must-haves, performance, and delight is crucial.
Limitations and Risks of the Kano Model
The Kano model is a powerful tool for categorizing features based on their impact on user satisfaction. While it identifies which features can surprise and excite users, it doesn’t delve deeply into the nuances of emotional connection.
Limited Depth of Delight
One of the key limitations of the Kano model is that it doesn’t account for the varying depths of delight. Not all delightful experiences are the same; some may create momentary joy, while others foster long-term emotional attachment.
For example, a fun animation in a user interface (UI) may generate a quick smile, but a thoughtfully personalized onboarding experience can create a much deeper, lasting connection. The Kano model doesn’t differentiate between surface delight and deep delight.
Overlooks Emotional Motivators
While the Kano model categorizes features based on their functional impact on satisfaction, it lacks emphasis on why certain features create delight. True delight often stems from emotional motivators, whether personal (e.g., feeling accomplished, valued, or understood) or social (e.g., feeling connected, admired, or included).
For example, Spotify Wrapped is delightful not just because it’s unexpected, but because it taps into personal nostalgia and social validation. People love sharing their music taste and seeing their listening history reflected back to them. The Kano model doesn’t provide a way to connect between the product category and these deeper emotional triggers.
Beyond Kano: A More Holistic Approach to Delight
While the Kano model is a great framework, product teams looking to create truly standout experiences need to go further. By integrating emotional motivators and exploring deeper levels of delight, they can move beyond just identifying delightful features to intentionally creating products that users love, remember, and keep coming back to.
How can we avoid the trap of only delivering aesthetic delight and instead maximize features that trigger an emotional connection between the product and the users?
The Delight Grid helps your product team strike the perfect balance between functionality and emotion. When you categorize solutions into Low Delight, Surface Delight, and Deep Delight, you increase your chance of creating solutions that not only solve user problems but also elevate the experience.
Get the full blog about Delight Grid here.
All you need to know to apply the delight model is in Product Delight book. You can sign up Now.