Kano Model: Categories, Survey and Roadmap

10 min read ยท 2026-10-25

The Kano model is a way to prioritize product features by how they change customer satisfaction. You ask customers two questions about each feature. Dr Noriaki Kano created the model in 1984. It sorts features into must-be, performance, attractive, indifferent and reverse. That shows you which features stop complaints, which ones win customers and which ones nobody needs.

This guide covers the whole method in order. It explains each category and the satisfaction curve, and gives you kano model survey questions to copy. It walks through the full evaluation table and shows how to handle split answers. It ends with a worked example that becomes a quarterly roadmap.

The roadmap at a glance

Goal: Run a Kano analysis on your candidate features and turn the results into a balanced roadmap for next quarter. Duration: About 4 weeks of research, then one 13-week quarter

  1. Pick and describe the features (Days 1 to 3)

    Choose a short list of features you can describe clearly.

    • Shortlist the features you are really unsure about, not the whole backlog.
    • Write one sentence per feature that says what it does for the customer, not its internal name.
    • Add one or two features that already exist, as a check on the method.
    • Pick the one customer segment you will survey first.

    Milestone: A short feature list, each item in one plain sentence, plus one named segment.

  2. Write and pilot the survey (Days 4 to 7)

    Build the paired questions and test them on real people.

    • Write a functional question (feature present) and a dysfunctional question (feature absent) for each feature.
    • Use the same five answers for both questions.
    • Add an optional "How important is this to you?" question to help break ties.
    • Run the survey with a few customers and rewrite any question they misread.

    Milestone: A piloted survey where testers understand every question on the first read.

  3. Collect answers (Weeks 2 to 3)

    Get answers from the right people.

    • Send the survey by email, in-app message or your research panel.
    • Track responses by segment so one group does not drown out the others.
    • Book short calls with a few respondents whose answers surprise you.
    • Stop when new answers no longer change any feature's top category.

    Milestone: A stable response set plus notes from the follow-up calls.

  4. Classify with the evaluation table (Days 22 to 25)

    Turn each pair of answers into a category.

    • Map every answer pair to a category with the evaluation table.
    • Give each feature its most frequent category.
    • Calculate the Better and Worse coefficients for each feature.
    • Flag features with split results and check them by segment.

    Milestone: Every feature has a category, two coefficients and a note if results are split.

  5. Turn categories into a roadmap (Days 26 to 28)

    Order the work by category, then by cost.

    • Put missing must-be features first.
    • Rank performance features by coefficient and effort.
    • Keep room for one or two attractive features.
    • Park indifferent features. Make reverse features optional or drop them.

    Milestone: A quarter plan with the basics covered, the top performance work scheduled and one delighter.

  6. Ship, then re-check (The quarter, then repeat)

    Deliver and keep the classification up to date.

    • Ship basics early in the quarter, before anything new.
    • Watch support tickets for complaints about the basics you fixed.
    • Plan a repeat survey, because categories move over time.

    Milestone: The quarter's roadmap is shipped and the next survey is on the calendar.

What the Kano model categories mean

Each category describes how satisfaction reacts when a feature is there and when it is not. The labels change from source to source. Must-be features are also called basic or threshold features. Attractive features are also called delighters or excitement features.

  • Must-be (basic): customers expect it. If it is missing, they are frustrated. If it is there, nobody notices. Think of password reset in a web app.
  • Performance (one-dimensional): the better it works, the happier people are. Faster sync and better search results are typical examples.
  • Attractive (delighter): customers do not expect it, so its absence costs nothing, but its presence creates delight.
  • Indifferent: it has no effect either way. It is usually safe to leave off the roadmap.
  • Reverse: some customers would rather not have it. Make it optional or reconsider it.
  • Questionable: the answers contradict each other, which usually means the question was unclear.

The Kano satisfaction curve, read simply

The classic Kano diagram has two axes. The horizontal one shows how fully a feature is delivered. The vertical one shows how satisfied the customer is. Each main category draws its own line.

