Not all features are equal, and more is not always better. Kano sorts features by how they affect satisfaction — basics you'll be punished for missing, performance you're rewarded for, and delighters that surprise.
▸ Try the interactive toolThe Kano Model, developed by Noriaki Kano in 1984, categorises features by their relationship to customer satisfaction. Its core insight: not all features are equal, and more of a feature is not always better. Some features cause outrage if missing but delight no one if present; others surprise and delight but are never expected.
Kano sorts features into a few types — most importantly Must-be (basics whose absence angers but whose presence is unremarkable), Performance (the more, the better — linear satisfaction), and Delighters (unexpected features that excite). Crucially, categories decay over time: today's delighter becomes tomorrow's expectation. It tells you not just what to build but how much, and when to stop.
Must-be — absent = anger, present = neutral (the price of admission) · Performance — more is linearly better · Delighter — unexpected, creates excitement · Indifferent — users don't care either way
Teams routinely over-invest in basics (where extra effort earns nothing) or chase delighters before basics are solid (where the product feels broken despite the flourishes). Kano prevents both.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Treating all features equally | Equal effort to basics and delighters wastes both. | Categories tell you where effort changes satisfaction and where it doesn't. |
| Over-building basics | Polishing a Must-be past “works” earns no extra satisfaction. | Must-be features are satisfied at “present and reliable” — stop there. |
| Delighters before basics | Flashy extras on a product that fails the basics feels broken. | Kano enforces order: secure the Must-bes first, then performance, then delight. |
| Ignoring decay | Yesterday's delighter is today's expectation; teams coast on it. | The decay insight forces continual renewal of what delights. |
Gather the features under consideration — a mix of basics, improvements, and novel ideas.
For each feature, ask users how they'd feel if it were present, and how they'd feel if it were absent. The pattern of answers reveals the category.
Map responses to Must-be, Performance, Delighter, or Indifferent. The present-vs-absent contrast is what classifies it — anger-if-absent, neutral-if-present signals a Must-be.
Secure all Must-bes first (non-negotiable), invest in the Performance features that differentiate, then add a delighter or two. Drop Indifferent features entirely.
Categories decay — delighters become expectations as competitors copy them. Re-survey over time so your “delight” budget keeps moving to genuinely novel things.
A team had budget for several features and instinctively wanted to build the exciting one — a novel “delighter.” A Kano survey showed two of their planned items were actually Must-bes the product was missing: their absence quietly angered users, even though no one had filed a feature request for them.
Shipping the delighter on top of missing basics would have felt like a sports car with no seatbelts. They sequenced correctly — basics first, then the delighter — and the delighter actually landed because the foundation was solid.
The deliverable is each feature tagged by Kano type, which dictates how much to invest and in what order.
| Category | If absent | If present | Investment rule |
|---|---|---|---|
| Must-be | Anger / churn | Neutral (expected) | Ensure it works — don't over-polish |
| Performance | Disappointment | Satisfaction (linear) | Invest where it differentiates |
| Delighter | Neutral (not expected) | Excitement | Add a few — they decay, so renew |
| Indifferent | Neutral | Neutral | Don't build it |
“More features” and “better product” are not the same thing. Kano shows that effort on a Must-be past “it works” is wasted, and a delighter on a broken foundation is invisible.
The subtle, strategic part is decay. Every delighter is on a one-way trip to becoming an expectation — the moment competitors copy it, it drops from “exciting” to “must-be,” and its absence now angers where its presence once thrilled. This means a product can't coast: the delight budget has to keep moving to genuinely new things, while yesterday's delighters get quietly maintained as the basics they've become. Kano is therefore not a one-time sort but a periodic re-survey — a map of a moving target.
Polishing a basic past “reliable” earns nothing. Secure it, then move on.
A flashy feature on a product missing its Must-bes feels broken. Sequence correctly.
If users don't care either way, it's pure waste. Cut it.
Delighters decay into expectations. Re-survey, or you'll coast on a delighter that's quietly become a basic.
Kano category sharpens the Impact score in RICE — a missing Must-be is high-impact; an Indifferent feature is near zero.
Kano helps ensure the Must-bes are solid — a precondition for the PMF the next tool measures.
The Kano survey is a specific design; clean questions are essential to clean categories.
Category order (basics → performance → delight) is a direct input to how you sequence a roadmap.
Pick a product you use and list five of its features. For each, ask yourself: how would I feel if it were present? Absent? Sort them into Must-be, Performance, Delighter, or Indifferent.
Then find a feature that used to delight you but now feels expected — that's category decay in action.
The decayed delighter is the most instructive one: it shows why no product can stop innovating, because every delight has a shelf life.