Kano model: which features delight and which are taken for granted

The Kano model classifies product features by their effect on satisfaction: basic, performance, attractive, or indifferent. Learn its questionnaire and limits.

info Quick Definition
The Kano model classifies a product’s features by how they affect customer satisfaction. It separates what is taken for granted, what improves satisfaction in proportion to performance, and what delights without the customer having asked for it. It helps decide where to invest without confusing basics with differentiators.

What is the Kano model?

It was developed by Japanese professor Noriaki Kano in 1984. Wikipedia cites his article in the Journal of the Japanese Society for Quality Control, titled “Attractive quality and must-be quality”. Its core idea is that features do not all work the same way: some prevent dissatisfaction, some reduce it, and others create enthusiasm without the customer having requested them.

Wikipedia and WARC describe five categories; Cambridge IfM focuses on three (basic, performance, and attractive) and mentions an optional fourth, “enragers”, which frustrate customers whether they are missing or present. This is the five-category version:

CategoryWhat happens to satisfaction
Must-be (basic)If missing, it dissatisfies; if present, it barely adds. It is the “price of entry”.
One-dimensional (performance)Rises or falls in proportion to how well it works. It is where companies usually compete.
Attractive (delight)If present, it creates enthusiasm; if missing, it does not cause dissatisfaction.
IndifferentDoes not affect satisfaction either way.
ReverseMore functionality produces less satisfaction. WARC notes that it is rare.

Why does it matter to a designer?

Because it helps distribute effort. A designer can spend weeks polishing a delight feature while a basic one fails: the customer is left feeling the product does not work. Kano reminds you that minimum expectations come first, then performance is improved in proportion to what customers value, and only then is it worth investing in delight.

The classification also lets you speak more precisely with product and business. Saying “this feature is basic, it does not differentiate us” is more useful than saying “it is important”.

How do you apply it?

The traditional method uses a standardized questionnaire. For each feature, two questions are asked:

  • Functional: “How would you feel if the product had this feature?”
  • Dysfunctional: “How would you feel if the product did not have it?”

Answers are chosen from options such as “I like it”, “I expect it”, “I am neutral”, “I can tolerate it”, and “I dislike it”. Combining both answers gives the category in an evaluation table. Wikipedia notes that illogical combinations are usually discarded or placed in a special “questionable” category.

Wikipedia’s evaluation table gives these example answer pairs:

Functional answerDysfunctional answerCategory
I expect itI dislike itMust-be
I like itI dislike itOne-dimensional
I like itI am neutralAttractive
I am neutralI am neutralIndifferent
I dislike itI expect itReverse

Reading the table is simple: if customers expect the feature and would be bothered by its absence, it is a must-be. If they would like to have it but would not mind its absence, it is a delighter.

If you do not have time to survey people, you can use the model as a team exercise: each person classifies the features based on their judgment, and then the differences are checked against real data. Cambridge IfM presents it as a way of visualizing product characteristics and stimulating debate within the design team.

How does it change over time?

This is the part most often overlooked. An attractive feature becomes expected over time. Cambridge IfM uses the example of a cup holder in a car: today it may delight, and tomorrow it is normal. Wikipedia describes the same path: a feature can move from delighting to a performance requirement and then to a basic need.

That is why it helps to reclassify the product periodically. What is a differentiator today may, within two years, be something competitors copy and customers take for granted.

When should you NOT use it?

The model does not replace research. The categories depend on what customers answer, and attractive features are hard to anticipate: customers often do not know they need them until they see them. Nor is it a sole basis for prioritizing, because it ignores cost and technical feasibility.

Wikipedia describes its purpose as supporting product specification and discussion through a better shared understanding in the team. That is the right expectation: a tool for organizing decisions, not a formula that decides for the team.

Example

Illustrative example: a digital banking app classifies its features before a redesign. “See balance” and “transfer money” are basic: if they fail, customers leave. “Transfer response time” is a performance feature: improving it visibly raises satisfaction. “Monthly spending summary with suggestions” is attractive: few people ask for it, but those who use it recommend it. The team decides to first fix transfer stability, then speed transfers up, and only then invest in the summary. Two years from now, the summary might become expected.

Common mistakes

  • Treating everything as delight and neglecting the basics.
  • Using the model without asking customers, and classifying by intuition.
  • Forgetting that categories change over time and in the market.
  • Using it as a single ranking without considering cost or feasibility.
  • Writing confusing questions in the questionnaire, which produces illogical answers.
  • Confusing “important” with “differentiating”: a basic feature can be very important and differentiate nothing.

To organize the ideas that feed the classification, How Might We questions help frame the problem. If you want to compare your product with competitors before classifying, the competitive matrix is the natural prior step. And for deciding with data, data-driven design decisions explains how to combine information before prioritizing.

Sources

Frequently asked questions

What is the Kano model?
It is a model that classifies product features by how they affect customer satisfaction: must-be requirements, performance features, attractive features that delight, indifferent features, and reverse features.
What does it mean for a feature to be 'must-be'?
It is a minimum expectation. If it is missing, customers are dissatisfied, but if it is present it adds little satisfaction. It is what people take for granted.
How is the Kano model applied?
With a standardized questionnaire that asks two questions per feature: a functional one (how you would feel if the product had it) and a dysfunctional one (how you would feel if it did not). The combined answers indicate the category.
Does an attractive feature stay attractive?
No. It changes over time. According to Wikipedia, a feature can move from delighting to being a performance requirement and then to a basic need.