Kano model: learn how features affect customer satisfaction

The Kano model separates features that prevent dissatisfaction from features that create satisfaction. That distinction helps a team recognize table stakes, improvements, and potential delighters—but it does not replace product strategy or effort estimates.

What is the Kano model?

Professor Noriaki Kano and his colleagues introduced the model in the 1980s to explain why quality and satisfaction do not always move in a straight line.

Fixing a missing basic can remove frustration without creating delight. Improving a performance feature can steadily increase satisfaction. An unexpected capability can delight people even though nobody was upset before it existed.

Kano research turns that idea into paired survey questions. It asks how someone feels when a feature is present and how they feel when it is absent. The answer pair is more informative than a single importance score because presence and absence can have different effects.

The five Kano feature categories

Categories are not permanent labels attached to a feature. They can change by audience, use case, product maturity, and time. A capability that once felt surprising may become an expected basic after competitors adopt it.

How a Kano survey works

For every feature, ask two questions:

1. Functional: How would you feel if the product had this feature?
2. Dysfunctional: How would you feel if the product did not have this feature?

A standard response scale is:

• I would like it.
• I expect it.
• I am neutral.
• I can live with it.
• I would dislike it.

The feature description must stay identical in both questions. Write a capability someone can picture, such as “schedule a PDF report to arrive by email every Monday,” rather than “better reporting.”

The answer pair maps to an evaluation table. Some pairs are markedquestionable rather than one of the five feature categories—for example, contradictory answers that may signal confusion or careless responding. Review those patterns instead of hiding them.

How to analyze Kano responses

Start with the category distribution

Report the number or percentage of answers in each category, not only the most common label. A feature with a narrow plurality is less clear than one with a strong, consistent classification.

Calculate satisfaction coefficients carefully

Kano analysis often adds two coefficients. Using A for attractive, O for one-dimensional, M for must-be, and I for indifferent responses:

• Better: (A + O) ÷ (A + O + M + I)
• Worse: −(O + M) ÷ (A + O + M + I)

Better approaches 1 when presence has stronger upside. Worse approaches −1 when absence has stronger downside. Reverse and questionable answers are normally excluded from these formulas, so report their counts separately.

Look for segment differences

Administrators, buyers, and daily users may classify the same feature differently. Compare only segments defined before analysis and supported by enough responses. Otherwise, chance patterns can look strategic.

A simple Kano result

The following example shows how to discuss results without pretending the dominant category is the whole story:

These numbers are illustrative. They show the conversation the analysis enables: protect the baseline, decide how far to improve performance, and test whether a potential delighter deserves investment.

How to use Kano results in prioritization

1. Protect must-be quality. Missing basics create downside, but polishing them beyond expectation may have limited satisfaction return.
2. Choose a competitive performance level. More is not automatically worth the cost; understand where meaningful gains flatten.
3. Test attractive ideas as bets. A delighter still needs a clear problem, feasible solution, and business case.
4. Challenge indifferent work. Check whether the audience or description was wrong before removing it from consideration.
5. Design for reverse preferences. Segmentation, configuration, or a simple default may serve both groups.

Add effort, risk, strategic fit, accessibility, revenue, and evidence from actual behavior. Kano is a customer-satisfaction lens, not a complete roadmap formula.

If the team instead needs a relative ranking, use MaxDiff. If features and price must be traded as complete offers, use conjoint analysis.

Common Kano survey mistakes

• Testing a slogan instead of a feature. Everyone needs to evaluate the same concrete capability.
• Changing wording between the pair. The only intended change is presence versus absence.
• Asking people without relevant experience. An audience that cannot imagine the feature will produce neutral or noisy answers.
• Making the survey exhausting. Each feature creates two questions. Pilot completion time and split the study when attention fades.
• Reporting only the winning category. Preserve the full distribution, reverse answers, questionable answers, and uncertainty.
• Treating categories as timeless. Repeat research when the audience, market, or product expectation changes materially.

How to run a Kano study with SenseFolks

FeaturePriority supports Kano, MaxDiff, and Bradley-Terry methods. Begin with a small, decision-ready list rather than moving an entire backlog into the survey.

1. Add the website where the relevant audience will see the survey.
2. Create a FeaturePriority survey and select Kano.
3. Describe each feature in plain, concrete language.
4. Pilot both sides of every question pair.
5. Embed the survey after users have enough context to answer.
6. Review distributions and coefficients, including reverse and questionable responses.
7. Combine the result with effort and strategy before changing the roadmap.

See the FeaturePriority reference for configuration and the guide to in-product surveys for placement advice.

Kano model questions, answered