The Kano Model: Basics, Performance and Delighters

The Kano model sorts product features by how they affect customer satisfaction. Some are basics customers expect, some are performance features they compare and some are delighters they never expected.

Knowing which is which helps you decide where to invest. It stops teams polishing things nobody notices while missing the basics that cause real frustration.

The Origins of the Kano Model

The model was introduced by Professor Noriaki Kano and colleagues in 1984, in a paper on attractive quality and must-be quality. Its big insight was that satisfaction isn't a straight line. Doing more of something doesn't always make people happier.

The Three Main Categories

• Basics. Customers expect them and won't thank you for them. Leave one out and they're furious. A banking app that shows your balance is a basic.
• Performance features. The more you deliver, the happier people are. Speed, price and battery life are classic examples. This is usually where products compete.
• Delighters. Customers don't expect them, so they don't miss them. When they find one, they're pleased and often tell others.

Kano also describes features people are indifferent to and features that actively annoy some people. Both are worth knowing about, so you can stop spending effort on them.

Delighters Fade Over Time

This is the part teams often forget. A delighter becomes a performance feature, then a basic. Contactless payment once felt clever. Then shops competed on it. Now people are surprised when it's missing.

So a Kano sort isn't a one-off. Re-sort your list every year or so.

When to Choose the Kano Model

Choose Kano when you need to decide which features are must-haves, which compete and which delight. It's especially useful before a big release, when entering a new market or when customers are unhappy and you can't tell why.

How to Use the Kano Model, Step by Step

1. List the features and qualities that matter to your customers. Include the boring ones.
2. Ask customers, don't guess. The classic Kano survey asks two questions per feature: how would you feel if it were there, and how would you feel if it weren't?
3. Classify each feature as a basic, performance feature or delighter, and note anything people are indifferent to or dislike.
4. Make sure every basic is present and reliable. Fix these first.
5. Invest in the performance features where you compete.
6. Save some room for a delighter that sets you apart.
7. Re-sort regularly as expectations change.

A Worked Example

A dog-walking app surveyed 120 owners about six features. Here's what the answers showed.

Feature	Category	What it means
Walker's ID and insurance checked	Basic	Non-negotiable. Must be visible and reliable.
Booking confirmation	Basic	Expected. Nobody will praise it.
Short-notice availability	Performance	The more slots, the happier owners are.
Price per walk	Performance	Owners compare apps on this.
Photo and route map after each walk	Delighter	Unexpected, and owners share them.
Walker leaderboard	Indifferent	Nobody cared. Stop work on it.

The team had been building the leaderboard. They paused it, made sure the insurance checks were visible on every profile and added the post-walk photo. Owners began sharing those photos on social media, which brought in new customers.

Running a Simple Kano Survey

You don't need special software to run a Kano survey. A short form with paired questions is enough.

For each feature, ask two questions. The first is functional: "If the app had this, how would you feel?" The second is dysfunctional: "If the app didn't have this, how would you feel?" Offer the same five answers each time: I'd like it, I'd expect it, I'm neutral, I could live with it or I'd dislike it.

The pair of answers tells you the category. If people expect it when present and dislike its absence, it's a basic. If they like it when present and dislike its absence, it's a performance feature. If they like it when present but are neutral without it, it's a delighter.

Keep the survey short. Eight to twelve features is plenty, or people start answering without thinking. Describe each feature in plain words, ideally with a picture, so everyone pictures the same thing.

When the results come back, look at the spread as well as the winner. A feature that splits evenly between basic and delighter may mean you have two different customer groups. That's worth knowing before you design for either.

Finally, share the results with the whole team. Kano is at its most powerful when designers, engineers and marketers all see the same picture of what customers expect.

Common Mistakes

• Guessing the categories. Teams often think a feature is a delighter when customers see it as a basic. Ask.
• Forgetting that delighters fade. Last year's surprise is this year's expectation.
• Over-investing in performance features customers already think are good enough.
• Ignoring the basics because they feel unglamorous. Missing basics cause the most complaints.

How the Kano Model Compares with Other Tools

Kano and MoSCoW fit together well. Basics usually become musts. Delighters are often the coulds that make a release memorable.

Kano and RICE answer different questions. Kano tells you what kind of value a feature brings. RICE helps you rank features once you know.

Kano and Jobs to Be Done also pair well. Jobs to Be Done explains why customers hire your product. Kano tells you which features satisfy that job and which delight.

The Product Field Kit includes a fillable Kano worksheet and a calculator that classifies features from your survey answers and plots them for you.

Questions People Ask

← More Field Notes