The Kano model is a framework for categorizing product features by how they affect customer satisfaction. Developed by Noriaki Kano in the 1980s, it helps teams decide what to build next by distinguishing between features customers expect, features they value, and features that genuinely delight them.
The three categories
Basic features are expected. Customers don't mention them when they exist, but they're furious when they don't. A save button is a basic feature.
Performance features scale linearly with satisfaction. The faster your search, the happier the user. More of these is always better.
Excitement features (delighters) are things customers didn't know they wanted. Finding them creates loyalty that performance improvements alone can't match.
Why it's useful
Not all feature requests carry the same weight, even when customers ask for them the same way. A request might be a basic expectation you've missed, or a nice-to-have that sounds important but won't move retention.
Kano also prevents feature bloat. Adding excitement features doesn't help if your basics are broken. Fix the foundation first.
One catch: categories shift over time. Last year's delighter is this year's basic expectation. Re-run the analysis periodically.
Apply Kano before committing to anything on your roadmap.