What Is the Kano Model? How to Categorize Features by User Satisfaction
The Kano Model is a theory of customer satisfaction developed by Professor Noriaki Kano in the 1980s that classifies product features into categories based on their relationship to user satisfaction and their presence or absence in the product. It provides a framework for understanding that not all features create equal customer value — that some features can delight customers when present but barely register when absent, while others can dissatisfy customers when missing but produce no positive response when they’re there.
The Kano Model is widely used in product management to prioritize features based on their satisfaction potential, set realistic expectations about which features will drive delight vs. merely avoid dissatisfaction, and identify where innovation can create the most customer impact.
The Five Kano Categories
Basic Needs (Must-Be Quality)
Features customers expect without asking for them. When present, they don’t create satisfaction — they’re simply expected. When absent, they create strong dissatisfaction. These are the hygiene factors of the product.
Example: A mobile banking app must show current account balance. Users won’t be impressed that it does; they’ll be furious if it doesn’t.
Strategic implication: Invest sufficiently to meet basic needs reliably. No amount of investment beyond this creates competitive advantage, but failing to meet these needs is disqualifying.
Performance Needs (One-Dimensional Quality)
Features where more is better and less is worse — there’s a linear relationship between the feature’s performance and customer satisfaction. Users will appreciate better performance and notice degraded performance.
Example: App load time. Users are more satisfied with faster performance and less satisfied with slower performance, with no threshold where it stops mattering.
Strategic implication: Continuous investment in performance needs creates proportional satisfaction improvement. These are often the features that competitive differentiation hinges on.
Excitement Needs (Attractive Quality / Delighters)
Features that create strong positive satisfaction when present but whose absence doesn’t create dissatisfaction — because users weren’t expecting them. These are the surprise-and-delight features.
Example: A travel app that automatically detects that a flight was cancelled and proactively suggests alternative connections before the user knows to look.
Strategic implication: Delighters create disproportionate positive impact when discovered. They’re also the most time-sensitive category: today’s delighter often becomes tomorrow’s basic expectation as competitors copy it.
Indifferent Quality
Features that don’t move the needle on satisfaction in either direction — present or absent, users don’t care.
Strategic implication: Don’t invest here. Resources spent on features that don’t affect satisfaction are wasted.
Reverse Quality
Features that actively decrease satisfaction when present. Some users don’t want certain features and are made worse off when they’re present.
Strategic implication: Identify these and either make them optional or don’t build them.
How to Apply the Kano Model
Kano Surveys
The formal Kano technique uses paired questions for each feature: one asking how the user would feel if the feature were present (“How would you feel if the product had X?”) and one asking how they’d feel if absent (“How would you feel if the product didn’t have X?”). Respondents choose from: I like it, I expect it, I’m neutral, I can tolerate it, I dislike it.
Combining the two responses into a Kano category matrix assigns each response pair to basic, performance, excitement, indifferent, or reverse.
Using Kano Without Formal Surveys
Even without formal Kano surveys, the framework’s categories provide a useful lens for product conversations:
- “Is this a basic expectation or a potential delighter?”
- “If we don’t have this feature, will users be dissatisfied or just unimpressed?”
- “Is this a feature users expect us to have, or one that would surprise them positively?”
The Time Dimension of Kano Categories
One of the most important insights from the Kano Model is that features migrate over time. Today’s delighter becomes tomorrow’s performance need and eventually becomes a basic expectation. The iPhone’s touch screen was a delighter in 2007; today it’s a basic need in every smartphone. This migration means that maintaining competitive advantage requires continuously identifying new delighters — investment in excitement needs today becomes tomorrow’s table stakes.
Key Takeaways
The Kano Model provides a sophisticated framework for understanding that customer satisfaction is not a simple function of having features. By distinguishing between features that prevent dissatisfaction, features that create proportional satisfaction improvement, and features that create disproportionate delight, it enables product teams to make more strategically intelligent investment decisions — focusing energy on the features that will have the most meaningful impact on customer perception rather than optimizing uniformly across all features.