Kano model
Definition
The Kano model is a product development and customer satisfaction framework, created by Noriaki Kano in the 1980s, that categorizes product features into five types based on how their presence or absence affects customer satisfaction — helping teams prioritize what to build and in what order.
Noriaki Kano, a Japanese engineer and management consultant, developed the model in 1984 at Tokyo University of Science. The core insight: not all features affect customer satisfaction the same way. Some features delight customers when present; others just prevent dissatisfaction when absent. Understanding which is which changes how you should prioritize.
The five Kano categories:
- Must-be (Basic needs): Features customers expect to be there. When present, they don't create satisfaction — they're just expected. When absent, customers are furious. Example: a login button on a web app. Nobody gives you credit for having it; everyone complains if it's broken.
- Performance (Linear): The more, the better — customers are proportionally more satisfied as the feature improves. Example: battery life, page load speed, number of integrations. These are usually the "main features" you compete on.
- Attractive (Delighters): Features customers didn't expect but love when they discover them. When absent, nobody misses them. When present, they create strong positive reactions and loyalty. Example: a clever keyboard shortcut, a beautiful empty state, a personalized welcome message.
- Indifferent: Features that don't affect satisfaction either way. Customers don't care if you have them or not. Dangerous if they consume engineering time.
- Reverse: Features that actually reduce satisfaction for some customer segments — what some users love, others hate.
How to run a Kano survey: For each feature, ask customers two questions: "How do you feel if this feature is present?" and "How do you feel if this feature is absent?" Map the responses to the categories using the Kano evaluation table.
Attractives are strategically valuable — they often become the next generation of Performance features as competitors copy them.
Examples
- Kano survey reveals that users categorize onboarding checklist as a Must-be (expected) — team deprioritizes as a 'delighter' since it won't surprise users
- Response time under 2 seconds categorized as Performance — every 100ms improvement directly increases satisfaction
- BoardSnap's brand-aware AI categorized as an Attractor — users didn't know they wanted it, but love it when they see it
- Feature idea classified as Indifferent after Kano survey — removed from backlog, saving two weeks of engineering
- Team discovers a feature loved by power users is Reverse for casual users — builds it as an opt-in setting
Snap a kano model. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.