Kano Model: Build Features Users Need vs Features Users Want

At a Glance: The Problem the Kano Model Solves

Teams tend to add features that sound exciting in brainstorming sessions but do not improve user retention—while neglecting basic, "boring" features whose absence causes users to churn. The Kano Model, developed by Professor Noriaki Kano in Tokyo in 1984, provides a structured framework to categorize features based on how their presence or absence impacts user satisfaction. It helps product managers move away from speculative roadmaps and prioritize features based on validated customer experience segments.

The 4 Core Kano Categories

Basic Needs (Must-Haves / Threshold Features)

Users take them for granted — but will immediately churn if they fail

Basic Needs are the foundational elements of your category. When they work, users feel neutral (no extra satisfaction). But if they break or fail, user dissatisfaction spikes instantly. In fintech, secure bank account linking, OTP delivery, and password reset flows are Basic Needs.
Strategy: Ship these first. Do not allocate resources to exciting new features until your Must-Haves are rock-solid and fail-safe.

Performance Features (Linear Satisfiers)

Directly linear: More Performance = More Satisfaction

Performance features have a direct, linear relationship with user satisfaction. Faster loading times, better interest rates, wider mutual fund selections, and higher cashback rates are all linear features. This is where active competitive comparison occurs.
Strategy: Invest here after your Basic Needs are fully sealed. Continuous optimization in this zone returns predictable customer satisfaction lifts.

Delighters (Attractive / Excitement Features)

Unexpected value that drives word-of-mouth and NPS

Delighters are features users do not expect. Their absence causes zero complaints because users do not know to ask for them. However, when present, they drive high delight, creating strong retention hooks and unpaid viral referral loops.
Strategy: Build one or two key Delighters per release cycle once your core product foundation is healthy.

Indifferent Features

Features that users genuinely do not care about either way

Present or absent—satisfaction remains completely unchanged. Product backlogs are often clogged with Indifferent features (such as dark mode in a B2B tax compliance dashboard or a Google Calendar sync for loan EMI dates) because teams mistake them for delighters.
Strategy: Deprioritize and cut these features. Reallocate engineering resources to Performance or Basic Needs.

The Kano Decay Effect: How Time Shifts Expectations

A critical dimension of the Kano Model is that **customer expectations decay over time**. What is considered a Delighter today will inevitably become a Basic Need tomorrow as technology matures and competitors copy it.

Paytm Soundbox: When Paytm launched the merchant Soundbox in 2020 (which reads out payment confirmations aloud), it was a massive Delighter for busy street merchants who could not stop to check their phones. By 2024–2026, the Soundbox has transitioned into a strict Basic Need (threshold feature); any merchant app trying to acquire sellers without instant audio feedback is ignored.
UPI credit lines (RuPay on UPI): Having credit card limits accessible via UPI scans was a major delighter in early 2024. By 2026, it is rapidly moving to a Performance standard that Indian credit-first consumers expect as table stakes.
UPI Auto-retry: Automatic routing across backup bank handles to retry a failed transaction was once a delighter. Now, users expect seamless transaction processing as a baseline.

Product teams must run Kano surveys every 12 to 18 months to map this decay and ensure their product investments match current expectation zones.

The Kano Survey Method

To run a Kano audit, present users with functional and dysfunctional questions for each feature:

Functional question: "How do you feel if this feature IS present?" (e.g. single-tap checkout via UPI Lite under ₹500 without a PIN).
Dysfunctional question: "How do you feel if this feature is NOT present?" (e.g. entering a 6-digit PIN for every single ₹20 transaction).

Users respond using a standardized 5-point scale:

I like it
I expect it
I am neutral
I can tolerate it
I dislike it

Kano Categorisation Grid (GSM Lookup)

Cross-reference the functional and dysfunctional responses to categorize each feature:

Functional → Dysfunctional ↓	1. I like it	2. I expect it	3. I'm neutral	4. I can tolerate	5. I dislike it
1. I like it	Questionable	Reverse	Reverse	Reverse	Reverse
2. I expect it	Delighter	Indifferent	Indifferent	Indifferent	Basic Need
3. I'm neutral	Delighter	Indifferent	Indifferent	Indifferent	Basic Need
4. I can tolerate	Delighter	Indifferent	Indifferent	Indifferent	Basic Need
5. I dislike it	Performance	Basic Need	Basic Need	Basic Need	Questionable

Worked Example: Kano Analysis for a Lending App

An audit of a digital consumer credit platform reveals the following categorizations:

Feature Name	Kano Classification	Prioritisation Decision
Loan disbursement under 10 mins	Must-Have	Non-negotiable. If bank APIs drop, build queued retries immediately.
Flexible repayment schedules	Performance	Optimize continuously. More options directly reduce customer drop-off.
One-tap bank mandate setup	Delighter	High satisfaction boost. Drives conversions u/s RBI mandate limits.
Dark mode interface	Indifferent	Cut. Does not impact conversions or repayments in this category.

Step-by-Step Checklist: Running a Kano Audit

[ ] Define Feature Candidates: Select 5–10 roadmap features that represent significant design or engineering work.
[ ] Draft Functional/Dysfunctional Pairs: Write functional and dysfunctional questions, avoiding loaded words.
[ ] Deploy Survey to Core Cohorts: Distribute the survey to at least 100 active users, targeting different demographics (e.g. Metro vs Tier 2/3).
[ ] Map the Responses: Cross-reference user responses using the lookup grid and sum the totals for each category.
[ ] Seal Must-Haves and Cut Indifferents: Direct your team to fix failing Basic Needs immediately, and purge all Indifferent features from the sprint backlog.

Ready to Audit Your Product Roadmap?

We help tech teams run structured Kano audits, identify roadmap bloat, and reallocate resources to delighters that drive real growth. Book a strategy session.

Book a Free Call

Related Resources

Product Analytics Guide