Prioritization
The Kano model, explained for product teams
Not all value is the same kind of value. Kano sorts features into basics, performance, and delighters — and tells you where investment actually pays off.
Most prioritization frameworks rank a list. The Kano model does something different: it tells you what kind of value a feature delivers, which changes how you think about the whole backlog. Developed by Noriaki Kano, it sorts features by how they affect customer satisfaction.
The categories
Basic (must-be) features are expected. Their presence is invisible; their absence is infuriating. A hotel room has a clean bed — nobody praises it, but a dirty one ends the relationship. You don't get credit for basics, but you can't skip them.
Performance features scale linearly: more is better, and customers will pay for more. Faster load times, more storage, better search. Investment here produces proportional satisfaction, which makes these the easiest to justify on a spreadsheet.
Delighters (attractive features) are unexpected. Customers don't ask for them and don't miss them when absent — but their presence creates disproportionate goodwill. These are where differentiation lives.
The moving bar
The crucial insight: categories migrate over time. Today's delighter becomes tomorrow's performance feature and eventually a basic expectation. Front-facing cameras delighted, then competed, then became mandatory. This means a portfolio of only basics is a treadmill — you're running to stay in place — while a portfolio of only delighters ignores the table stakes that keep you in the game.
How to use it
Kano data comes from a specific survey: for each feature, ask how the customer would feel if it were present, and how they'd feel if it were absent. The pattern of answers classifies the feature. You don't need the full survey to think in Kano terms, though — just asking "is this a basic, a performance gain, or a delighter?" reshapes a backlog conversation.
Kano tells you what to invest in; it doesn't sequence the work. Once you know a feature is, say, a high-leverage delighter, bring it back to RICE or Value/Effort to decide when it ships relative to everything else.
- Kano classifies features by how they affect satisfaction, not by effort.
- Basics are expected (their absence hurts); performance scales with investment; delighters surprise.
- Today's delighter becomes tomorrow's basic — the bar keeps rising.
- Use it to decide what kind of value to buy, then RICE to sequence the list.
Try the Prioritization workflow in Cadenly
Use Kano to decide what kind of value to invest in, then bring the shortlist into Cadenly's RICE workflow to sequence it.
Start free →