Must-be features curve up from deep dissatisfaction to neutral, then flatten. Doing them better than "working" earns you nothing. Performance features follow a straight diagonal, so each improvement adds satisfaction. Attractive features start at neutral and curve sharply upward, so a little effort can create a lot of delight. Indifferent features stay flat on the middle line. This is why months spent polishing a basic feature rarely move the needle, while a missing basic can undo everything else.

Kano model survey: the questions to ask

For each feature you ask the same pair of questions. Describe the benefit, not the feature name. The dysfunctional question simply describes the feature as absent. It is not a negative version of the first question.

Both questions use the same five answers: I like it, I take that for granted, I don't care, I can tolerate it, I dislike it. Some teams use another scale, from "Not necessary" to "Very necessary" plus "Indifferent". Whatever you choose, keep one scale for the whole survey. A short image or a one-line example per feature helps people picture what they are rating. An open question at the end ("Anything we missed?") often turns up basics you forgot to test.

  • Functional: "If you could repeat a task every week automatically, how would you feel?"
  • Dysfunctional: "If you had to re-create a weekly task by hand each time, how would you feel?"

The Kano evaluation table, cell by cell

The evaluation table crosses the answer to the functional question (feature present, in rows) with the answer to the dysfunctional question (feature absent, in columns). Find the row and column for each respondent's answer pair, and the cell gives the category.

The table uses six letters: M = must-be, O = performance (one-dimensional), A = attractive, I = indifferent, R = reverse, Q = questionable. Here is every cell, row by row.

Count the categories for each feature across all respondents. The most frequent category wins.

  • Functional "I like it": with "I dislike it" when absent, the feature is performance (O). With "I take that for granted", "I don't care" or "I can tolerate it" when absent, it is attractive (A). With "I like it" when absent, the result is questionable (Q).
  • Functional "I take that for granted", "I don't care" or "I can tolerate it": with "I dislike it" when absent, the feature is must-be (M). With any of the same three middle answers when absent, it is indifferent (I). With "I like it" when absent, it is reverse (R).
  • Functional "I dislike it": with "I dislike it" when absent, the result is questionable (Q). With any other answer when absent, it is reverse (R).

How to analyze Kano results when answers split

Two coefficients help you compare features inside the same category. Better = (A + O) / (A + O + M + I) shows how much satisfaction rises when the feature is there. Worse = -(O + M) / (A + O + M + I) shows how much dissatisfaction you risk if it is missing. A, O, M and I are the counts of attractive, performance, must-be and indifferent answers. Reverse and questionable answers stay out of both formulas.

When two categories are close, first split the results by segment. New users and power users often see the same feature differently. If the split remains, choose the category that hurts more if you get it wrong: must-be before performance, performance before attractive. Many questionable answers on one feature mean you should rewrite the question, not interpret it.

Worked example: six features for an imaginary to-do app

This example is invented to show the method. It uses 20 imaginary respondents, and each feature adds up to 20 answers. The counts are given in the order M, O, A, I, R, Q.

