Kano Model: A Founder's Guide to Prioritizing Features

The Kano model is a framework, developed by Noriaki Kano, that sorts product features by how they affect customer satisfaction. It maps features into categories — must-be, one-dimensional, attractive, indifferent, and reverse — using paired survey questions, so you invest where satisfaction actually moves instead of guessing.

Quick Answer: The Kano model classifies features by their effect on satisfaction, not by raw importance. Must-be features cause dissatisfaction when absent but never delight. One-dimensional features scale satisfaction with performance. Attractive features delight when present but are forgiven when missing. A short functional-plus-dysfunctional survey tells you which is which.

Founders and product managers rarely fail because they built badly. They fail because they built the wrong things in the wrong order — polishing a delighter nobody noticed while a basic expectation quietly bled trust. The Kano model exists to fix that sequencing problem. It refuses to treat every feature as equally worthy of your next sprint and instead asks a sharper question: what does this feature actually do to how a customer feels?

This guide walks through every Kano category, the survey mechanics that assign features to them, how to read the resulting chart, and the mistakes that quietly break the analysis. By the end you should be able to run a lightweight Kano study on your own roadmap and defend the priorities it produces.

What are the Kano model categories?

The Kano model uses five feature categories, each defined by a different relationship between how much of a feature you deliver (functionality) and how satisfied customers feel. Two categories are strategic dead ends you want to catch early, and three are the levers you actually manage.

The whole framework rests on one insight that separates it from a simple priority list: satisfaction is not linear, and it is not the same shape for every feature. Adding more of a basic expectation cannot make anyone happy — it can only stop them being unhappy. Adding an unexpected delight can thrill someone even in small doses. Kano gives each of these behaviors a name.

Here is the full set, described qualitatively before we work through each one in depth. Read the middle column as "what happens to satisfaction as you deliver more of this feature."

The practical takeaway from this table is that "important" is the wrong axis. A must-be feature is critically important yet delivers zero upside satisfaction — its entire job is to avoid a disaster. A delighter may look trivial on a spec sheet yet be the reason someone switches to you. You cannot see these differences by ranking features on a single importance scale, which is exactly the gap Kano fills.

What do must-be, one-dimensional, attractive, indifferent, and reverse mean?

Each Kano category prescribes a different investment strategy: some features you must not skimp on, some you compete on, some you sprinkle sparingly, and some you should actively avoid building. Understanding the behavior of each is what turns Kano from a chart into a decision.

Must-be features are the price of entry

Must-be (also called basic or threshold) features are the expectations customers assume silently and only notice when they are missing. Their presence buys you nothing; their absence poisons everything.

Think of a login that remembers your session, a checkout that charges the correct amount, or an app that opens without crashing. Nobody writes a five-star review praising a crash-free launch. But a single crash on first open can end the relationship. Must-be features have a hard ceiling on satisfaction and no floor on dissatisfaction, so your job is simply to meet the standard reliably and move on. Over-investing past "it works dependably" produces no return.

One-dimensional features are where you compete

One-dimensional (performance) features move satisfaction up and down in direct proportion to how well you deliver them. More is genuinely better, and customers can feel the difference.

Load speed, battery life, storage capacity, and price all tend to behave this way — the faster, longer, larger, or cheaper you are, the happier people get, and the reverse hurts. These are the features customers actively compare across options, so they are usually where markets fight. Because the relationship is linear and visible, one-dimensional features are the safest place to make measurable, defensible investments: you can promise more and customers will notice.

Attractive features delight but are forgiven

Attractive features (delighters or exciters) generate outsized satisfaction when present but cause no dissatisfaction when absent, because customers never expected them.

These are the surprising touches — a thoughtful onboarding moment, an integration nobody asked for but everyone loves, a small piece of automation that saves an hour. Because they are unexpected, even a modest delighter can produce a disproportionate emotional payoff and become the story customers tell about you. The strategic catch is that you cannot fill a roadmap with delighters alone, and you cannot skip the basics to chase them. Delight sits on top of a foundation of met expectations, not in place of it.

Indifferent features waste your roadmap

Indifferent features barely move satisfaction whether present or absent — customers simply do not care about them one way or the other.

Every roadmap accumulates these: settings nobody opens, configuration options that matter to the team who built them and to no one else, features shipped to satisfy an internal stakeholder rather than a market. Kano's value here is defensive. Surfacing that a proposed feature is indifferent to customers is often the highest-return output of the whole exercise, because it lets you cancel work before you pay for it.

Reverse features actively hurt

Reverse features reduce satisfaction as you add more of them, because a meaningful segment of customers wants the opposite of what you are building.

Forced social features in a tool people use for focused solo work, aggressive notifications, or an "assistant" that intervenes uninvited can all land as reverse for some users. Reverse results are also a signal that your customer base is not uniform — what one segment experiences as a delighter, another experiences as an intrusion. When Kano flags a reverse pattern, treat it as a prompt to segment, not as a single verdict.

