Kano Model
The Kano model is a framework for classifying product features by how they affect customer satisfaction. Developed by Professor Noriaki Kano and colleagues and published in 1984, it shows that some features only prevent dissatisfaction, some raise satisfaction in proportion to how well they perform, and others delight customers who did not expect them at all.
How the Kano Model Works
Kano's original paper, "Attractive quality and must-be quality," describes five categories of quality attributes:
- Must-be (basic): expected features. Their absence causes strong dissatisfaction, but delivering them well earns no extra credit.
- One-dimensional (performance): satisfaction rises and falls in line with how well the feature performs. More is better.
- Attractive (delighters): unexpected features that create satisfaction when present but cause no dissatisfaction when absent.
- Indifferent: features customers do not care about either way.
- Reverse: features that some customers actively prefer not to have.
To place a feature in a category, the Kano method uses a paired questionnaire. Each respondent answers a functional question ("How would you feel if the product had this feature?") and a dysfunctional question ("How would you feel if it did not?"), choosing from answers such as "I like it," "I expect it," "I am neutral," "I can tolerate it" and "I dislike it." The combination of the two answers maps to a category. For example, liking the feature when present and disliking its absence indicates a one-dimensional feature.
Categories are not permanent. As competitors catch up and expectations rise, today's delighters tend to become performance features and eventually basics.
Why the Kano Model Matters
The Kano model reminds teams that not all features move satisfaction in the same way. That shapes priorities in a specific order: secure the must-be features first, because no amount of delight compensates for missing basics; invest in the performance features customers compare products on; then add a few attractive features to stand out. It also flags indifferent features that consume effort without changing how customers feel.
The model's limits are practical. A proper Kano study needs a well-designed survey and enough respondents, and different customer segments can classify the same feature differently, so results should be read per segment. It explains how features affect satisfaction, not how much they cost to build, so it is usually combined with an effort-based method.
Kano Model Example
A team building a video-calling app runs a Kano survey with small-business users:
- A stable connection and clear audio are must-be features. Nobody praises them, but failures drive users away.
- Video resolution is one-dimensional: the sharper, the happier users are.
- Automatic meeting summaries are attractive for now, though the team expects them to become a basic expectation as competitors add them.
- Custom background music while waiting is indifferent, so it is dropped from the roadmap.
Kano Model vs. Opportunity Scoring
Both rely on customer surveys. The Kano model classifies specific features by their effect on satisfaction. Opportunity scoring ranks underlying customer needs by importance and current satisfaction, before any feature is chosen. Kano results are a useful input to product differentiation, since attractive features are often where a product can stand apart, and to ongoing user research.