Kano Analysis is a framework for understanding which product features actually drive customer satisfaction, and which don't. Developed by Noriaki Kano in the 1980s, it separates features into categories that behave very differently, guiding product development toward the improvements that matter most.
Must-be: features whose absence causes dissatisfaction but whose presence is taken for granted (a car with brakes). Performance: features where "more is better" and satisfaction rises linearly with performance (fuel economy). Attractive: features customers don't expect but delight them when present (a thoughtful design detail). Indifferent: features customers don't care about either way. Reverse: features some customers actively dislike.
Customers answer paired questions for each feature: "how do you feel if this feature is present?" and "how do you feel if it is absent?" The pattern of answers classifies the feature into one of the categories. The exercise reveals where investment will produce real satisfaction, and where it will simply add cost the customer doesn't value.
Improving a Must-be feature past "acceptable" doesn't increase satisfaction; customers just expect it to work. Improving a Performance feature scales linearly. Adding an Attractive feature can create disproportionate delight, but attractive features tend to migrate over time to performance and then to must-be as customers get used to them. Kano keeps product decisions honest about where value actually comes from.
Kano Analysis turns "what should we build next?" from an opinion contest into a structured conversation grounded in customer response. Combined with Voice of the Customer and A/B testing, it helps teams invest development effort where it will produce measurable satisfaction, not just measurable output.
