Kano Model: How to Prioritize Customer Satisfaction

The Kano model is the framework that separates features customers expect from the ones that genuinely excite them. Without it, product and process teams spend budget on improvements that don't move satisfaction at all.

What Is the Kano Model?

The Kano model is a product prioritization framework developed by Professor Noriaki Kano of Tokyo University of Science in 1984. It maps product or service features to their effect on customer satisfaction, helping teams decide what to build, improve, or drop.

Kano's insight was simple but counterintuitive: not all features affect satisfaction the same way. Some features are basic expectations. Others drive satisfaction linearly. A third group delights customers precisely because they didn't expect them. His 1984 paper, "Attractive Quality and Must-Be Quality," introduced the categories that product teams still use today.

The model asks teams to stop treating all features as equal priorities and instead classify each one by how customers actually respond to its presence or absence.

Key Facts

Professor Noriaki Kano published the foundational paper "Attractive Quality and Must-Be Quality" in 1984, introducing the framework at Tokyo University of Science. It remains one of the most cited works in quality management literature.

80% of features in the average software product are rarely or never used, according to the Standish Group's CHAOS Report and Pendo's 2019 State of Product Leadership research. The Kano model is one of the primary tools teams use to cut this waste.

Kano analysis is now embedded inside ISO 9001 and Six Sigma curricula worldwide, reflecting its acceptance as a standard quality-planning tool rather than a niche academic method.

The 5 Categories of the Kano Model

Kano defined five ways a feature can relate to customer satisfaction. Three are actionable for most teams; two are worth knowing so you can avoid them.

The most valuable strategic insight from this table is the decay pattern for Attractive features. Today's delighter becomes tomorrow's basic expectation. This is why companies like Apple and Spotify ship something new every cycle: the delight curve is always decaying toward Must-Be.

The Kano Model Graph

The Kano graph plots customer satisfaction on the vertical axis (from "Very Dissatisfied" at the bottom to "Very Satisfied" at the top) and degree of implementation (or functionality) on the horizontal axis (from "Not Implemented / Absent" on the left to "Fully Implemented / Present" on the right).

Three curves run across this space:

Must-Be curve. Starts in the bottom-left and flattens into neutral satisfaction on the right. Fully implemented means the customer barely notices. Not implemented means dissatisfaction falls sharply. The curve never climbs into delight territory.

One-Dimensional curve. A diagonal running from bottom-left (absent = dissatisfied) to top-right (fully present = very satisfied). This is the linear trade: invest more, get more satisfaction in return. Budget decisions for Performance features are straightforward.

Attractive curve. Starts in neutral territory on the left (absent, but no one expects it) and curves steeply upward to the right (present = high delight). The critical characteristic: the left half of the curve sits at the zero line, not below it. Missing a Delighter doesn't hurt you. Delivering one surprises and wins customers.

The Indifferent category appears as a flat line at the zero (neutral) point across the entire graph. The Reverse category is the mirror of One-Dimensional, running from top-left to bottom-right.

Reading the graph together tells you where to invest. Features above the diagonal at low implementation cost are Delighters worth shipping fast. Features below the diagonal at high cost are Must-Bes worth meeting at minimum viable quality, not over-investing in.

How to Conduct a Kano Analysis

Running a Kano analysis takes four steps. It's more structured than a typical customer survey, because each feature gets asked twice: once positively, once negatively.

Step 1: Select Features to Evaluate

Choose 10 to 20 specific features or improvements. Vague items ("better performance") produce noisy results. Concrete items ("page load under 1 second") produce clean categorizations. Pull candidates from your backlog, customer support tickets, competitor feature lists, or your team's roadmap debates.

Step 2: Write Functional and Dysfunctional Question Pairs

Each feature gets exactly two questions:

• Functional question: "How would you feel if this feature was present?"
• Dysfunctional question: "How would you feel if this feature was absent (or removed)?"

Both questions use the same five response options:

1. I like it
2. I expect it (take it for granted)
3. I'm neutral
4. I can tolerate it
5. I dislike it

Write each pair in plain language. Avoid double negatives. Test on two or three colleagues before sending. Poor question wording is the biggest source of bad Kano data.

Step 3: Survey Customers and Categorize Responses

Collect responses from a representative sample (30 to 100 respondents is typical; more for high-stakes features). Then cross-reference each respondent's functional and dysfunctional answers using the Kano Evaluation Table:

Aggregate the categories across all respondents. The most common category for a feature is its Kano classification. When a feature splits nearly equally between two categories, that often signals a segmentation opportunity: different customer types value it differently.

Step 4: Prioritize Your Roadmap

Apply this logic:

