Kano model

The Kano model helps teams distinguish product or service attributes that prevent dissatisfaction, improve satisfaction in proportion to performance or create unexpected delight. It focuses investment on what customers value rather than on feature volume.

When to use it

• Use the model during product discovery, service design, prioritisation and value-engineering.
• Research current or credible prospective users, and segment responses where needs differ.

Origins

Quality-management scholar Noriaki Kano published the model in 1984 after challenging the assumption that every attribute affects satisfaction in the same way. Influenced by total quality management, his work showed that fulfilment and satisfaction are not always linearly related.

What it is

The vertical dimension represents customer satisfaction; the horizontal dimension represents how fully an attribute is delivered. The principal categories are:

• Basic attributes: expected conditions whose presence is barely noticed but whose absence creates dissatisfaction. A phone lasting 24 hours or acceptable hotel temperature may become basic expectations.
• Performance attributes: satisfaction changes roughly with performance. A hotel check-in taking five minutes may be acceptable, 10 minutes disappointing and two minutes pleasing; a 10 per cent improvement may produce a corresponding 10 per cent satisfaction change.
• Excitement attributes: unexpected benefits that delight when present but do not disappoint when absent. Successful delighters are often copied and can migrate toward performance and basic status.
• Indifferent attributes: features that do not materially affect preference and may add avoidable cost.
• Reverse attributes: features whose presence reduces satisfaction for some users. Segmentation matters because one person’s convenience can be another’s complexity.

Classify an attribute by pairing questions:

• Functional: how would you feel if the attribute were present or performed well?
• Dysfunctional: how would you feel if it were absent or performed poorly?

Responses commonly use: like it, expect it, do not care, can live with it and dislike it. The pair is evaluated through Kano’s classification table. Question wording and translation should be piloted; simple averaging can obscure contradictory or questionable responses.

Developments of the model

An importance question can help prioritise attributes within the same category. Every attribute then requires at least two questions and sometimes a third, so online self-completion may reduce interviewer fatigue. Importance does not replace classification or evidence about feasibility and economics.

How to use it

Define the decision and customer segment. Generate attributes from interviews, observation, complaints, competitive research and technical possibilities. Keep each attribute specific and understandable.

For a key-location feature, ask the functional and dysfunctional questions, then ask importance on a scale from 1 to 10, where 10 is extremely important.

A legacy scoring example assigns:

• functional: –2 (Dislike), –1 (Live with), 0 (Don’t care), 2 (Expect it), 4 (Like);
• dysfunctional: –2 (Like), –1 (Expect it), 0 (Don’t care), 2 (Live with), 4 (Dislike);
• importance: 1 (Not at all important), 10 (Extremely important).

Use the established evaluation matrix rather than treating those numeric values as an interval satisfaction scale. Report category shares and confidence by segment. Revalidate over time because expectations move.

In a student-computer study, build quality might be basic, light weight a performance attribute, extended battery life an excitement attribute and warranty increasingly indifferent. A built-in camera may delight some students while being less important overall.

Excitement Performance

Built in Lightweight

camera

Battery

life

Functional

Indifferent Basics

Warranty

Build quality

2 4

Dysfunctional

Combine customer classification with cost, strategic fit, accessibility, risk and technical evidence. Remove indifferent or reverse features only after checking whether they serve a smaller segment, legal requirement or critical use case.

Some things to think about

• Use Kano to identify possible innovation and avoid over-investing in low-value features.
• Complement it with trade-off methods when customers must choose among bundles or prices.

Top practical tip

Segment the results and show category distributions, importance and uncertainty. A single average label can hide opposing customer needs.

Top pitfall

Do not infer category from one leading question or from numeric averages alone. Use paired wording, the evaluation table and a representative sample.

Further reading

• Kano, N., Seraku, N., Takahashi, F. and Tsuji, S. (nineteen eighty-four). “Attractive Quality and Must-Be Quality.” Journal of the Japanese Society for Quality Control.
• Berger, C. et al. (nineteen ninety-three). “Kano’s Methods for Understanding Customer-Defined Quality.” Center for Quality Management Journal.