Kano Model Template
Classify features by how they affect customer satisfaction. Identify basic expectations, competitive differentiators, and surprise delighters so you invest effort where it creates the most value.
Why product teams use the Kano model
Not all features are equal. A feature that meets basic expectations will never delight customers, no matter how well you build it. A delighter feature will create disproportionate satisfaction even with minimal investment. The Kano model helps you understand this asymmetry.
Most teams default to building performance features because they are easy to measure and compare. But the highest ROI often comes from identifying what is Must-Be (to avoid churn) and what is Attractive (to create word-of-mouth). The Kano model makes these distinctions visible before you commit engineering resources.
Use this template to survey your users and classify your backlog. The results will change how you allocate effort and communicate feature value to stakeholders.
Kano feature categories
Five categories that reveal how each feature affects customer satisfaction differently.
Must-Be (Basic Expectations)
Features customers expect as a baseline. Their presence does not increase satisfaction, but their absence causes strong dissatisfaction. These are table stakes. Customers will not praise you for having them but will punish you for missing them. Examples include login functionality, data security, and basic load times.
Example: "Page load time under 3 seconds. Users do not celebrate fast load times but will leave immediately if pages take 10+ seconds. This is a Must-Be quality."
Tips
- Must-Be features never create delight, only prevent frustration
- Identify by asking: what would users complain about if missing?
- Invest enough to meet expectations, not exceed them
- Must-Be features shift over time as expectations rise
One-Dimensional (Performance)
Features where satisfaction scales linearly with implementation quality. More is better, less is worse. These are the features customers actively compare when evaluating products. Better search results, faster exports, more storage. The competitive battleground.
Example: "Search result relevance. The better the search results, the happier users are. The worse they are, the more frustrated users become. Satisfaction correlates directly with quality."
Tips
- Satisfaction is proportional to feature quality
- These are the features competitors compare on
- Invest in areas where you can outperform alternatives
- Measure with direct satisfaction surveys
Attractive (Delighters)
Features that create disproportionate satisfaction when present but cause no dissatisfaction when absent. Customers do not expect them, so their presence delights. These are your differentiation opportunities. A small investment in an Attractive feature can create more satisfaction than a large investment in a One-Dimensional feature.
Example: "AI-generated summary of meeting notes after every standup. Users do not expect this and would not miss it if gone, but when they see it, they share it with their team."
Tips
- Delighters become expected over time (they decay into Must-Be)
- Small, surprising features can create outsized word-of-mouth
- Do not over-invest: delighters work because they are unexpected
- Identify by observing what makes users say "wow" in testing
Indifferent
Features that do not affect satisfaction whether present or absent. Users genuinely do not care. Building indifferent features is wasted effort. Identifying them is just as valuable as identifying Must-Be features because it tells you where not to invest.
Example: "Custom color themes for the sidebar. In surveys, users rate this the same whether the feature exists or not. Building it would consume engineering time with zero impact on retention."
Tips
- Indifferent features waste engineering resources
- Identify early through surveys to avoid building them
- What stakeholders think is important may be indifferent to users
- Re-evaluate periodically as user needs change
Reverse
Features that some users actively dislike. Their presence decreases satisfaction for a segment of your user base. Auto-playing tutorials, mandatory onboarding flows, and aggressive notification defaults often fall into this category. Reverse features are dangerous because they can drive users away.
Example: "Mandatory guided tour on every login for the first week. Power users find this patronizing and have requested a way to permanently dismiss it."
Tips
- Always provide opt-out for features that could be Reverse
- Survey different user segments separately
- Reverse features are often well-intentioned (onboarding, nudges)
- Test with both new and experienced users before shipping
Related templates
Frequently asked questions
Build features that actually matter
Vantage connects to your user data to surface which features delight and which are table stakes. Free to start.
Free to start. No credit card required.