The Kano Model: Not All Features Are Created Equal

WHY IT EXISTS Product teams constantly face the question: what should we build next? Without a framework, they risk wasting effort on features that don't increase customer satisfaction. The Kano model was created to solve this by providing a structured way to prioritize features based on their likely emotional impact on users.

THE MENTAL MODEL Think of features in three main buckets. First, MUST-HAVES are features whose absence makes users angry, but whose presence they don't even notice (like a car having brakes). Second, PERFORMANCE features are linear: the better you make them, the happier users are (like gas mileage). Third, DELIGHTERS are unexpected surprises that create joy, but whose absence goes unnoticed (like the first car with cup holders).

HOW IT WORKS The model classifies features into five categories based on customer surveys. The main three are Must-Be Quality (basic expectations), One-Dimensional Quality (performance payoffs), and Attractive Quality (delighters). Two others are Indifferent (users don't care) and Reverse (users actively dislike them). To categorize a feature, you survey users with two questions: a functional one ("How would you feel if you had this feature?") and a dysfunctional one ("How would you feel if you did NOT have this feature?"). The combination of answers maps the feature to a category.

WHEN TO USE IT Use the Kano model when planning a product roadmap, especially for a mature product where you need to decide between fixing basics, improving existing features, or innovating. It's a powerful tool for aligning engineering effort with customer value and defending prioritization choices to stakeholders.

WHEN NOT TO USE IT Don't treat the categories as static. A delighter in one product version can become a must-have in the next as the market evolves. The model is also less useful for brand-new, category-defining products where user expectations haven't been formed yet. The survey-based approach can also be time-consuming for teams that need to move very quickly.

ONE CANONICAL EXAMPLE Consider a smartphone. A reliable phone call function is a Must-Be feature; its absence is unacceptable, but its presence isn't praised. Battery life is a One-Dimensional (Performance) feature; the longer it lasts, the more satisfied users are. The first time a company introduced a high-quality portrait mode camera, it was an Attractive (Delighter) feature; users didn't expect it, but were thrilled to have it. Now, for many users, it's becoming a Must-Be for flagship phones.