Ask customers how they feel when a feature is present and how they feel when it is absent. Pair the two responses to classify the feature, then combine that evidence with strategy, cost, and segment importance.
- Ask both the functional and dysfunctional question for each feature.
- Analyze meaningful customer segments separately before combining results.
- Expect delighters to become expected basics as products and markets mature.
What the Kano categories mean
Basic needs cause dissatisfaction when absent but add little delight when present. Performance needs produce more satisfaction as performance improves. Delighters create satisfaction when present but little dissatisfaction when absent. Indifferent features have little effect, while reverse features are preferred by some customers when absent.
| Feature | Likely category | Product implication |
|---|---|---|
| Reliable autosave | Basic | Fund it as product hygiene; do not expect it to differentiate. |
| Faster search | Performance | More speed should improve satisfaction. |
| Automatic meeting recap | Delighter | Test whether delight converts into repeat use. |
| Animated workspace themes | Indifferent | Do not prioritize without evidence from a target segment. |
How to ask Kano questions
For each feature, ask a functional question such as, “How would you feel if Relay automatically summarized a meeting?” Then ask the dysfunctional version: “How would you feel if Relay did not automatically summarize a meeting?” Use the standard response choices: I like it, I expect it, I am neutral, I can tolerate it, and I dislike it.
Do not ask whether the respondent wants the feature. That produces stated preference, not the asymmetric satisfaction pattern the model is designed to reveal.
Use Kano evidence in a roadmap decision
Kano identifies the kind of customer response a feature may create. It does not account for effort, revenue, strategic fit, or technical risk. Use the result as one criterion in a broader decision. A basic need may deserve priority even though it will never win an excitement vote.
Common mistakes
- Assigning categories in a workshop without asking customers.
- Combining segments that have different expectations and workflows.
- Assuming every delighter should be built regardless of effort or strategy.
- Treating categories as permanent rather than time-sensitive evidence.
Check your understanding
Customers dislike a feature being absent but feel merely neutral when it is present. Which category best fits?
A basic need. Its absence creates dissatisfaction, while its presence is simply expected.
Sources
- Kano et al.: Attractive Quality and Must-Be QualityThe original 1984 paper describing attractive and must-be quality.