Planet RoadmapThe Kano model gives product teams a framework for deciding which features are worth building, because not all features create equal satisfaction. Some are expected and cause frustration only when missing. Others surprise and delight customers in ways they did not anticipate. Developed by Professor Noriaki Kano, the model maps the relationship between how well a feature is implemented and how customers feel about it, leading to smarter investment decisions.
The Five Kano Categories
The Kano Model classifies features into five categories based on how their presence or absence affects customer satisfaction.
- Must-Be: Basic expectations. Customers are dissatisfied when these are missing but not thrilled when they are present. Example: a login page that works.
- Performance: More is better. Satisfaction increases proportionally with how well these are implemented. Example: page load speed.
- Attractive: Unexpected delighters. Customers do not miss them when absent but are excited when they appear. Example: smart suggestions based on usage patterns.
- Indifferent: Features that customers do not care about either way.
- Reverse: Features that some customers actively dislike.
How to Run a Kano Model Survey
To classify features, survey customers with a pair of questions for each feature: how would you feel if this feature were present, and how would you feel if it were absent? The combination of answers places the feature into one of the five categories. You typically need at least 20 to 30 responses to see meaningful patterns.
Keep surveys short and focused. Customers lose patience with long questionnaires. Pick the ten to fifteen features you are most uncertain about and focus your analysis there.
Using Kano Results in Your Roadmap
Prioritize Must-Be features first because their absence causes active dissatisfaction. Then invest in Performance features to stay competitive. Sprinkle in Attractive features to differentiate your product and build loyalty. Avoid spending resources on Indifferent or Reverse features.
Planet Roadmap helps you collect the customer feedback needed for Kano analysis through feature request portals and feedback channels. Tag features with their Kano category to keep your roadmap grounded in customer insight.
Common Kano Model Mistakes to Avoid
The Kano model is simple to misapply. A few recurring mistakes quietly distort the results and lead teams to invest in the wrong features.
- Surveying too many features at once, which exhausts respondents and lowers the quality of every answer. Focus on the features you are genuinely unsure about.
- Treating the categories as permanent. Attractive features decay into Must-be expectations over time, so a one-time analysis goes stale.
- Ignoring the Indifferent and Reverse results. Discovering that customers do not care about a feature, or actively dislike it, is just as valuable as finding a delighter.
- Over-investing in delighters while basic Must-be needs are still broken. No amount of delight compensates for a login page that fails.
- Collecting too few responses. With fewer than 20 to 30 answers, the patterns are noise rather than signal.
Kano Model vs Other Prioritization Frameworks
The Kano model answers a different question than scoring frameworks like RICE or weighted scoring. Kano tells you how a feature affects customer satisfaction; RICE estimates effort-adjusted impact across reach, impact, confidence, and effort. The two are complementary rather than competing.
MoSCoW (Must, Should, Could, Won’t) sorts a backlog into delivery tiers for a specific release, but it relies on judgment rather than customer data. A common workflow is to run a Kano analysis to learn what customers value, then feed those insights into a MoSCoW or RICE pass to decide what actually ships this cycle. Use Kano to understand demand and the scoring methods to sequence the work.
Kano Categories Change Over Time
What delights customers today becomes an expectation tomorrow. Features that were once Attractive eventually become Must-Be as competitors adopt them and customers raise their baseline expectations. Revisit your Kano analysis periodically to ensure your roadmap reflects current customer sentiment rather than outdated assumptions.