Three categories that behave differently
The model's core distinction is between three ways an attribute can relate to satisfaction. Two further categories, indifferent (nobody cares either way) and reverse (some customers actively dislike it), are quoted less often and are routinely the most useful finding in a real study.
| Category |
How it behaves |
Recognisable examples |
| Basic (must-be) |
Absence causes dissatisfaction; presence goes unnoticed. It can only fail, never delight. |
The card payment that simply processes; brakes that work; a hotel room that is clean |
| Performance (one-dimensional) |
Satisfaction rises roughly in line with how much of it you deliver. Where most head-to-head competition happens. |
Battery life, delivery speed, storage capacity, price |
| Attractive (delighter) |
Absence costs nothing, because nobody expected it; presence creates disproportionate satisfaction. |
Hotel Wi-Fi when it was new; the first phone cameras; an onboarding step that removes a dreaded task |
How the categories are actually established
Kano's method pairs two questions per attribute: how would you feel if the product had this (the functional form), and how would you feel if it did not (the dysfunctional form). The pattern of answers across a sample of real customers assigns the category. The mechanics matter because they place the authority outside the building: an attribute is a delighter because customers answered that way, not because the product team feels it. A Kano exercise run as an internal workshop with no customer data is an opinion poll of the people who built the product.
Delight decays into expectation
Attractive attributes do not stay attractive. As competitors copy them and customers habituate, they slide into performance territory and finally into basics: hotel Wi-Fi went from chargeable novelty to assumed utility in under a decade, and smartphone cameras made the same journey. The implication for roadmap planning is uncomfortable. Delight is a depreciating asset, the categories are a snapshot rather than a property of the feature, and a study from three years ago describes a market that no longer exists. The decay also pushes cost in one direction, because yesterday's differentiator becomes something that must now be maintained without winning anything.
A roadmap illustration
A B2B software company is allocating its next two releases. Sales lobbies for an analytics dashboard on the grounds that customers will love it. A Kano survey of forty active customers tells a different story: the dashboard lands as indifferent (most respondents already run their own BI tools), export-to-spreadsheet emerges as a basic whose intermittent failures are churning two named accounts, and processing speed shows up as a classic performance attribute worth every increment. The release plan inverts: fix the export, invest in speed, park the dashboard. The decision required no genius, just a structured question put to customers instead of an argument settled by seniority.
How Kano gets bent inside product teams
The failure modes cluster around one theme: the team supplies the answers the method was designed to collect.
- Pet features are classified as delighters without customer evidence, because the sponsor is certain customers will love what the team enjoyed building. The delighter label is the easiest place in the model to hide a preference.
- The survey sample is drawn from friendly customers, the ones who accept the call, and the categories inherit the bias of the relationship.
- Basics are starved because fixing them wins no internal credit: nobody presents "the export now works every time" at a product showcase, so the work that prevents churn loses out to the work that demos well.
- Categories are treated as permanent, and the roadmap keeps defending a differentiator that decayed into a basic two years ago.
- Segments are averaged together, hiding that one segment's delighter is another's reverse attribute: the automation that thrills a mid-market buyer can read as loss of control to an enterprise one.
Customer evidence against internal conviction
Every category debate inside a product organisation is also a debate about whose roadmap wins, which is why the delighter label attracts so much lobbying. Selected senior operators who have run comparable products have watched this category's delighters decay on someone else's budget, and they can read a Kano study against what customers in the market actually punished rather than what they praised. Putting the roadmap's biggest bets through that filter before the release is committed costs a fraction of shipping a delighter nobody asked for while a basic fails.
