Glossary

Kano Model

Glossary

Kano Model

Introduction

Not all features matter in the same way. Some are expected so completely that their presence earns nothing and their absence causes fury; some please in proportion to how well they're done; some delight precisely because nobody expected them; and some, whatever the effort, nobody cares about. The Kano model is the framework that sorts features into those categories, using a deceptively simple pair of survey questions, and it has shaped prioritisation thinking for four decades. This article covers the categories, the questionnaire mechanics, and the model's most underrated lesson: today's delighter is tomorrow's baseline.

What is the Kano Model?

The Kano model is a framework for classifying product attributes by the relationship between how fully they're delivered and how satisfied customers are, developed by Professor Noriaki Kano and colleagues in Japan in the 1980s. Its core insight is that satisfaction is not one-dimensional: features differ not just in importance but in the shape of their effect, and a prioritisation method that treats every feature on a single "how much do you want this" scale misses the shape entirely. The model distinguishes five relationships and supplies a survey method for assigning features to them, which makes it one of the few prioritisation frameworks with an empirical instrument attached rather than a workshop and a feeling.

The Categories

Must-be (basic) attributes. Expected by default: their absence causes dissatisfaction, their presence causes nothing, because customers assume them. Security, uptime, a working login. Investment beyond adequacy is wasted; investment below it is catastrophic.

One-dimensional (performance) attributes. Satisfaction rises and falls in proportion to delivery: speed, storage, price, accuracy. The features customers can articulate and compare, and the ones competitors race on.

Attractive (delighter) attributes. Unexpected: their absence causes no dissatisfaction (nobody misses what they didn't imagine), their presence produces disproportionate delight. The source of differentiation and of most "how did we live without this" reactions.

Indifferent attributes. Present or absent, customers don't care: the features teams build because someone senior liked them.

Reverse attributes. Some customers actively prefer their absence: the automation that removes control, the personalisation that reads as surveillance. A reminder that segments can disagree on the sign, not just the size, of a feature's value.

The Questionnaire Mechanics

Each feature is assessed with a paired question: a functional form ("How would you feel if the product had X?") and a dysfunctional form ("How would you feel if it did not have X?"), each answered on a five-point scale from "I like it" through "I expect it", "I am neutral", "I can tolerate it", to "I dislike it". The combination of the two answers assigns the feature to a category through a standard evaluation table (like-it-if-present plus dislike-if-absent indicates performance; like-if-present plus neutral-if-absent indicates attractive; neutral-if-present plus dislike-if-absent indicates must-be; and so on), with each respondent's classification tallied across the sample and reported as a distribution, since a feature is rarely one category for everyone. The instrument inherits every hazard of stated-preference survey work: hypothetical questions about features people haven't used, acquiescence, and the gap between how people say they'd feel and how they feel. Pairing Kano responses with a concrete prototype or demonstration of the feature (so respondents react to something real, as in a concept test run with the feature shown on screen) markedly improves what the answers mean.

The Underrated Lesson: Decay

Kano attributes migrate over time, in one direction. Delighters become performance attributes as competitors copy them, then must-bes as they become standard: the camera phone, the cloud sync, the dark mode. The model is therefore a snapshot, and the strategic use of it is temporal: invest in delighters knowing they will decay into expectations, and audit must-bes regularly, because yesterday's differentiator is now silently mandatory and its absence is costing you customers who never mention it.

Using It Well

1. Segment the results; the same feature is a delighter to one audience and indifferent to another.
2. Show, don't describe, wherever the feature can be prototyped.
3. Combine with behavioural and willingness-to-pay evidence; Kano tells you the shape of value, not its price.
4. Repeat periodically to catch the decay.

The Takeaway

The Kano model sorts features by the shape of their satisfaction curve: must-be, performance, attractive, indifferent, reverse, assigned through paired functional and dysfunctional questions and reported as distributions across segments. Its craft is in the instrument (concrete stimuli, honest samples) and its wisdom is temporal: delight decays into expectation, and prioritisation that ignores the clock optimises for a market that has already moved.

Further reading

For the model and its survey method:

Articles:

1. The Complete Guide to the Kano Model - Folding Burritos
The definitive practitioner walkthrough: categories, questionnaire design, the evaluation table, and analysis.

2. The Kano Model: A Tool to Prioritize the Users' Wants and Desires - Interaction Design Foundation
The model in a UX context, with guidance on applying it to feature prioritisation.