Kano Model
Version 1.0.0 · Updated 2026-07-31
CORE DEFINITION
Classifies product requirements into three categories: 1. Must-be: having it doesn't add satisfaction, but lacking it causes dissatisfaction (e.g., a phone can make calls). 2. Performance: having it adds satisfaction, lacking it causes dissatisfaction (e.g., long battery life). 3. Delighters: having it adds satisfaction, lacking it doesn't cause dissatisfaction (e.g., a phone can take photos of the moon). -
SCAFFOLDING EFFECT
Reduce cognitive load
A classifier for requirement priority. - When resources are limited, you must first satisfy 'Must-be' (hold the baseline), then improve 'Performance' (accumulate...
Anchor fast decisions
Classifies product requirements into three categories: Must-be (absence causes dissatisfaction), Performance (more is better), and Delighters (presence brings surprise, absence doesn't cause dissatisfaction). The mechanism is **nonlinearity of requirements**—satisfaction does not increase linearly with features; Must-be is the 'passing line', and Delighters create word-of-mouth. Requirement categories shift over time (Delighters become Performance, then Must-be).
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Kano_modelverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS