Kano Model for Feature Prioritization: Complete Guide with

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). Use the Kano Analyzer to categorize your own features. 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:

• A hotel room having a working lock on the door
• An e-commerce site processing credit card payments securely
• A SaaS app loading in under 3 seconds
• A mobile app not crashing during normal use
• Slack delivering messages reliably without data loss

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:

• Battery life on a laptop (longer = happier)
• Storage space in a cloud product (more = happier)
• Speed of search results (faster = happier)
• Number of integrations in a SaaS tool (more = happier)
• Quality of customer support response time (faster = happier)

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:

• Spotify's "Wrapped" year-in-review feature
• Slack's custom emoji and playful loading messages
• Airbnb's guidebooks from hosts with local recommendations
• A SaaS tool automatically generating a weekly summary email
• An unexpected free upgrade on a hotel room

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:

• A settings panel with 50 configuration options that 95% of users never touch
• A feature built for an edge case that affects 0.1% of users
• Backend architectural improvements with no visible impact
• Aesthetic changes to rarely visited screens

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:

• Forced social features in a productivity app ("Share your task completion on LinkedIn!")
• Aggressive onboarding tooltips that can't be dismissed
• Auto-playing videos on a news website
• Complex "power user" features that clutter the interface for basic users
• Mandatory two-factor authentication for a low-stakes consumer app

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:

• Attractive --> One-dimensional --> Must-be: GPS navigation was once an Attractive delighter in cars. Now it's a Must-be expectation. Free Wi-Fi at hotels followed the same path.
• This migration is one-directional. Features move from Attractive to Must-be, never the other way. This means you must continuously innovate to find new Attractive features.

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:

• Proposed new features
• Existing features you're considering removing or improving
• Competitor features you're deciding whether to copy
• Concepts from user research that need validation

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:

1. I like it
2. I expect it
3. I'm neutral
4. I can tolerate it
5. I dislike it

Step 3: Build the Evaluation Table

Cross-reference the functional and dysfunctional answers to classify each response:

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:

• Randomize the order of features for each respondent
• Include 1-2 attention-check questions
• Keep the total survey under 15 minutes (8-12 features maximum)
• Segment your audience (new users vs. power users, small vs. enterprise). Kano categories often differ by segment

Step 5: Analyze Results

For each feature, calculate the percentage of responses in each Kano category:

Interpreting the results:

• Real-time collaboration is primarily One-dimensional. The better you execute it, the happier customers are. Invest in excellence here.
• AI writing assistant is primarily Attractive. It's a delighter that creates excitement. Build it, but know that it will become expected over time.
• Custom color themes is primarily Indifferent. Most customers don't care. Deprioritize or skip it.
• Offline mode is split between Must-be and One-dimensional. It's a strong expectation and execution quality matters. Prioritize it.
• Social activity feed is primarily Reverse. Customers actively don't want it. Don't build it, or make it optional.

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

Slack Feature Analysis

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 via the RICE Calculator), then One-dimensional features (ranked by RICE), then Attractive features (ranked by RICE). For a comparison of scoring approaches, see RICE vs. ICE vs. MoSCoW.

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

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:

• User role (admin vs. end user)
• Company size (SMB vs. enterprise)
• Tenure (new user vs. veteran)
• Subscription tier (free vs. paid)

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

1. Select 8-12 features you're considering for your roadmap
2. Write clear descriptions for each feature (include mockups for complex features)
3. Design your Kano survey with paired functional/dysfunctional questions
4. Pilot the survey with 5-10 people and refine
5. Distribute to 100+ users across your key segments
6. Classify each feature using the evaluation table
7. Calculate satisfaction and dissatisfaction coefficients for a nuanced view
8. Prioritize: Must-be features first, then One-dimensional, then Attractive
9. Cut Indifferent and Reverse features from your roadmap
10. Re-run annually to track category migration

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. To see how Kano compares to RICE, MoSCoW, and other scoring methods, check out our best prioritization frameworks list.

Explore More

• What Is Kano Model Analysis? - Expert answer on Kano model analysis for product feature categorization.
• What Is Opportunity Scoring and When to Use It - Expert answer on opportunity scoring for product prioritization.
• Prioritization for New Product Managers - Learn prioritization fundamentals as a new PM.
• Prioritization for Director/VP Product Managers - Director and VP-level prioritization: portfolio allocation, organizational capacity planning, and strategic investment decisions across product lines.