ProductIntermediate7 min read

Kano Model

The Kano Model — developed by Noriaki Kano in 1984 — categorizes product features into five buckets based on how they affect customer satisfaction: Must-Haves (their absence destroys satisfaction; their presence is taken for granted), Performance (linear — more is better, like battery life), Delighters (their presence creates joy; their absence isn't noticed), Indifferent (no one cares), and Reverse (some customers want the opposite). The categorization comes from a paired survey: 'How would you feel if this feature were present?' and 'How would you feel if this feature were absent?' The brilliance is that it forces a non-linear view of features — adding more 'must-haves' doesn't increase satisfaction, while a single delighter can transform a product.

Also known asKano AnalysisKano SurveyKano CategorizationNoriaki Kano Model

Challenge a friend Browse library

The Trap

The biggest trap is that Delighters become Must-Haves over time, and most teams don't update their categorization. Apple introduced the trackpad scrolling gesture as a delighter in 2007 — by 2012, customers expected it on every laptop. Teams that built their roadmap around 'delight your customers' kept investing in flashy features without realizing yesterday's delighters were today's table stakes. Second trap: Kano surveys are slow and expensive, so teams skip the survey and just guess the categorization. Guessed Kano is just a roadmap with confidence theater attached.

What to Do

Run a Kano survey every 12-18 months on your top 15-20 candidate features. The paired questions force categorization: rate each feature on (1) functional form: 'I would like it,' 'It must be that way,' 'Neutral,' 'I can live with it,' 'I dislike it'; (2) dysfunctional form: same scale, but for the feature's absence. Cross-tabulate the answers — the matrix maps each respondent to a category for each feature. Build the most-have features first, the performance features second, and reserve 10-20% capacity for delighters. Re-survey when measured satisfaction stops correlating with shipped features.

In Practice

Hypothetical: A B2B SaaS team ran a Kano survey on 18 candidate features for their next two quarters. Results showed three features they'd planned as 'must-haves' actually scored Indifferent (a built-in chat widget, custom field reordering, and a mobile app for admins). The team killed those three features, freeing roughly 4 person-months. They reinvested in fixing slow page loads (categorized as a broken Performance feature) — measured DAU/MAU rose 8% in the following quarter. The Kano categorization paid back 10x its survey cost in killed features alone.

Pro Tips

01
Delighters have a half-life. The wow factor of any feature decays as competitors copy it and customers normalize. Plan delighter investments knowing they'll commoditize within 18-36 months — the goal is to be ahead of the commoditization curve, not to discover permanent magic.
02
Indifferent features are where most product roadmaps die. Teams ship features that fall in the Indifferent quadrant for everyone but the PM who advocated them. A Kano survey is brutal at exposing this — features the team loved score 70%+ Indifferent.
03
Segment Kano results by customer type. A feature that's a Delighter for power users may be Indifferent for casual users. Segment-level Kano often produces opposite categorization for the same feature, which means you should ship to the segment that delights and skip the segment that doesn't care.

Myth vs Reality

Myth

“You should always invest in delighters to differentiate”

Reality

Investing in delighters before nailing must-haves is product malpractice. Customers tolerate the absence of delighters but immediately leave when must-haves break. The order is: must-haves at 100%, performance features competitive, then delighters. Teams that flip the order build beautiful products that lose to functional ones.

Myth

“The Kano survey gives a definitive answer”

Reality

Kano categorization shifts based on segment, market maturity, and competitor moves. A 'delighter' in 2018 is a 'must-have' in 2024. The survey is a snapshot, not a permanent map. Teams that treat Kano as a one-time exercise build products optimized for last year's market.

Try it

Run the numbers.

Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.

🧪

Scenario Challenge

You're a PM at a project management SaaS. Your CEO wants to invest 60% of next quarter's roadmap in 'delighters' — animations, custom themes, AI-powered insights — to differentiate from competitors. Customer feedback shows 25% of paying customers complain weekly about a slow search feature and missing keyboard shortcuts. NPS is 22 (industry median: 35).

Industry benchmarks

Is your number good?

Calibrate against real-world tiers. Use these ranges as targets — not absolutes.

Roadmap Allocation by Kano Category

Quarterly product roadmap allocation

Healthy mix

55-65% Must-Have/Performance, 10-15% Delighter, 0-5% Indifferent

Delighter-heavy (risky)

30-40% Delighter

All-must-have (defensive)

90%+ Must-Have

Indifferent waste

>10% Indifferent

Source: Adapted from Noriaki Kano (1984) and modern product practitioner guidance

Real-world cases

Companies that lived this.

Verified narratives with the numbers that prove (or break) the concept.

🧪

Hypothetical: Mid-Market SaaS

Hypothetical 2023

success

Hypothetical: A 200-employee SaaS ran their first Kano survey on 20 candidate features after years of roadmap-by-loudest-voice. Results were uncomfortable: 6 of the top 10 'must-build' features categorized as Indifferent for the majority segment. Two features the team dismissed as 'nice to have' categorized as Must-Have for the enterprise segment (SSO depth and audit logs). The team reorganized the roadmap around segment-level Kano categories. Enterprise NPS rose 12 points; mid-market NPS held steady. Engineering velocity improved because the team stopped building features no one wanted.

Features killed post-survey

6 of 20

Engineering capacity freed

~30%

Enterprise NPS change

+12 points

Time to run survey

3 weeks (200 respondents)

Kano's value isn't the categorization — it's the permission structure to kill features that would have shipped on momentum alone.

Decision scenario

Delighter vs Must-Have Trade-Off

You're VP Product at a 100-person SaaS. Q4 Kano survey results just came in. The headline: your flagship 'AI-powered insights' feature, which the team has invested in for 18 months, now categorizes as Indifferent for 70% of users (down from Delighter for 65% just 12 months ago — competitors copied it). Meanwhile, two boring Must-Haves are broken: (1) reliable mobile app, (2) bulk export. Engineering capacity for Q4: 8 person-months.

AI insights category (12mo ago)

Delighter (65% of users)

AI insights category (now)

Indifferent (70% of users)

Mobile app reliability

Must-Have, currently broken

Bulk export

Must-Have, missing entirely

Q4 capacity

8 person-months

Decision 1

Your CEO wants to keep investing in AI insights to 'stay ahead' on the delighter axis. The Kano data says the AI feature has commoditized — it no longer differentiates. The Must-Haves are bleeding NPS and enterprise renewals. You can fund (a) more AI insights work, (b) fix the Must-Haves, or (c) split the capacity.

Continue AI insights investment — staying ahead on delighters builds long-term competitive moatReveal

Q4 ships 3 more AI insights features. Adoption metrics show 8% engagement (similar to last quarter). NPS continues declining as mobile and export issues persist. Two enterprise renewals are lost in Q1 next year citing 'platform reliability.' The Kano data accurately predicted this: delighters that have commoditized produce no satisfaction lift, while broken must-haves actively destroy satisfaction. Burned 8 person-months on the wrong axis.

Renewals lost (Q1 next year): −2 enterprise accountsNPS: Continued declineAI feature adoption: Flat 8%

Reallocate: 6 person-months to Must-Have fixes (mobile + export), 2 person-months to NEXT-generation delighter exploration (not more of the commoditized AI work)Reveal

Correct. Must-Have fixes ship by mid-Q4. Mobile app reliability triggers 11 pp NPS lift. Bulk export resolves a top-3 enterprise complaint. Two renewals that were at risk get extended. The 2 person-months of delighter exploration produces a small experiment that won't ship until Q2 — but it's a genuine differentiation candidate, not more commoditized AI. The Kano framework's value: it gave you permission to stop investing in last year's delighter and refocus on the must-haves customers actually feel.

NPS (Q4): +11 ppEnterprise renewals: 2 savedFuture delighter pipeline: 1 validated experiment in flight

Related concepts