• Must-Be features not yet met: Fix these first. They're table stakes. Failing here damages trust regardless of your Delighters.
• One-Dimensional features with a performance gap: Invest proportionally. These move satisfaction directly, so the ROI calculation is clear.
• Attractive features your competitors don't have: Ship fast. The delight window closes as the market normalizes.
• Indifferent features: Cut or defer. Redirect that budget to the above.
• Reverse features affecting a key segment: Remove or make optional.

Pair Kano prioritization with your existing frameworks. MoSCoW prioritization works well alongside Kano: Must-Be maps to "Must Have," One-Dimensional to "Should Have," Attractive to "Could Have," and Indifferent to "Won't Have."

Kano Model Example

Consider a B2B project management SaaS product evaluating its next quarter roadmap. The team surveyed 60 customers on eight potential features:

The result: the team deprioritized the color theme and music features entirely, flagged SSO as a non-negotiable for enterprise expansion, and fast-tracked the AI meeting summary as a competitive differentiator before rivals ship it.

This kind of structured evidence replaces the opinion-driven arguments that slow most roadmap reviews. It also gives the team a defensible answer when executives ask why a feature isn't in the next sprint.

Benefits and Limitations

Where the Kano model adds real value:

• Forces customer data into prioritization instead of relying on internal gut feel
• Separates "nice to have" from "table stakes" with clarity
• Identifies competitive differentiation opportunities before rivals do
• Reduces feature bloat by surfacing Indifferent categories
• Works across industries: product, service design, process management, customer experience

Where teams run into friction:

• Survey design is harder than it looks; bad question wording skews every result
• Results are a snapshot. Features decay from Attractive to Must-Be over time, so analysis needs repeating annually or after major market shifts
• Small samples produce unreliable categorizations, especially for features that split between categories
• Doesn't rank features within the same category; you still need a second tool (effort/impact matrix, value proposition canvas) to sequence them
• Customers often can't articulate what would delight them, only what they already know to expect

The Kano model works best when paired with other quality and prioritization methods. Teams running Six Sigma use Kano in the Define phase to establish Critical-to-Quality (CTQ) requirements. Total Quality Management programs use it to align improvement projects with real customer value. Value stream mapping teams use it to decide which steps in a process are worth optimizing versus eliminating.

Frequently Asked Questions

Who created the Kano model and when? Professor Noriaki Kano of Tokyo University of Science developed the model. His 1984 paper, "Attractive Quality and Must-Be Quality," introduced the framework to quality management literature. Kano was building on customer satisfaction research from the 1970s, but his categorization and graphing approach became the standard that quality practitioners worldwide now follow.

What are the 5 categories of the Kano model? The five categories are Must-Be (Basic), One-Dimensional (Performance), Attractive (Delighters), Indifferent, and Reverse. Must-Be features are expected and taken for granted. One-Dimensional features scale satisfaction linearly with investment. Attractive features surprise and delight. Indifferent features don't move satisfaction either way. Reverse features are actively disliked by some customer segments when present.

What is the difference between a functional and a dysfunctional question? A functional question asks how a customer would feel if a feature were present. A dysfunctional question asks how they'd feel if it were absent. You need both to categorize a feature correctly. A respondent who says "I like it" when present and "I dislike it" when absent has given you a One-Dimensional result. A respondent who says "I like it" when present but is "neutral" when absent has given you an Attractive result. The pairing is what makes Kano analysis more precise than a single satisfaction rating.

Do Attractive features stay Attractive forever? No. This is one of the most important and underused insights from the model. Attractive features decay over time. They shift from Attractive to One-Dimensional (as customers start expecting them) and eventually to Must-Be (as they become table stakes across the market). Early smartphone touchscreens were Attractive in 2007; by 2012 they were Must-Be. AI-generated content summaries are Attractive for many SaaS tools today; they won't stay that way. The implication: ship Delighters fast and keep surveying customers to track the decay.

How does the Kano model compare to MoSCoW prioritization? Both frameworks help teams decide what to build. MoSCoW prioritization classifies features into Must Have, Should Have, Could Have, and Won't Have, based on team judgment and project constraints. Kano classifies features based on measured customer response data. They're complementary: Kano tells you how customers feel, MoSCoW helps you make the delivery decision given time and budget. Many product teams run Kano analysis first to inform their MoSCoW decisions.

The Kano model doesn't tell you how fast to ship or how much to spend. But it does tell you which direction matters to customers, and that's the question most roadmap debates never answer with real data. Start with a small survey, categorize your top ten backlog items, and you'll likely find two or three features the team has been arguing about that turn out to be Indifferent to the people who actually use the product.