What is the Kano model — and how it separates delighters from must-haves.
Short answer
The Kano model is a product development framework that classifies features into five categories based on how they affect customer satisfaction: Basic needs (expected, dissatisfying if absent), Performance needs (more is better, linear satisfaction), Excitement features (delighters, unexpected, no dissatisfaction if absent), Indifferent features (don't affect satisfaction either way), and Reverse features (some customers dislike them). Developed by Noriaki Kano in 1984, it helps teams decide what to build and in what order.
The Kano model was developed by Japanese quality management professor Noriaki Kano and published in 1984. It reframes the question of feature priority from "how important is this?" (which conflates different types of value) to "how does this feature affect customer satisfaction in the presence or absence of it?"
The five categories.
Basic needs (Must-Be quality). Features customers expect so naturally that they don't mention them when they're present — but are highly dissatisfied when they're absent. Example: a banking app that works without crashing. Adding more reliability beyond a threshold doesn't increase satisfaction; removing it causes severe dissatisfaction. Build these first; don't compete on them.
Performance needs (One-dimensional quality). More is better — satisfaction increases linearly with the feature's quality. Example: battery life on a laptop. Customers explicitly mention these in research because they compare on them. Competing on performance features is where most product investment goes.
Excitement features (Attractive quality / Delighters). Features customers don't expect but are pleasantly surprised by. When present: high satisfaction. When absent: no dissatisfaction (they didn't know to miss it). Example: a phone camera feature that automatically corrects the horizon. Delighters create word-of-mouth and brand differentiation.
Indifferent features. Customers don't care whether the feature exists. Building these wastes resources. The surprising finding from Kano surveys: many features teams debate intensely turn out to be indifferent to actual users.
Reverse features. Some customers are actively dissatisfied by features that others find attractive. This reveals segmentation — different customer groups have fundamentally different preferences. Building for one segment may repel another.
Running a Kano survey. For each potential feature, ask two questions: (1) How do you feel if this feature is present? (Delighted / Expect it / Don't care / Tolerate it / Dislike it.) (2) How do you feel if this feature is absent? Same scale. The combination of the two answers classifies each feature into the Kano categories. Run the survey with 20–50 customers; patterns emerge quickly.
The Kano insight. Delighters eventually become basic needs as customer expectations rise. Yesterday's wow becomes today's expectation. This means the search for new delighters is never done — the Kano map for a product shifts every 2–3 years.
A Kano mapping session at the whiteboard places features on a 2x2 (satisfaction if present × dissatisfaction if absent). Snap the whiteboard with BoardSnap and the AI reads the placement and produces a prioritized feature list by Kano category.
Frequently asked
Who invented the Kano model?
Noriaki Kano, a Japanese quality management expert and professor at the Tokyo University of Science, developed the model in 1984. It was published in the Journal of the Japanese Society for Quality Control. Kano was influenced by Frederick Herzberg's two-factor motivational theory, which similarly distinguished between hygiene factors (dissatisfiers) and motivators (satisfiers).
How is the Kano model different from simple feature prioritization?
Simple prioritization asks how important a feature is. Kano asks how presence or absence affects satisfaction differently. A feature can be critically important (high priority) but be a Basic need — meaning it will never delight customers, only fail to dissatisfy them. Understanding the category changes the investment strategy: basics must be met; performance features are where you compete; excitement features are where you differentiate.
Can Kano categories change over time?
Yes — and this is one of the model's most important insights. Excitement features become Performance needs and eventually Basic needs as customer expectations rise. Touch ID was a delighter in 2013; by 2016 it was expected on all smartphones. Teams should re-run Kano surveys every 2–3 years to understand how their feature landscape has shifted.
See it work in ten seconds.
BoardSnap is free on the App Store. Snap a board — get a summary and action plan.