Quick Answer (TL;DR)
The Kano Model classifies product features into five categories based on how they affect customer satisfaction: Must-be (expected baseline), One-dimensional (more is better), Attractive (unexpected delighters), Indifferent (nobody cares), and Reverse (actively disliked). Developed by Professor Noriaki Kano in the 1980s, it uses a paired-question survey to categorize features based on customer responses. The model helps product teams invest in features that genuinely matter -- and avoid wasting effort on features that don't move the needle.
What Is the Kano Model?
The Kano Model is a theory of product development and customer satisfaction created by Professor Noriaki Kano at Tokyo University of Science in 1984. It challenges the assumption that customer satisfaction is a linear function of feature completeness -- that is, the naive belief that "more features = happier customers."
Instead, Kano demonstrated that different types of features have fundamentally different relationships with customer satisfaction. Some features are invisible when present but devastating when absent. Others create no satisfaction on their own but generate disproportionate delight when added. Understanding these dynamics lets product teams allocate effort where it will have the greatest impact on customer perception and loyalty.
The Five Kano Categories
1. Must-Be (Basic Expectations)
Must-be features are baseline expectations that customers take for granted. Their presence doesn't increase satisfaction -- it simply prevents dissatisfaction. But their absence causes immediate frustration and rejection.
The relationship: Having the feature = neutral. Missing the feature = very dissatisfied.
Examples:
Product strategy implication: You must invest enough to meet Must-be expectations, but over-investing yields diminishing returns. No customer has ever said "I love this app because it doesn't crash." But they'll leave the moment it does.
2. One-Dimensional (Performance Features)
One-dimensional features have a linear relationship with customer satisfaction. The better you execute them, the happier customers are. The worse you execute them, the more dissatisfied they become.
The relationship: More/better = more satisfied. Less/worse = more dissatisfied.
Examples:
Product strategy implication: One-dimensional features are where you compete head-to-head with competitors. They're the features that show up in comparison tables and buying criteria. Invest here to differentiate, but know that competitors can match you.
3. Attractive (Delighters)
Attractive features are unexpected bonuses that customers didn't know they wanted. Their presence creates disproportionate delight, but their absence causes no dissatisfaction because customers weren't expecting them in the first place.
The relationship: Present = delighted. Absent = neutral (customers don't know to miss it).
Examples:
Product strategy implication: Attractive features create word-of-mouth, differentiate your product, and drive emotional loyalty. They're your biggest opportunity for competitive advantage because they're hard for competitors to anticipate. However, they have a shelf life -- today's delighter becomes tomorrow's expectation.
4. Indifferent
Indifferent features generate no significant satisfaction or dissatisfaction regardless of whether they're present or absent. Customers simply don't care about them.
The relationship: Present = neutral. Absent = neutral.
Examples:
Product strategy implication: Stop building Indifferent features. Every hour spent on a feature customers don't care about is an hour stolen from a feature they do. The Kano survey helps you identify these so you can ruthlessly cut them from your roadmap.
5. Reverse
Reverse features actually decrease satisfaction when present. Some customers actively dislike them. What one customer loves, another customer hates.
The relationship: Present = dissatisfied. Absent = satisfied (or neutral).
Examples:
Product strategy implication: Reverse features are dangerous because they can drive customers away. If a Kano survey reveals a feature is Reverse for a significant segment, make it optional or remove it entirely.
How the Kano Model Works Over Time
A critical insight of the Kano Model is that features migrate between categories over time:
This has direct implications for product strategy: what delighted users two years ago is now baseline. Your roadmap must include a steady stream of new Attractive features to maintain differentiation.
How to Run a Kano Survey
Step 1: Identify Features to Test
Select 8-15 features or concepts you want to categorize. These can be:
Write a clear, jargon-free description of each feature. Include a brief explanation or mockup so respondents understand what they're evaluating.
Step 2: Create the Paired Questions
For each feature, ask two questions:
Functional question (if the feature IS present):
"If [feature description], how would you feel?"
Dysfunctional question (if the feature is NOT present):
"If [feature description] were not available, how would you feel?"
Each question has five response options:
Step 3: Build the Evaluation Table
Cross-reference the functional and dysfunctional answers to classify each response:
| Dysfunctional: Like | Dysfunctional: Expect | Dysfunctional: Neutral | Dysfunctional: Tolerate | Dysfunctional: Dislike | |
|---|---|---|---|---|---|
| Functional: Like | Questionable | Attractive | Attractive | Attractive | One-dimensional |
| Functional: Expect | Reverse | Indifferent | Indifferent | Indifferent | Must-be |
| Functional: Neutral | Reverse | Indifferent | Indifferent | Indifferent | Must-be |
| Functional: Tolerate | Reverse | Indifferent | Indifferent | Indifferent | Must-be |
| Functional: Dislike | Reverse | Reverse | Reverse | Reverse | Questionable |
Reading the table: If a respondent says "I like it" for the functional question (feature present) and "I dislike it" for the dysfunctional question (feature absent), that's a One-dimensional classification. If they say "I like it" when present and "Neutral" when absent, it's Attractive.
Step 4: Survey Your Users
Sample size: Aim for 100-200 responses minimum per user segment. Kano analysis requires enough data to see clear category patterns.
Survey tips:
Step 5: Analyze Results
For each feature, calculate the percentage of responses in each Kano category:
| Feature | Must-be | One-dimensional | Attractive | Indifferent | Reverse | Questionable |
|---|---|---|---|---|---|---|
| Real-time collaboration | 12% | 45% | 28% | 10% | 3% | 2% |
| AI writing assistant | 5% | 18% | 52% | 20% | 3% | 2% |
| Custom color themes | 2% | 8% | 15% | 65% | 8% | 2% |
| Offline mode | 35% | 32% | 18% | 12% | 1% | 2% |
| Social activity feed | 3% | 5% | 10% | 35% | 42% | 5% |
Interpreting the results:
The Kano Satisfaction and Dissatisfaction Coefficients
For a more nuanced analysis, calculate these coefficients:
Satisfaction coefficient = (Attractive + One-dimensional) / (Attractive + One-dimensional + Must-be + Indifferent)
Dissatisfaction coefficient = (One-dimensional + Must-be) / (Attractive + One-dimensional + Must-be + Indifferent) x (-1)
The satisfaction coefficient ranges from 0 to 1 (higher = more satisfaction potential). The dissatisfaction coefficient ranges from -1 to 0 (closer to -1 = more dissatisfaction risk if absent).
Plot features on a grid with satisfaction coefficient on the Y-axis and dissatisfaction coefficient on the X-axis. Features in the upper-left quadrant (high satisfaction, low dissatisfaction) are Attractive. Features in the lower-right (low satisfaction, high dissatisfaction) are Must-be.
Real-World Kano Examples
Spotify Feature Analysis
| Feature | Likely Kano Category | Rationale |
|---|---|---|
| Music playback works | Must-be | Fundamental expectation -- absence = unusable |
| Sound quality options | One-dimensional | Better quality = more satisfaction |
| Discover Weekly playlist | Attractive (becoming One-dimensional) | Unexpected delight at launch, now expected |
| Spotify Wrapped | Attractive | Annual surprise that generates massive sharing |
| Social listening activity | Reverse (for many) | Many users find it invasive |
Slack Feature Analysis
| Feature | Likely Kano Category | Rationale |
|---|---|---|
| Message delivery reliability | Must-be | Non-negotiable baseline |
| Search speed and accuracy | One-dimensional | Faster/better = happier |
| Huddles (audio calls) | Attractive | Unexpected addition that reduced meeting fatigue |
| Custom emoji | Attractive | Drives culture and emotional connection |
| Enterprise Key Management | Indifferent (for SMBs) / Must-be (for enterprise) | Category depends on segment |
Common Mistakes and Pitfalls
1. Surveying Too Few People
Kano analysis with 20 responses is unreliable. You need at least 100 responses per segment to see stable patterns. With fewer, individual preferences skew results.
2. Not Segmenting Results
A feature that's Attractive for startup users might be Must-be for enterprise users. Always analyze Kano results by user segment -- company size, role, tenure, use case, or subscription tier.
3. Ignoring Category Migration Over Time
Running a Kano survey once and treating the results as permanent is a mistake. Features shift categories. Re-run the survey annually to catch migration from Attractive to One-dimensional to Must-be.
4. Poorly Written Feature Descriptions
If respondents don't understand what a feature is, their answers are meaningless. Include clear descriptions, mockups, or short videos for any feature that isn't self-explanatory.
5. Skipping the Dysfunctional Question
Some teams try to simplify by only asking the functional question. This defeats the entire purpose of Kano. The paired-question format is what makes the categorization work.
6. Over-Indexing on Attractive Features
While delighters are exciting, a product that's full of delighters but missing Must-be features will fail. Prioritization order should always be: Must-be first, then One-dimensional, then Attractive.
Combining Kano with Other Frameworks
Kano + RICE
Use Kano to classify features into categories, then use RICE to prioritize within each category. All Must-be features get built first (ranked by RICE score), then One-dimensional features (ranked by RICE), then Attractive features (ranked by RICE).
Kano + JTBD
Use JTBD interviews to identify customer jobs and underserved needs. Then use Kano surveys to categorize the features you've brainstormed to address those needs. This tells you both what to build and how customers will perceive it.
Kano + Weighted Scoring
Add a "Kano category" criterion to your weighted scoring model. Must-be features get the highest score on the "customer expectation" criterion; Attractive features get the highest on "differentiation potential."
Kano vs. Other Prioritization Methods
| Factor | Kano | RICE | MoSCoW | Weighted Scoring |
|---|---|---|---|---|
| Input required | Customer survey | Internal estimates | Team discussion | Internal criteria + scoring |
| Customer voice | Direct (survey) | Indirect (data) | Indirect (assumptions) | Indirect (criteria) |
| Output | Feature categories | Numerical scores | Priority buckets | Numerical scores |
| Time investment | High (survey design, data collection) | Medium | Low | Medium |
| Best for | Understanding customer expectations | Ranking a backlog | Release scoping | Multi-criteria ranking |
| Unique strength | Reveals what customers expect vs. what delights them | Accounts for reach and confidence | Stakeholder alignment | Flexible criteria |
Best Practices for Kano Implementation
Invest in Survey Quality
The Kano survey is only as good as your feature descriptions. Spend time crafting clear, unambiguous descriptions. Pilot the survey with 5-10 people and refine based on their confusion or feedback.
Segment Your Analysis
Always cut your Kano data by customer segment. At minimum, analyze by:
Create a Kano Feature Map
Visualize your results on a 2D plot with the satisfaction coefficient on one axis and the dissatisfaction coefficient on the other. This creates a clear visual map of where each feature falls and makes it easy to communicate findings to stakeholders.
Track Category Migration
Create a historical record of Kano classifications for your key features. Review it annually. Features migrating from Attractive to One-dimensional are becoming competitive table stakes -- you need to maintain investment. Features migrating to Must-be are non-negotiable -- any quality regression will cause churn.
Pair Kano with Qualitative Research
The Kano survey tells you what category a feature falls into, but not why. Follow up with 5-8 qualitative interviews to understand the reasoning behind the responses. Why do users see offline mode as Must-be? What makes the AI assistant feel like a delighter?
Use Kano to Say No
One of the most valuable outcomes of a Kano survey is identifying Indifferent and Reverse features. These are data-backed reasons to say no to feature requests. "Our Kano analysis shows that 65% of users are indifferent to this feature" is a much stronger argument than "I don't think we should build this."
Getting Started with the Kano Model
The Kano Model brings the voice of the customer directly into your prioritization process. It prevents the two most common product mistakes: building features nobody cares about and neglecting features everyone expects. That combination of customer insight and prioritization clarity makes Kano one of the most powerful tools in a product manager's toolkit.