# Kano Model

The Kano model studies how different product attributes influence satisfaction, from basic expectations to attractive surprises.

- Type: framework
- Domain: Data, experimentation & growth
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/kano-model/>)

## What it means

The Kano model, introduced by Noriaki Kano and colleagues, classifies product attributes by the relationship between their performance and customer satisfaction. Common categories include must-be, one-dimensional, attractive, indifferent, and reverse qualities.

## Why it matters

Not every feature creates satisfaction in the same way. Improving a basic expectation may prevent frustration without generating delight, while an unexpected capability may delight some users despite not being expected. The model helps teams interpret demand beyond simple feature voting.

## When to use it

Use the Kano model during discovery or portfolio planning when a team needs to understand how a defined customer segment perceives possible capabilities. It is most useful with structured research and should be repeated as expectations, markets, and segments change.

## How it works

1. Select a specific user segment and a manageable set of product attributes to investigate.
2. Ask paired functional and dysfunctional questions: how respondents feel if an attribute is present and if it is absent.
3. Combine each response pair with a Kano evaluation table to classify the attribute for each respondent.
4. Aggregate the classifications while retaining distributions and segment differences rather than reporting only a winning label.
5. Use the findings with feasibility, strategy, behavior, and qualitative evidence to decide what to build or improve.

## A practical example

A travel app studies live disruption alerts. Frequent commuters classify reliable delay notifications as must-be, while proactive alternative-route suggestions are often attractive. The team first fixes notification reliability, then experiments with route suggestions for commuters rather than assuming the same categories apply to occasional tourists.

## Where it breaks

Kano categories are not permanent properties of features; expectations can shift and results vary by wording, context, and segment. The questionnaire records stated reactions rather than observed behavior, and classification alone does not account for cost, accessibility, strategy, or technical risk.

## Common mistakes

- Treating an attribute’s category as universal across users and time.
- Writing vague paired questions that describe different capabilities.
- Using Kano results as a standalone roadmap rather than one source of evidence.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/kano-model/#visualization-kano-model>)

## Sources

1. [Attractive Quality and Must-Be Quality](<https://www.jstage.jst.go.jp/article/quality/14/2/14_KJ00002952366/_article/-char/en>) — Japanese Society for Quality Control · Original research paper
2. [What is the Kano Model?](<https://asq.org/quality-resources/kano-model>) — American Society for Quality · Professional institution guide

## Related topics

- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
- [Jobs to Be Done](<https://wiki.soroush.uk/topic/jobs-to-be-done/>)
- [RICE Prioritization](<https://wiki.soroush.uk/topic/rice-prioritization/>)
