Kano Model
A framework for categorizing product features by how they affect customer satisfaction — from basic must-haves to unexpected delighters.
Origins
The Kano Model was introduced by Noriaki Kano, a professor at Tokyo University of Science, in his 1984 paper “Attractive Quality and Must-Be Quality.” Kano challenged the prevailing assumption that customer satisfaction was simply a function of how well a product performed — more performance, more satisfaction. His research demonstrated that different types of features produce radically different satisfaction responses, and that understanding those differences was essential to making good product decisions.
The model emerged from Kano’s work in quality management, but its practical implications for product strategy proved so powerful that it was adopted well beyond manufacturing — first by industrial design, then by software product teams, and eventually by startup founders looking for a principled way to prioritize their roadmaps.
The Core Idea
Not all features are equal. Adding a feature that customers expect to exist won’t delight them — it will merely prevent them from being disappointed. Adding a feature they never thought to ask for might generate extraordinary enthusiasm. And some features simply don’t move the needle at all, regardless of how well they’re executed.
The Kano Model gives product teams a language for these distinctions. By categorizing features according to how their presence or absence affects customer satisfaction, teams can make smarter decisions about what to build first, what to use for differentiation, and what to skip entirely.
The Five Feature Categories
1. Must-Be (Basic) Quality
These are features customers expect as standard. Their absence causes strong dissatisfaction. Their presence produces no positive reaction — customers simply take them for granted.
A banking app that crashes frequently violates a Must-Be. A banking app that reliably processes transactions does not delight anyone — it just meets the baseline expectation. Must-Be features are the entry price for a category. Ship without them and customers won’t consider you. Ship them and you haven’t earned differentiation — you’ve only earned consideration.
2. Performance (One-Dimensional) Quality
These features have a direct, proportional relationship with satisfaction: the more you deliver, the more satisfied customers are; the less you deliver, the more dissatisfied they become.
Page load speed, number of integrations, storage capacity, and price-to-value ratio are common Performance features. Unlike Must-Bes, improvements here are always rewarded. These are the features that show up clearly in competitive comparisons.
3. Attractive (Delighter) Features
Delighters are unexpected features that produce disproportionate satisfaction when present and cause no dissatisfaction when absent — because customers never thought to expect them.
A SaaS product that sends a personalized congratulatory message when a user hits a milestone. A financial app that visualizes spending patterns with a beautiful chart nobody asked for. An AI assistant that proactively flags an anomaly the user wouldn’t have noticed. Delighters create the moments users tell their colleagues about. They are the primary source of organic word-of-mouth.
4. Indifferent Quality
These are features that customers don’t care about either way. Their presence or absence has no measurable effect on satisfaction. Most features that get built fall into this category — especially features that teams build because they seem technically interesting or because a competitor has them.
Identifying Indifferent features is one of the most valuable outputs of a Kano analysis. It provides permission to deprioritize or cut scope without sacrificing satisfaction.
5. Reverse Quality
Some features actively displease a segment of customers while satisfying others. A highly automated workflow might delight power users who want speed but frustrate novices who want control. Mandatory social sharing features delight some users and alienate others. Reverse features require segmentation: who are you building for, and who might this push away?
| Category | Present | Absent | Strategic Role |
|---|---|---|---|
| Must-Be | Neutral | Strong dissatisfaction | Table stakes |
| Performance | More = more satisfied | Less = more dissatisfied | Competitive differentiation |
| Attractive | Delight | No dissatisfaction | Emotional differentiation |
| Indifferent | No reaction | No reaction | Cut or deprioritize |
| Reverse | Dissatisfaction (for some) | Relief (for some) | Segment carefully |
The Kano Survey Method
The Kano Model is not only a taxonomy — it comes with a structured research method. For each feature under evaluation, customers are asked two questions:
- Functional question: “How would you feel if this feature was present?”
- Dysfunctional question: “How would you feel if this feature was absent?”
Each question has five response options: I like it, I expect it, I’m neutral, I can live with it, I dislike it. The combination of functional and dysfunctional responses maps each feature to one of the five categories using a standard Kano evaluation table.
This paired-question structure is what distinguishes the Kano Method from simple feature voting. It reveals the asymmetry in how customers respond to presence versus absence — which is the critical insight the model is built on.
Applying the Kano Model in Practice
Prioritization Order
The Kano Model implies a natural build sequence:
- Satisfy all Must-Bes first. A single missing Must-Be can disqualify your product regardless of how good everything else is.
- Invest in Performance features competitively. These are what justify your pricing and positioning versus alternatives.
- Use Delighters strategically. One or two well-placed Delighters do more for differentiation and retention than many incremental Performance improvements.
Feature Decay Over Time
One of Kano’s most important insights is that feature categories are not static. Delighters become Performance features over time as market expectations rise. Performance features become Must-Bes as they reach ubiquity.
When the iPhone launched in 2007, its pinch-to-zoom gesture was a Delighter — nobody expected it, and it was a source of genuine wonder. By 2012, its absence on any smartphone would have been a Must-Be violation. The same pattern plays out in enterprise software, B2B SaaS, and consumer apps. Categories always move in one direction: Delighter → Performance → Must-Be.
For startups, this means the Delighters you build today are buying you time, not permanent advantage. The goal is to keep innovating in the Attractive quadrant while ensuring your Must-Be and Performance foundation keeps pace with rising market standards.
Limitations
- The Kano survey requires a sufficient sample of target customers to be statistically meaningful — difficult in very early stages.
- Customer responses reflect what they can articulate; they may not capture latent needs or desires they haven’t yet formed.
- The same feature can fall into different categories for different customer segments, requiring segmented analysis.
- The method is a snapshot in time. As noted above, categories shift — a Kano analysis done 18 months ago may already be outdated.
- Running a full Kano survey for every roadmap decision is impractical; it is best reserved for significant prioritization moments or major product bets.
Key Takeaway
The Kano Model transforms feature prioritization from intuition into a structured decision. Before any roadmap debate, ask which category a proposed feature falls into: is it a Must-Be that protects you from disqualification, a Performance feature that drives competitive positioning, a Delighter that creates differentiation and word-of-mouth, or an Indifferent feature that should be cut? Build Must-Bes completely. Compete on Performance features where they matter to your segment. Deploy Delighters deliberately. And remember: today’s Delighter is tomorrow’s table stake.