Skip to main content
Not all features are equal. Some make customers ecstatic. Some are expected - invisible when present, deal-breaking when absent. Some genuinely don’t matter. The Kano model helps you tell them apart before you build them 🎯 Developed by Professor Noriaki Kano in the 1980s, it maps features against two axes: how well you’ve implemented the feature, and how satisfied customers are as a result. The relationship isn’t always linear - and that’s exactly the insight.

​
The three main categories

Basic needs (must-haves) - Features customers expect as a baseline. They don’t create satisfaction when present - they just avoid dissatisfaction when absent. A login that works. A checkout that doesn’t error. Mobile responsiveness. Customers won’t thank you for these; they’ll punish you for missing them 😬 Performance needs (linear) - More is better, less is worse, in a roughly linear relationship. Speed, storage, accuracy, price. Improvements here directly increase satisfaction. Decline and satisfaction drops proportionally. These are the features worth investing in consistently. Delighters (excitement needs) - Features customers didn’t know they wanted but love when they discover them. By definition, their absence doesn’t cause dissatisfaction - because customers weren’t expecting them. But when they’re done well, they create disproportionate delight and word-of-mouth. The magic moments.

​
The twist: decay over time

Here’s what makes the Kano model genuinely useful rather than just interesting: delighters become performance needs, and performance needs become basic needs over time. Touch ID was a delighter when Apple introduced it. Now it’s a basic need - nobody buys a phone that doesn’t have biometric unlock. The same happens in every product category. This means you can’t rely on yesterday’s delighters to maintain your competitive advantage. What wowed customers two years ago is table stakes today 📉

​
Using it in practice

The Kano model is most useful during prioritisation. When you have a list of potential features, a quick Kano survey can help you categorise them: Ask two questions about each feature:
  1. “How would you feel if this feature were present?”
  2. “How would you feel if this feature were absent?”
The combination of answers places the feature in a category. Features that produce “I’d love it / I’d be fine without it” responses are delighters. “I’d expect it / I’d be frustrated” responses indicate basic needs.

​
The prioritisation implication

  • Basic needs - Get them right first. No amount of delighters compensates for a broken core experience
  • Performance needs - Invest proportionally based on how much they move satisfaction relative to cost
  • Delighters - Place a few strategic bets here. They’re your differentiation, but only until competitors copy them
Lesson learned: the most common mistake is treating everything as a performance need - assuming that more features always equal more satisfaction. The Kano model is a useful reminder that customers experience your product in categories, not on a single satisfaction scale 👊