A useful way to hold all five together: must-be features prevent loss, one-dimensional features win comparisons, attractive features create loyalty, indifferent features drain your budget, and reverse features cost you customers. Your roadmap should be deliberate about the first three and ruthless about the last two.

How does the Kano survey work?

The Kano survey identifies a feature's category by asking each customer two questions about it — one functional, one dysfunctional — and reading the pair together. Neither question alone tells you anything; the diagnosis lives in the combination.

This paired structure is the mechanical heart of the model, and it is what makes Kano more rigorous than simply asking people what they want. People are bad at rating importance in the abstract and worse at predicting their own delight. But the functional/dysfunctional pair sidesteps that by forcing a customer to react to both the presence and the absence of a feature, which exposes the shape of their satisfaction rather than a flat opinion.

The functional and dysfunctional question pair

For every feature you want to classify, you ask the same two-part question:

• Functional form: "How would you feel if the product had this feature?"
• Dysfunctional form: "How would you feel if the product did not have this feature?"

Respondents answer each on a standardized five-option scale that runs roughly from "I like it that way" through "I expect it," "I am neutral," and "I can tolerate it" to "I dislike it that way." The wording matters and is easy to get wrong, so it is worth treating question design as its own step — our companion piece on how to write Kano model survey questions covers the phrasing traps that quietly corrupt results.

The trick is that the same emotional answer means different things depending on which half of the pair it belongs to. Liking a feature when it is present is expected; liking its absence is not. It is the tension between the two answers that reveals the category.

Reading the answer pairs into categories

Once you have both answers from a respondent, you cross-reference them to land on one category for that person and that feature. The logic follows an intuitive pattern:

• Someone who likes having a feature and dislikes not having it is describing a one-dimensional feature — they respond to both directions.
• Someone who is neutral or expectant about having it but dislikes not having it is describing a must-be — its absence hurts, its presence is assumed.
• Someone who likes having it but is neutral or tolerant about its absence is describing an attractive feature — upside with no penalty.
• Someone neutral in both directions is indifferent.
• Someone who dislikes having it is signaling reverse.

Here is how the same emotional reaction changes meaning across the pair. The lead-in matters: read each row as one respondent's two answers combined.

The takeaway is that a Kano category is a property of a customer-and-feature pair, not of the feature in isolation. That is why you never run Kano on one respondent. You survey a representative group, tally which category wins for each feature across everyone, and read the distribution — which is also why sampling the right people matters as much as the questions. Grounding your respondent pool in real target users, not whoever is easy to reach, is a discipline worth borrowing from any complete guide to customer research for founders.

Adding a self-stated importance question

Many practitioners bolt a third question onto each pair: "How important is this feature to you?" on a simple scale. This does not change the Kano category, but it helps you break ties. When two features both land as must-be, the importance rating tells you which basic expectation customers weight more heavily, so you can sequence even within a category. Treat it as a tie-breaker, never as a replacement for the functional/dysfunctional logic.

How do you plot and read a Kano chart?

The Kano chart plots customer satisfaction on the vertical axis against feature functionality on the horizontal axis, and each category traces a distinctly shaped curve across that space. Reading the chart is really about recognizing which curve a feature sits on.

Picture a graph with an origin in the center. The horizontal axis runs from "feature absent or poorly executed" on the left to "feature fully present and well executed" on the right. The vertical axis runs from deep dissatisfaction at the bottom to high satisfaction at the top. Every category is a different line drawn through that field.

• The one-dimensional line is a straight diagonal through the origin: as functionality rises, satisfaction rises with it in equal measure, and it dips symmetrically below the axis when functionality drops.
• The must-be line is a curve that lives mostly in the lower half. Deliver the feature and you climb toward neutral but never break into real satisfaction; fail to deliver and you plunge. It flattens as it approaches the top — you cannot buy delight with a basic.
• The attractive line is a curve that lives mostly in the upper half. Its absence barely registers below neutral, but its presence arcs steeply upward toward delight. It flattens near the bottom — nobody is angry it was missing.
• Indifferent features hug the horizontal axis, staying near neutral regardless of functionality.
• Reverse features slope the wrong way, descending as functionality increases.

Why the curves shift over time

The single most important thing the chart teaches is that categories are not permanent. Delighters decay into basics as the market catches up. A feature that thrills customers today becomes an expectation tomorrow and a silent must-be the day after, once every competitor has copied it and customers stop noticing.

The classic pattern: what was an attractive feature a few years ago is a table-stakes must-be now, and its absence would trigger dissatisfaction that its presence once inspired delight. This decay is why Kano is not a one-time exercise. Re-running the survey periodically shows you which of yesterday's delighters have slid into the basics tier, which is your cue to invest in the next round of delighters before your differentiation quietly erodes into the baseline.

Turning the chart into a roadmap decision

Reading the chart gives you a priority sequence rather than a single ranked list:

1. Secure every must-be first. A gap here caps your ceiling no matter how good everything else is.
2. Choose your one-dimensional battles. Decide which performance features you will compete on and commit to being visibly good at them.
3. Layer in a few attractive features. Once the foundation holds, delighters are where differentiation and word of mouth come from.
4. Cut the indifferent and reverse features. Redirect that capacity to the first three tiers.

