HomeFrameworksDesign & UX › Kano Model
// framework

Kano Model

Noriaki Kano, 1984

A feature classification model separating must-haves, performance features, and delighters — showing that the features buyers mention in reviews without being asked are always the attractive ones with the highest ROI to build.

// description

The Kano Model classifies product features into five categories: Must-haves (basic expectations that cause dissatisfaction when absent but not delight when present), Performance features (satisfaction increases proportionally with quality), Attractive features (delighters that customers don't expect but greatly appreciate), Indifferent features (customers don't care either way), and Reverse features (features some customers actively dislike). The model shows that not all features contribute equally to satisfaction.

// history

Noriaki Kano, a professor of quality management at Tokyo University of Science, published the model in 1984. It was influenced by Herzberg's two-factor theory of motivation and applied that logic to product quality. The Kano questionnaire (pairing a functional and dysfunctional form of each question) provides a structured way to classify features through customer surveys.

// example

A KDP publisher surveying buyers of her nurse planner finds: clean layout and correct page count are must-haves (assumed; their absence drives 1-star reviews); number of pages per section is a performance feature (more is generally better, up to a point); a nurse-specific shift tracking layout is an attractive feature (delights buyers who didn't expect it); and a generic inspirational quote on every page is an indifferent feature (nobody mentions it positively or negatively). This tells her where to invest: improve the shift tracking feature rather than adding more motivational quotes that cost design time but don't move satisfaction.

// katharyne's take

The Kano Model is brilliant for deciding what to add to a KDP interior or a digital product. Before you spend a week designing a new feature, ask: is this a must-have (if absent, buyers will complain), a performance feature (more is better), or an attractive feature (a genuine surprise that delights)? Most creators spend their time improving performance features when the highest ROI is in attractive features — the unexpected touches that generate "oh wow, I didn't know I needed this." Those are the features that get mentioned in reviews without prompting.

// creative uses
// quick actions
// prompt ideas
Apply the Kano Model to my [KDP journal / Etsy product / digital course]. Here are the features currently included: [list them]. Classify each as a must-have, performance feature, attractive feature, or indifferent feature. Then tell me: which features should I invest in improving, which attractive features are worth doubling down on, and what I should stop spending time on because buyers are indifferent to it.
I'm planning a v2 of my [product name / course / template pack]. Using the Kano Model, help me analyse my existing reviews to identify must-haves, performance features, and attractive features. Here are 10-15 representative review snippets: [paste them]. What does this review analysis tell me to build next, and what should I stop adding more of?
Help me design an "attractive feature" — a Kano delighter — for my next [KDP book / Etsy digital product / course module]. My core product is [describe it]. Brainstorm 8 unexpected additions that buyers in this category don't expect but would genuinely delight them if present — the kind that get mentioned in reviews without prompting. Then rank them by difficulty to implement vs. likely delight impact.
See also: Jobs to Be Done · Value Proposition Canvas · MoSCoW Prioritisation
← Jobs to Be Done Wizard of Oz Prototyping →