What Is the Kano Model?
The Kano Model is a product development and customer satisfaction theory created by Professor Noriaki Kano at Tokyo University of Science in the 1980s. It classifies product features into five categories based on how they affect customer satisfaction: Must-be (basic expectations), Performance (the more the better), Attractive (delighters), Indifferent (customers do not care), and Reverse (features that cause dissatisfaction). The model recognizes that the relationship between feature implementation and customer satisfaction is not always linear — some features have diminishing returns while others have outsized impact.
Why the Kano Model Matters for Product Teams
Not all features are created equal. Traditional prioritization treats every feature request as equally important, leading to bloated products and wasted development effort. The Kano Model provides a structured framework for understanding which features are table stakes (Must-be), which drive competitive advantage (Performance), and which can create viral delight (Attractive). Product managers use Kano analysis to make better roadmap decisions, allocate engineering resources efficiently, and differentiate their product in crowded markets.
Understanding the Five Categories
Must-be features are expected by default — their absence causes major dissatisfaction, but their presence does not increase satisfaction (e.g., a working brakes in a car). Performance features have a linear relationship — better execution means higher satisfaction (e.g., battery life). Attractive features are unexpected bonuses that delight when present but are not missed when absent (e.g., a surprise upgrade). Indifferent features do not affect satisfaction either way. Reverse features actually decrease satisfaction when implemented, indicating a mismatch between the feature and the user segment.
Best Practices for Kano Analysis
Survey at least 20-30 customers for statistically meaningful results. Use the standard Kano questionnaire: for each feature, ask both the functional question (how would you feel if this feature was present?) and the dysfunctional question (how would you feel if it was absent?). Segment your results by customer type — different segments may classify the same feature differently. Remember that categories shift over time: yesterday's Attractive feature becomes today's Performance feature and tomorrow's Must-be. Re-run Kano analysis quarterly to keep your roadmap aligned with evolving expectations.