Kano tells you the shape of each feature's payoff; you still supply the strategy for how many battles to fight and where to differentiate. If you want to compare this satisfaction-shaped approach against a simpler bucketing method, our breakdown of the Kano model versus MoSCoW prioritization lays out when each one earns its keep.

What are the most common Kano model mistakes?

The most common Kano mistakes come from treating it as a ranking tool, surveying the wrong people, or freezing the results in time. Each one quietly converts a rigorous method into false confidence.

Surveying people who are not your customers. Because Kano categories belong to a customer-and-feature pair, the answer depends entirely on who answers. Run the survey on a convenience sample, or on prospects who will never buy, and you get a clean-looking chart that describes the wrong market. Define your target segment before you write a single question.

Confusing must-be with unimportant. A must-be feature scores no satisfaction upside, which can make it look low-value on a naive reading. It is the opposite: must-be features are non-negotiable, and skipping one to chase a delighter is how founders build charming products that customers cannot trust. Satisfaction upside and strategic importance are different measurements.

Chasing delighters before the basics hold. Delighters are seductive because they generate the strongest emotional response. But a delighter stacked on top of a broken must-be is worthless — the excitement evaporates the moment a basic expectation fails. Sequence matters: foundation first, delight second.

Treating the classification as permanent. Because delighters decay into basics, a Kano study has a shelf life. Founders who run it once and cite the same chart two years later are steering by an outdated map. Re-survey on a cadence that matches how fast your market moves.

Over-engineering the analysis. Kano has formal scoring methods, satisfaction and dissatisfaction coefficients, and discrete-versus-continuous variants that can absorb weeks. For most founders, the plurality-vote version — tally which category wins for each feature and read the pattern — is enough to make a materially better roadmap decision. Precision beyond the point of the decision is wasted motion.

Ignoring the reverse and indifferent signals. Teams love the must-be, performance, and attractive story and skim past the two categories that tell them to stop building. Yet cancelling an indifferent feature or catching a reverse feature before launch is often the highest-return outcome of the whole study. Read the losers as carefully as the winners.

Key Takeaways

• The Kano model sorts features by their effect on satisfaction, not by importance. Developed by Noriaki Kano, it plots satisfaction against functionality to reveal that different features follow completely different payoff curves.
• There are five categories: must-be, one-dimensional, attractive, indifferent, and reverse. Each prescribes a different strategy — meet basics reliably, compete on performance, layer in delight, and cut what customers do not want.
• Must-be features prevent loss and attractive features create loyalty, but they are not interchangeable. A delighter cannot compensate for a broken basic, so sequence your roadmap foundation-first.
• The paired functional and dysfunctional survey is what makes Kano rigorous. Asking how customers feel about both having and not having a feature exposes the shape of their satisfaction, which a single importance rating never could.
• A Kano category belongs to a customer-and-feature pair, not to a feature alone. That is why you survey a representative sample of real target users and read the distribution rather than one opinion.
• Delighters decay into basics over time. Yesterday's attractive feature becomes today's expectation, so Kano is a recurring study, not a one-time chart.
• The reverse and indifferent categories are often the most valuable output. They tell you what to stop building, which protects your roadmap capacity better than any ranked wishlist.

Frequently Asked Questions

What is the Kano model in simple terms?

The Kano model is a way to classify product features by how they affect customer satisfaction. Developed by Noriaki Kano, it recognizes that some features only prevent unhappiness (basics), some scale satisfaction with performance, and some create surprise and delight. It uses a short paired survey to sort features into those categories so you build in the right order.

What are the five categories of the Kano model?

The five categories are must-be (basic expectations that cause dissatisfaction when missing), one-dimensional (performance features where more is better), attractive (delighters that thrill when present but are forgiven when absent), indifferent (features customers do not care about), and reverse (features that reduce satisfaction because customers want the opposite).

How is a Kano survey structured?

A Kano survey asks two questions per feature: a functional question about how the customer would feel if the product had the feature, and a dysfunctional question about how they would feel without it. Both use a standardized five-option scale, and the pair of answers is cross-referenced to assign the feature to a category for that respondent.

Do Kano categories change over time?

Yes. Attractive features tend to decay into must-be features as competitors copy them and customers come to expect them. A feature that delights today can become a silent basic within a few years. This is why the Kano survey should be re-run periodically rather than treated as a permanent classification.

When should a founder use the Kano model instead of a simpler prioritization method?

Use Kano when you have customer access and need to understand not just which features matter but how they affect satisfaction — especially when deciding where to differentiate versus where to simply meet expectations. For quick internal triage with limited research, a lighter bucketing method can be faster; the tradeoff is covered in our Kano-versus-MoSCoW comparison.

How many features can I put in a single Kano survey?

Practically, keep it short. Each feature adds two questions plus an optional importance rating, and respondent fatigue degrades answer quality quickly. Most founders get reliable results by limiting a single survey to a focused set of candidate features rather than an entire backlog, then running follow-up rounds for the rest.