The resulting quarter plan: Month 1 fixes recurring tasks. Month 2 speeds up sync. Month 3 ships the weekly summary as the one delighter. Search quality is next in line for the following quarter. Badges are parked. Auto-reordering gets five interview calls before anyone builds it, and if it ships, it ships as an option users can turn off.

  • Recurring tasks (M 9, O 6, A 3, I 2, R 0, Q 0), must-be: Better = (3 + 6) / 20 = 0.45. Worse = -(6 + 9) / 20 = -0.75. Few people will praise it, but many will be unhappy without it. Leaving it out is costly.
  • Sync speed across devices (M 5, O 10, A 3, I 2, R 0, Q 0), performance: Better = 13/20 = 0.65, Worse = -15/20 = -0.75. It is the strongest performance feature: faster is clearly better.
  • Search quality (M 4, O 9, A 2, I 5, R 0, Q 0), performance: Better = 11/20 = 0.55, Worse = -13/20 = -0.65. It is also performance, but with a lower Better than sync, so it comes second.
  • Weekly review summary (M 1, O 2, A 10, I 7, R 0, Q 0), attractive: Better = 12/20 = 0.60, Worse = -3/20 = -0.15. It delights a group of users and costs little if it is missing.
  • Streak badges (M 0, O 1, A 4, I 15, R 0, Q 0), indifferent: Better = 5/20 = 0.25, Worse = -1/20 = -0.05. Mostly indifferent.
  • Automatic task reordering (M 0, O 1, A 7, I 5, R 6, Q 1), split between attractive and reverse: 6 reverse and 1 questionable answer leave 13 answers in the formulas. Better = 8/13 = 0.62, Worse = -1/13 = -0.08. The coefficients look good, but 7 attractive against 6 reverse is a real split.

From Kano results to your roadmap

Category gives you the order, and effort decides the timing. A cheap must-be gap goes in right away. An expensive delighter needs a strategic reason. A sensible default for one quarter is all missing basics, the two or three performance features with the best Better score for their effort, and one or two attractive features at most.

Put indifferent features in a "not now" column instead of deleting them, so the discussion does not come back every sprint. Next to each roadmap item, write its category and coefficients, so stakeholders can see why it is there.

Kano vs RICE, MoSCoW and value vs effort

Kano tells you what kind of value a feature brings. It does not score that value against cost. RICE scores Reach, Impact, Confidence and Effort. MoSCoW sorts items into Must have, Should have, Could have and Won't have. A value vs effort matrix plots each idea on two axes.

They work well together. Use Kano results to inform the Impact score in RICE, or to back up which items deserve "Must have" in MoSCoW. Use value vs effort for the final order within each Kano category.

When to use the Kano model, and its limits

Kano fits best when you have customers to ask, a shortlist of uncertain features and a decision big enough to justify a survey. It fits poorly when you have no users yet, when a feature is hard to explain in one sentence, or when you need an answer by tomorrow.

Its limits are real. Long surveys tire people, so keep the feature list short. Stated feelings are not behavior, so check surprises against usage data. Categories also move over time. Yesterday's delighter becomes today's performance feature and eventually a basic, so treat each result as a snapshot and repeat the survey.

Common mistakes to avoid

  • Naming features in internal jargon gives you noisy answers, so describe the benefit in customer words.
  • Writing the dysfunctional question as a negative of the functional one confuses people, so simply describe the feature as absent.
  • Mixing very different segments hides real splits, so analyze each segment on its own.
  • Filling the quarter with delighters while basics are broken frustrates users, so close must-be gaps first.
  • Treating Kano results as permanent ignores category drift, so schedule a repeat survey.
  • Ranking by category alone ignores cost, so add effort estimates before you lock the roadmap.

Frequently asked questions

What is the Kano model?

It is a prioritization method created by Dr Noriaki Kano in 1984. It classifies product features by how their presence or absence affects customer satisfaction. Teams use it to decide which features to build first.

What are the 5 categories of the Kano model?

They are must-be, performance, attractive, indifferent and reverse. A sixth result, questionable, flags contradictory answers. The first three usually drive roadmap decisions.

How do you run a kano model survey?

For each feature, ask how the customer would feel if it were present and how they would feel if it were absent. Both questions use the same five answers. Then map each answer pair to a category with the evaluation table.

How do Kano categories change over time?

As customers get used to a feature, their expectations rise. A delighter turns into a performance feature and later into a basic. Repeat the survey regularly so your roadmap does not rely on old categories.

Is the Kano model better than RICE or MoSCoW?

They answer different questions, so neither one replaces the other. Kano explains the type of satisfaction a feature creates, while RICE and MoSCoW rank or bucket work. Many teams use Kano results to inform their RICE or MoSCoW decisions.

Generate this roadmap with AI