The Kano Model

Ask a product team which features to build next and you'll get a long list, all marked "high priority." But features don't affect customers equally. A working checkout is expected — nobody praises it, yet its absence is a disaster. A thoughtful surprise, on the other hand, can win loyalty even though no one asked for it.

The Kano model, developed by Noriaki Kano in the 1980s, captures exactly this asymmetry. It sorts features by the relationship between how present a feature is and how satisfied customers feel — and that relationship isn't the same for every feature.

The Five Categories

Kano places each feature into one of five categories based on how its presence and absence move satisfaction.

Must-be features are the price of entry. One-dimensional features are where you compete on quality. Attractive features are where you differentiate. Indifferent features are candidates to cut, and reverse features are warnings that a "feature" may be unwanted.

The Two-Question Method

Kano's cleverness is in how it measures this. For every feature, respondents answer two questions — a functional form and a dysfunctional form.

Each is answered on a five-point scale: I like it, I expect it, I'm neutral, I can tolerate it, I dislike it. The pair of answers is what classifies the feature. Someone who "likes" a feature when present but "expects" it when absent is describing a must-be; someone who "likes" it present and is "neutral" when absent is describing a delighter.

Satisfaction Coefficients

Beyond the category, Kano yields two numbers per feature that quantify its leverage.

• Satisfaction coefficient (CS+): how much satisfaction rises when the feature is present — closer to 1 means strong upside
• Dissatisfaction coefficient (CS−): how much satisfaction falls when it's absent — closer to −1 means strong downside

A must-be feature has a strong CS− and a weak CS+; a delighter is the reverse. Plotting features on these two axes turns a wall of opinions into a map of where effort pays off.

Turning Categories into a Roadmap

Once every feature has a category and coefficients, the sequence writes itself:

1. 1Secure every must-be first — these are non-negotiable; a gap here sinks satisfaction no matter what else you ship.
2. 2Invest in the one-dimensional features where you want to win — this is where more quality directly buys more satisfaction.
3. 3Add a few attractive features to differentiate — small, well-chosen delighters create loyalty out of proportion to their cost.
4. 4Deprioritize indifferent features and review anything flagged reverse before it does harm.

Common Mistakes

• Skipping the dysfunctional question — one direction can't classify anything
• Testing too many features at once, doubling the question count and tiring respondents
• Treating Kano categories as permanent — delighters decay into must-bes as they become standard
• Reading a single respondent's answer as the verdict rather than the aggregate pattern

Kano in the SKARI Survey Lab

SKARI's Survey Lab runs the full Kano workflow: it pairs the functional and dysfunctional questions, classifies each feature, and reads the result back in plain language rather than a raw category table.

• Automatic functional/dysfunctional pairing for each feature
• Classification into must-be, one-dimensional, attractive, indifferent, and reverse
• Satisfaction coefficients (CS+ / CS−) per feature
• A verdict that flags a weak must-be, highlights the top attractive feature, and names the highest-priority candidate

Frequently Asked Questions

How many features can I test?

Because each feature needs two questions, keep it to a manageable set — often 8–15 — or respondents fatigue and the classifications get noisy.

What if a feature comes back "indifferent"?

That's a signal customers don't care — a strong candidate to deprioritize or cut, freeing effort for must-bes and delighters.

Kano or MaxDiff?

Kano classifies the type of need; MaxDiff ranks relative importance. They answer different questions and pair well together.

Key Takeaways

The Kano model replaces a flat priority list with a shape: secure the must-bes, invest in the performance features that set you apart, sprinkle in delighters, and stop spending on what customers don't notice.