The Kano Model is a framework used to prioritize product features based on how they affect customer satisfaction. It was developed by Noriaki Kano in the 1980s.
Business analysts, product managers, and UX teams use it to decide which features to build first.
Core Idea
Not all features increase satisfaction equally.
Some features:
must exist (customers expect them)
increase satisfaction proportionally
delight customers unexpectedly
The Kano Model classifies features into five categories.
---
1. Must-Have (Basic Needs)
Features customers expect by default.
If missing → customers are very unhappy
If present → customers are neutral
Examples:
Banking app: login security
E-commerce: payment processing
Car: brakes
Even if you improve them, customers usually won’t praise you because they assume they should exist.
Example:
> If a mobile banking app does not allow login → users uninstall immediately.
---
2. Performance Needs (Linear Features)
These features have a direct relationship with satisfaction.
More performance → more satisfaction.
Examples:
Internet speed
Battery life
Price vs quality
Delivery speed in Amazon
Example:
> Faster delivery → happier customers.
---
3. Delighters (Excitement Needs)
Features customers do not expect.
If absent → no dissatisfaction
If present → huge satisfaction
Examples:
Amazon same-day delivery
Google Photos automatic AI album creation
Tesla self-driving features
These create competitive differentiation.
---
4. Indifferent Features
Customers do not care whether these features exist or not.
Examples:
Minor UI color changes
Rarely used settings
Extra customization nobody asked for
Building these wastes time and engineering resources.
---
5. Reverse Features
Some features annoy certain users.
Example:
Autoplay videos
Forced notifications
Over-complex UI
These can actually reduce satisfaction.
---
Kano Model Diagram (Concept)
Customer satisfaction vs feature implementation:
Customer Satisfaction
^
| Delighters
| /
| /
| /
|------/----------- Performance
| /
| /
| /
| /
| /
|/
+---------------------------->
Feature Implementation
Must-Have Features start negative if missing.
---
How Companies Use Kano
Typical process:
1. List potential product features
2. Ask customers two questions for each feature:
How do you feel if the feature exists?
How do you feel if the feature does NOT exist?
3. Categorize features into Kano types
4. Prioritize development
---
Simple Example (Food Delivery App)
Feature Kano Category Reason
Order tracking Must-have Expected
Fast delivery Performance Faster = happier
AI meal recommendation Delighter Surprise value
Theme color options Indifferent Little impact
---
Why Kano Is Important for Business Analysts
For BA/Product roles (like the ones you're applying to):
Kano helps you:
Prioritize requirements
Balance customer satisfaction vs development cost
Avoid building useless features
This is frequently discussed in Product Owner / BA interviews.
---
✅ Short interview answer
> The Kano Model is a product prioritization framework that categorizes features into Must-Have, Performance, and Delighters based on their impact on customer satisfaction. It helps teams prioritize development by focusing first on basic needs, then performance improvements, and finally delighting features.
