The Kano model classifies features into five categories based on how their presence or absence affects customer satisfaction. It helps you decide which features to build, which to perfect, and which to skip entirely.
The Five Categories
Must-be (Basic): Customers expect these. Having them does not delight anyone, but missing them causes frustration. Example: a login page that works. You cannot skip these, but do not over-invest either.
One-dimensional (Performance): More is better in a linear way. Faster load times, more storage, better uptime. Customers explicitly ask for these. Investment here produces proportional satisfaction gains.
Attractive (Delighters): Customers do not expect these, but they create outsized satisfaction when present. They are your competitive differentiation. Example: Slack's custom emoji reactions when they launched. Nobody asked for it, but everyone loved it.
Indifferent: Customers do not care either way. Building these wastes engineering time. Your backlog probably has more indifferent features than you think.
Reverse: Features that actually decrease satisfaction for some users. Aggressive upsell modals and notification spam fall here.
How to Run a Kano Survey
For each feature, ask two questions: "How would you feel if this feature existed?" and "How would you feel if this feature did not exist?" Both use a 5-point scale from "I'd like that" to "I'd dislike that." Cross-reference the answers on a Kano evaluation table to classify the feature.
You need 30-50 responses per customer segment for reliable classification. Keep the survey under 15 features or respondents will bail.
Using Kano with Scoring Frameworks
Kano tells you what type of value a feature creates, but not how to rank features within each category. Pair it with RICE scoring or weighted scoring for a complete prioritization system. Use Kano categories as a filter: must-be features go in the current release regardless of RICE score. Delighters compete on RICE for the remaining capacity.
The prioritization guide explains how to combine qualitative frameworks like Kano with quantitative scoring.
Common Mistakes
Categories shift over time. What was a delighter last year becomes a must-be this year. Mobile apps were a delighter in 2010 and a must-be by 2015. Re-run your Kano analysis annually.
Another mistake: surveying only power users. They skew toward performance features because they already have the basics handled. New users and churned users reveal must-be gaps. Check the NPS Calculator to segment satisfaction data by user cohort before designing your survey.
For comparing Kano against other prioritization approaches, the RICE vs ICE vs MoSCoW comparison covers the tradeoffs.