Definition
Kano Model
The Kano model classifies product features by how their presence or absence affects customer satisfaction, sorting them into five types: Must-be (basics expected by default), Performance (more is better), Attractive (delighters), Indifferent (no effect either way), and Reverse (please some, annoy others). Its core insight is that satisfaction is asymmetric — a missing basic angers users while its presence earns no credit.
Key takeaways
- The Kano model sorts features into five types — Must-be, Performance, Attractive (delighters), Indifferent, and Reverse — by their effect on satisfaction.
- Its core insight is asymmetry: a missing basic angers users while its presence earns no credit, and a delighter thrills without its absence disappointing.
- It's measured with a paired survey asking how customers feel when a feature is present versus absent, then classifying the answers.
- Categories drift over time — today's delighter becomes tomorrow's must-be — so classifications need periodic revisiting.
Developed by Professor Noriaki Kano in the 1980s, the model maps each feature against two axes: how well it's implemented and how satisfied customers are. Must-be features are table stakes — their absence causes strong dissatisfaction, but their presence is simply expected and adds no delight (a hotel room with a working lock). Performance (one-dimensional) features track satisfaction linearly: the more or better, the happier customers are (faster load times, longer battery).
Attractive features, or delighters, are the asymmetric upside — when present they generate disproportionate joy, but when absent they cause no complaint because customers didn't expect them. Indifferent features move the needle neither way and are candidates to cut. Reverse features satisfy some users while actively annoying others (autoplaying video), so they need segmentation rather than a blanket decision.
The model's lasting value is that asymmetry: you can't earn loyalty by perfecting basics alone, and you can't skip basics by adding delighters on top of a broken foundation. It's measured with a paired questionnaire that asks how a customer feels both when a feature is present and when it's absent, then classifies the response. A second caution is that categories drift over time — today's delighter (a camera on a phone) becomes tomorrow's must-be.
Planoda can tag roadmap initiatives with their Kano category alongside scores like RICE, so a roadmap balances must-be foundations against the attractive bets that differentiate the product.
Related terms
- RICE PrioritizationRICE is a prioritization framework that scores each initiative by Reach (how many people it affects), Impact (how much it moves the needle per person), Confidence (how sure the estimates are), and Effort (the work required). The score is Reach × Impact × Confidence ÷ Effort, producing a comparable number that ranks competing ideas by expected value per unit of work.
- ICE ScoringICE is a lightweight prioritization framework that scores each idea on three factors — Impact (how much it will move the goal), Confidence (how sure you are in the estimate), and Ease (how simple it is to implement) — usually on a 1–10 scale. The ICE score is Impact × Confidence × Ease, giving a fast, comparable number for ranking competing experiments.
- MoSCoW PrioritizationMoSCoW is a prioritization method that sorts requirements into four categories — Must have, Should have, Could have, and Won't have (this time). The capitalized letters form the name; the lowercase o's make it pronounceable. It forces a team to agree explicitly on what is essential versus deferrable, rather than treating every request as equally urgent.
- RoadmapA roadmap is a high-level, time-oriented view of what a team or product plans to build and roughly when. It communicates direction and sequencing across initiatives and projects, aligning stakeholders on priorities. Unlike a backlog of granular tasks, a roadmap operates at the altitude of themes, outcomes, and quarters rather than individual issues.
- Product-Market FitProduct-market fit is the point at which a product satisfies a strong market demand — the right product serving the right market so well that growth begins to pull rather than push. It is the milestone before which a startup should focus on finding fit, and after which it should focus on scaling, often felt as demand outrunning the team's ability to keep up.