The Kano Model

What it is

The Kano Model is a way to prioritize features by how they actually affect customer satisfaction. Developed by Japanese researcher Noriaki Kano in the 1980s, it makes one crucial point that a flat priority list misses: different kinds of features move satisfaction in fundamentally different ways. A missing password reset makes people furious, but a flawless one wins you nothing, it's simply expected. A clever, unexpected touch can create loyalty out of proportion to its effort. Treating those two the same on a backlog is how teams waste quarters.

Kano plots features on two axes: how well a feature is implemented, and how satisfied users feel. Different feature types trace different curves across that space, which is what gives you the categories below.

When to use it

• Your backlog is longer than your roadmap. Kano turns "everything is a priority" into a defensible sequence.
• You're tempted by shiny features. It's a discipline check: are the basics actually solid before you chase delight?
• Your PMF score is stuck below 40%. Kano helps you tell "we're missing a must-have" from "we lack anything users love."
• You're planning a launch or a redesign. It keeps scope honest by separating table stakes from differentiators.

How to apply it

1. List your candidate features. Everything you're weighing for the roadmap goes on the table.
2. Ask the Kano question pair. For each feature, ask users two things: how would you feel if it were present, and how would you feel if it were absent? The pair is what reveals the category.
3. Categorize each feature. Map the answer pairs to must-be, performance, attractive, indifferent, or reverse.
4. Sequence the roadmap. Secure every must-be first, invest in the performance features that differentiate you, then add a couple of delighters. Never ship delighters while a basic is broken.
5. Re-run it over time. Categories drift. Today's delighter becomes tomorrow's expectation, so recategorize periodically.

Example

Think about a note-taking app. Reliable sync is a must-be: nobody praises it, but lose a note once and you lose the user. Search speed is a performance feature: faster is genuinely better, and users feel every improvement. An AI that turns messy notes into a clean summary is a delighter: unexpected, memorable, and the kind of thing people tell others about. Spend your first sprints perfecting the AI summary while sync silently drops notes, and your PMF score sinks no matter how clever the delighter is. Kano forces that sequencing into the open.

Common mistakes

• Building delighters on a broken foundation. A delighter never compensates for a missing must-be. Fix the basics first, every time.
• Assuming delighters last. They decay into expectations. What wowed users last year is table stakes now, so the roadmap is never finished.
• Categorizing from the building instead of from users. Teams routinely mislabel their pet features as delighters. Ask real users with the question pair.
• Ignoring reverse features. Some additions actively annoy a segment. More is not always better, and Kano is one of the few tools that catches this.

How it connects to your PMF score

The Kano categories map cleanly onto the Sean Ellis survey. Must-be features are defensive: when they're missing or broken, users drift toward "not disappointed" and your score bleeds. Performance and attractive features are offensive: they're what create the "very disappointed" segment that defines real fit. Someone answers "very disappointed" because you do something they can't easily replace, and that something is almost always a strong performance feature or a genuine delighter.

So a stuck score has two very different diagnoses, and Kano tells them apart. Below 40% with lots of complaints usually means broken must-be features. Below 40% with quiet indifference usually means you have no delighters and nothing users would miss. The fix is completely different, and guessing wrong costs a quarter. Pair Kano with Jobs to Be Done to make sure the features you're grading are aimed at a job users actually have.