Kano Model: An S-Tier Behavioral Designer’s Guide

Add a feature and nobody says thank you. Remove it and the whole account churns. Every product team has felt this and most read it as a fluke. It is not a fluke. It is a law, and a Japanese quality engineer named Noriaki Kano wrote it down in 1984.

Here is the trap it exposes. We assume satisfaction and dissatisfaction sit on one line, like a thermostat: turn a feature up and the needle slides from unhappy toward happy. Kano’s finding is that some features do not work like a thermostat at all. Fix them and you get nothing. Break them and you get a riot. Other features are the reverse: their absence costs you nothing and their presence delights. Satisfaction and dissatisfaction are two different dials, and most roadmaps are built as if there were only one.

That single reframe is worth more than most of what passes for prioritization. It tells you which features are worth polishing, which are worth competing on, and which are worth a bet. It also carries a warning that almost nobody who cites Kano bothers to read, and that warning is the reason half of all Kano studies are quietly wrong within a year.

I have spent two decades designing motivation into products, chasing the exact feeling Kano called “attractive quality.” So I want to give you the model straight, including the part where it turns on the people who use it lazily. My own field included.

Speed Run Notes

• Kano’s core discovery: satisfaction and dissatisfaction are two separate axes, not one. Removing a dissatisfier does not create satisfaction. Killing every bug leaves you with a product nobody hates and nobody loves.
• Features sort into three live categories. Must-be (expected, punished only when absent), Performance (linear, more is better), and Attractive (delighters that thrill when present and cost nothing when missing). Two more, Indifferent and Reverse, catch the rest.
• The load-bearing warning everyone skips: categories decay. Today’s delighter becomes tomorrow’s expectation. A phone camera was a delighter in 2007 and is a must-be now. Every Kano study has a shelf life.
• Must-be quality is pure Core Drive 8 (CD8): Loss & Avoidance. You feel it only when it breaks. That asymmetry is loss aversion, the same engine behind why losing $100 hurts more than finding $100 feels good.
• A delighter is a Core Drive 7 (CD7): Unpredictability & Curiosity event, a positive violation of expectation. Hedonic adaptation is what turns that CD7 surprise into a CD8 requirement. The Core Drive itself migrates.
• The measurement trick is a paired functional/dysfunctional question that surfaces must-be needs people never think to mention because they take them for granted. That is genuinely clever, and it measures what people say, not what they do.

Author Credibility: Yu-kai Chou

Yu-kai Chou created the Octalysis Framework after studying gamification since 2003 — years before the term entered mainstream vocabulary. As a Human-Systems Architect & Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.

Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.

His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and Google Scholar — with 3,700+ more academic publications. Explore his books here.

What Is the Kano Model?

The Kano model is a way of sorting the features of a product by how they affect customer satisfaction. Its central claim is that features do not all behave the same way. Some earn you nothing when present and cost you dearly when absent. Some pay off in direct proportion to how well you deliver them. And some produce delight out of nowhere while their absence goes unnoticed. Put a name on each behavior and you can stop treating your backlog as a flat list of equally worthy ideas.

Noriaki Kano, a professor of quality management at the Tokyo University of Science, published the idea in 1984 with three co-authors under the title “Attractive Quality and Must-Be Quality.” For years it lived only in Japanese quality-engineering circles. It reached the West in the 1990s, got adopted by product managers who had never heard the word quality used the way an industrial engineer means it, and has been a fixture of feature prioritization ever since.

The reason it stuck is the diagram. Kano drew a two-dimensional chart. The horizontal axis runs from a feature being completely absent or broken on the left to being fully and well implemented on the right. The vertical axis runs from deep dissatisfaction at the bottom to delight at the top. Then he plotted different kinds of features as different curves across that space, and the curves are not parallel. That is the whole insight in one picture: the relationship between how good a feature is and how happy it makes people depends entirely on what kind of feature it is.

Here is the part that gets lost when Kano becomes a slide in a workshop. This is not a fixed taxonomy of features. It is a snapshot of a relationship at a moment in time, and the relationship moves. A feature is not a delighter the way an element is gold. It is a delighter today, for this market, until enough competitors ship it that customers start expecting it. Miss that, and you will run a beautiful Kano survey, laminate the results, and be quietly wrong about your own market within a year.

The Origin: A Better Answer to Herzberg

Kano did not invent the idea that satisfaction and dissatisfaction are separate. He borrowed it, upgraded it, and made it measurable.

The borrowed part came from Frederick Herzberg. In the late 1950s Herzberg studied what made people satisfied and dissatisfied at work and reached a conclusion that sounded like a contradiction: the things that caused dissatisfaction and the things that caused satisfaction were not the same things. Bad pay, bad conditions and bad management made people miserable, but fixing them only brought people up to neutral. Genuine satisfaction came from a different set of factors entirely, like achievement and recognition. He called the first set hygiene factors and the second set motivators. I have written a full breakdown of the Two-Factor Theory, because the asymmetry it describes is one of the most useful ideas in all of behavioral design.

Kano’s move was to take Herzberg’s asymmetry out of the human-resources department and point it at products. If a clean office is a hygiene factor for an employee, then a phone that reliably makes calls is a hygiene factor for a customer. Nobody praises a phone for making calls. They abandon it when it fails to. Kano saw that the same two-dial logic governed product features, and then he did the thing Herzberg never fully managed: he built an instrument to measure which dial any given feature sits on.

That is the underappreciated part of the story. Plenty of thinkers have noticed that some things only matter when they are missing. Kano turned the observation into a repeatable survey that a company could run on real features with real customers and get back a category for each one. He converted a philosophical insight into an engineering tool. That is why his name is on the model and Herzberg’s is not, even though the core idea is Herzberg’s.

The Five Categories of Quality

Kano’s original paper named three categories. Two more got added as the model matured. All five earn their place, and confusing them is the most common way teams misuse the model.

1. Must-Be Quality (the price of admission)

Must-be features are the ones customers assume without thinking. When they are present and working, satisfaction does not rise at all, because their presence was never in question. When they are absent or broken, dissatisfaction plunges. The curve lives almost entirely in the lower half of the chart: you can do everything right and only ever climb back up to neutral.

Brakes on a car. A hotel room with a locking door. A login page that accepts your correct password. Nobody has ever posted a five-star review that reads “the brakes stopped the car.” They post one-star reviews when the brakes do not. Must-be quality is the tax you pay to be allowed in the market, and its defining property is that it can only ever hurt you. The ceiling on a perfectly executed must-be feature is that the customer feels nothing.

2. One-Dimensional Quality (the axis you compete on)

One-dimensional features, also called performance features, behave the way our thermostat intuition expects. More is better, less is worse, and satisfaction tracks fulfillment in a roughly straight diagonal line. These are usually the things customers will name if you ask them what they want, because they are the conscious, spoken needs.

A car’s fuel economy. A laptop’s battery life. Download speed, price, storage. Improve any of these and satisfaction goes up in proportion; let them slip and it goes down. This is the category where competition actually happens, because it is the one where being better than the other product is legible to the customer. It is also the category most roadmaps over-index on, because performance features are the easiest to justify in a planning meeting. Everyone understands “faster is better.” Fewer people understand that faster stops mattering past the point the customer can perceive.

3. Attractive Quality (the delighters)

Attractive features are the ones customers do not expect and often cannot articulate in advance. When present, they produce a jump in satisfaction far out of proportion to the effort. When absent, they cost nothing, because nobody was looking for them. The curve sits in the upper region of the chart: a little bit of this feature buys a lot of delight, and its absence never registers as a complaint.

This is the category everyone wants and few teams manage on purpose. The first smartphone that let you pinch to zoom. A software company that answers a support ticket in four minutes with a human who actually solved the problem. A checkout flow that remembered your address so you did not have to. Delighters are where differentiation is born, and Kano’s most important structural claim is that delighters are the only category that can lift you meaningfully above neutral. Must-be caps out at zero. Performance climbs a line. Attractive quality is the one that produces love rather than mere absence of complaint.

4. Indifferent Quality (the features nobody cares about)

Indifferent features move satisfaction in neither direction whether they are present or absent. The customer genuinely does not care. This category is quietly the most valuable output of a Kano study, because it is where you find the work you can stop doing. Every backlog is full of features that somebody was sure mattered and the market has never once noticed. Finding them and killing them frees the budget that must-be and attractive quality actually need.

5. Reverse Quality (the features that backfire)

Reverse features make some customers less satisfied when present. More is worse. The classic cases are features that add complexity or take away control: a car that aggressively auto-brakes for a driver who wants to drive, an app that keeps “helpfully” reorganizing content the user had arranged, a form with fields the customer resents. Reverse quality is the one that punishes the “more features is always better” instinct, and it is also the reason you cannot trust a category averaged across a whole population. What delights one segment can be reverse quality for another, and the average hides the war.

There is a sixth label that appears in Kano tables, usually called Questionable, but it is not a real category of feature. It is a flag for a survey response that contradicts itself, telling you the respondent misread the question. Treat it as noise to be cleaned, not a type of quality to design for.

The Kano Questionnaire: How You Actually Measure It

The categories are the famous part. The measurement method is the clever part, and it is what separates Kano from every other prioritization framework that just asks people to rank things.

For each feature, Kano asks two questions instead of one. The first is functional: “How would you feel if the product had this feature?” The second is dysfunctional, and this is the innovation: “How would you feel if the product did not have this feature?” Each question offers the same five answers, which run from “I like it that way” through “It must be that way,” “I am neutral,” and “I can live with it,” down to “I dislike it that way.”

The pair of answers is what reveals the category. Ask only the functional question and a must-be feature looks unremarkable, because people shrug at features they already assume. It is the dysfunctional question that lights it up: they say they like having it, and then say they would strongly dislike not having it. That gap is the signature of a must-be. A delighter shows the opposite fingerprint: they love having it and feel perfectly neutral about not having it, because they never knew to want it. Cross the two answers in a lookup table and each feature falls out as Must-be, Performance, Attractive, Indifferent, or Reverse.

The reason this matters is that customers are terrible at naming their must-be needs directly. Ask someone what they want from a hotel and they will not say “a door that locks,” because it never occurs to them to mention it. The dysfunctional question drags those invisible assumptions into the open by asking about their absence, which is the only situation in which a must-be need ever becomes conscious. That is a real piece of survey design, and it is why the Kano questionnaire still gets used forty years later when trendier methods have come and gone.

What Kano Got Right

Four decades of use have been kind to the model, and it earned that longevity on three specific merits.

He broke the single-axis illusion for good. Before Kano, and honestly still today in most planning meetings, teams reason as if satisfaction were one slider. Ship enough improvements and the slider goes up. Kano’s evidence that dissatisfiers and satisfiers are structurally different forces a harder and more useful question: not “is this feature good” but “what kind of good is it, and what is the ceiling on that kind.” Killing your bugs and answering your tickets removes reasons to leave. It does not, by itself, create a reason to stay. That distinction has saved more roadmaps than any amount of velocity.

He made delight an engineering category. “Delight” is the kind of word that shows up in mission statements and never in a spec. Kano gave it a technical definition, a place on a chart, and a measurement procedure. Attractive quality is not a vibe. It is a feature whose functional answer is positive and whose dysfunctional answer is neutral, and you can test any candidate feature against that definition. Turning an aspiration into something falsifiable is exactly the move I respect most in any framework, because it means the model can be wrong, which means it can be useful.

He built the dysfunctional question. The paired-question method is a small piece of genius that surfaces needs customers cannot self-report. Most research methods can only capture what people are able to articulate. Kano’s design specifically extracts the needs people are unable to articulate, because it asks about a world in which the taken-for-granted thing is missing. That is a rare thing for a survey to do, and it is the reason a Kano study tells you things a preference ranking never will.

What Kano got most right is that he treated customer satisfaction as a structured, measurable phenomenon rather than a mood to be chased. He was a quality engineer, and he brought an engineer’s demand for measurement to a domain that mostly ran on intuition. The model has flaws, which we are about to get into, but its ambition was correct: satisfaction has structure, and structure can be studied.

Where the Kano Model Falls Apart

I reach for this model constantly, and it still has three failure modes serious enough that using it without them is a liability.

The Categories Decay, and the Model Hides It

This is the big one, and it is baked so deep that most practitioners never see it. A Kano category is not a property of a feature. It is a property of a feature at a moment, for a market, and it drifts in one direction: attractive becomes one-dimensional becomes must-be. Kano himself described this natural decline of quality over time.

The examples are everywhere once you look. A camera on a phone was an attractive feature in 2007 and is a must-be today; a phone without one is unsellable, and no phone has ever been praised for having one. Free WiFi in a hotel was a delighter, then a performance feature you compared across hotels, then a must-be whose absence generates furious reviews. A backup camera in a car walked the same path in about a decade. The delighter of one product generation is the baseline expectation of the next, because customers adapt to whatever they are given.

The danger is that the model presents its categories as if they were stable, and teams treat a Kano study as a durable truth rather than a photograph with an expiry date. A study that told you a feature was a delighter two years ago may be describing a must-be today, and you would never know from the laminated chart on the wall. Any team using Kano without a re-measurement schedule is navigating by a map of a coastline that erodes.

It Measures What People Say, Not What They Do

The Kano questionnaire is a stated-preference instrument. It asks people to predict how they would feel about a feature they may never have used, and the gap between what people predict and what they actually do is one of the most reliable findings in all of behavioral science.

This bites hardest exactly where the model is supposed to shine, on delighters. By definition, an attractive feature is one people did not know they wanted. Asking them in advance how they would feel about it is asking them to forecast a reaction to a surprise, and people are notoriously bad at that. The most transformative delighters in product history would have scored as indifferent on a survey, because respondents had no mental model for a thing that did not yet exist. Kano can validate delighters you already thought of. It is much weaker at discovering the ones you have not, and the ones you have not are the valuable ones.

It Tells You the Category, Not the Trade-Off

A Kano study hands you a set of categories and stops. It says this feature is a must-be and that one is a delighter, but it says nothing about what any of them cost to build, and prioritization is a question about return on finite resources. A cheap delighter and a ruinously expensive one land in the same box.

Used alone, the model quietly encourages a bad instinct: chase delighters, because delighters are the exciting category. But a team that pours its budget into attractive quality while a must-be feature is broken has optimized for the wrong thing, because must-be failures are the ones that cause churn. The model has no internal mechanism to stop you from doing this. It needs to be paired with an honest cost estimate and a hard rule that must-be quality gets funded first, and neither of those is anywhere in the framework. Kano tells you what kind of feature you are looking at. It does not tell you what to do when you cannot afford all of them, which is the actual job.

What’s Really Happening Inside the Brain

The Kano curves are not arbitrary shapes. Each one is drawn by a specific, well-documented feature of human cognition, and once you see the machinery, the model stops being a marketing tool and becomes applied psychology.

Loss aversion draws the must-be curve. The reason a must-be feature can only ever hurt you is that losses loom larger than equivalent gains. This is the core finding of prospect theory: the pain of losing something is roughly twice the pleasure of gaining it. A must-be feature is one the customer has mentally priced as already theirs, so its presence is a non-event and its absence is a loss. The steep drop on the left side of the must-be curve and the flat ceiling on the right are loss aversion, rendered as a graph. The same asymmetry powers the endowment effect, where people demand more to give up an object than they would pay to acquire it.

Hedonic adaptation draws the decay. The migration of delighters into must-be’s is one of the most human things about the model. We adapt to whatever becomes normal. A pleasure experienced repeatedly stops registering as a pleasure and resets to the new baseline, from which only further improvement feels good. This is why the delighter treadmill never stops: the surprise that thrilled a customer last year is the floor they stand on this year, and the brain has quietly re-zeroed. Adaptation is why a company can never buy permanent satisfaction with a one-time delight. It can only rent it.

Expectation violation draws the delighter spike. Delight is not the same emotion as satisfaction, and it is not just a lot of satisfaction. It is what happens when reality beats a forecast. The pleasant surprise of a delighter is the felt sense of a positive prediction error, the gap between what you braced for and what you got. This is why delight requires the absence of expectation to work at all. The moment a feature is expected, encountering it can no longer beat the forecast, so it cannot delight, no matter how good it is. The psychology of surprise and the decay of delighters are the same fact seen from two angles.

None of this machinery is a malfunction. Loss aversion kept our ancestors alive by weighting threats over opportunities. Adaptation is what lets us stop noticing a constant so we can attend to change. Prediction error is the brain’s core learning signal. The Kano model works because it happens to trace, in the language of product features, three of the most fundamental operations the mind runs.

The Kano Model vs Other Frameworks

Kano vs Herzberg’s Two-Factor Theory

These are parent and child. Herzberg established the asymmetry between dissatisfiers and satisfiers in the workplace; Kano ported it to products and, crucially, added measurement. The Two-Factor Theory gives you two bins, hygiene and motivator. Kano splits the satisfier side into performance and attractive, adds indifferent and reverse to catch the rest, and hands you a survey to sort real features into them. If you already think in Herzberg’s terms, Kano is the version you can actually run on a backlog.

Kano vs the MoSCoW Method

MoSCoW sorts requirements into Must-have, Should-have, Could-have, and Won’t-have. It looks like a cousin of Kano and it is not. MoSCoW is a negotiation about priority among stakeholders. Kano is a measurement of satisfaction among customers. A MoSCoW “Must-have” is something the team decided is essential; a Kano “Must-be” is something the customer’s psychology treats as non-negotiable, whether the team agrees or not. The two often disagree, and when they do, Kano is describing reality and MoSCoW is describing the room. Run Kano first to learn what customers actually need, then MoSCoW to negotiate what you will build.

Kano vs the Lean Startup

The Lean Startup and Kano answer different halves of the same question. Kano’s weakness is discovering delighters, because you cannot survey people about surprises they have not imagined. That is exactly what build-measure-learn is for: you ship a candidate delighter to a small group and watch behavior instead of asking about intention. Lean’s experimental loop covers Kano’s stated-preference blind spot, and Kano’s category structure gives Lean’s experiments something to be about. They are complements, and the strongest product teams run both.

Kano vs Design Thinking

Design Thinking is the discovery engine that feeds Kano its candidates. The empathize-and-define phases generate a wide field of possible features and unmet needs; Kano is the filter that sorts those candidates by their satisfaction structure so you know which are hygiene and which could delight. Design Thinking is upstream and generative. Kano is downstream and evaluative. Neither replaces the other, and a team that only does the generative half ends up with a hundred ideas and no way to rank them.

The Kano Model in the Real World

SaaS Onboarding and Feature Bloat

Software companies are where Kano’s warnings bite hardest, because software makes it trivially cheap to add features and nearly impossible to remove them. Every SaaS product accumulates a graveyard of indifferent-quality features that some quarter’s roadmap was certain would move the needle. A Kano study is one of the few tools that gives a product team permission to stop building. The category that matters most in a mature SaaS product is not attractive, it is indifferent, because that is where the reclaimed budget hides. The Net Promoter Score can tell you customers are unhappy; Kano can tell you which features to stop pouring money into so you can fix the ones that matter.

The Hotel and Airline Baseline War

Hospitality is a live museum of category decay. Free WiFi, a flat-screen television, a USB port by the bed, a mobile check-in: each one arrived as a delighter, briefly became a point of comparison, and settled into a must-be whose absence now generates one-star reviews. The industry runs a permanent arms race in which today’s amenity is tomorrow’s expectation, and the only escape from the treadmill is a genuinely new delighter, which itself will decay. Any hotel executive who thinks a 2019 amenity list still describes a competitive advantage is reading an expired Kano map.

Automotive Feature Migration

Cars show the full lifecycle at a scale you can watch across a single decade. Power windows, anti-lock brakes, the backup camera, adaptive cruise control, the giant center touchscreen: each walked the path from optional delighter to advertised performance feature to assumed baseline. The backup camera even completed the journey into law in some markets, which is category decay in its final form, a delighter that became a must-be and then a legal requirement. Automotive product planning lives or dies on correctly guessing where on that curve a feature sits at launch, because pricing a must-be as if it were still a delighter is how you lose a segment.

AI Features and the Compressing Curve

Artificial intelligence is doing something to the Kano lifecycle that is worth naming: it is compressing the decay curve. Features that would once have spent years as delighters are becoming expected in months, because the pace of shipping and the pace of adaptation have both accelerated. An AI writing assistant, a smart summary, a natural-language search box: each of these was a genuine delighter recently and is racing toward must-be status faster than any hardware feature ever did. The strategic implication is uncomfortable. If your differentiation is an AI delighter, the clock on it is shorter than it has ever been, and you are effectively renting satisfaction on a monthly lease. I have written more about motivation design in the AI age, and the collapsing Kano curve is one of its defining features. The teams that win will be the ones who understood, going in, that the delight was temporary and priced their strategy accordingly.

The Elephant in the Room

Let me point this at my own field, because it belongs there.

Gamification sells delight. Points, badges, surprise rewards, celebratory animations, the little confetti burst when you finish a task. Most of what my industry markets is, in Kano’s terms, a portfolio of attractive-quality features, and the entire value proposition rests on the jolt of positive surprise. Which means my field is standing directly on top of the one Kano category that is guaranteed to decay.

Here is the uncomfortable arithmetic. A delighter works by beating expectations, and hedonic adaptation resets expectations to whatever you delivered last. So the confetti that thrilled a user in week one is invisible by week ten, and the surprise reward that drove engagement in the first month has become the baseline the user now requires just to feel neutral. This is not a hypothetical risk. It is the single most common way gamified systems fail: they front-load novelty, the novelty adapts away, and engagement collapses because the system was renting satisfaction and forgot to keep paying.

The naive gamification pitch is that you can bolt delighters onto a product and manufacture love. Kano says that love is on a lease with rising payments. Every delighter you add raises the baseline the customer will expect next time, which means a strategy built purely on Core Drive 7 (CD7): Unpredictability & Curiosity is a treadmill that speeds up under you. This is why I have spent years arguing that surprise-and-delight is the shallowest layer of motivation, not the deepest.

The mature version of my own field takes Kano’s warning seriously and does two things differently. It treats must-be quality as sacred, because a gamified layer on top of a broken product is confetti on a sinking ship, and it anchors motivation in drives that do not decay the way novelty does. Meaning, mastery, and belonging do not adapt away the way a surprise reward does, which is exactly why the durable part of motivation design lives there and not in the confetti. The whole reason I built the Behavioral Framework Library is so these models can be checked against each other rather than sold one shiny idea at a time. Kano is the model that keeps my own field honest about the difference between a thrill and a foundation.

How to Apply the Kano Model with the Octalysis Framework

The Octalysis Framework maps human motivation onto eight Core Drives. Lay the Kano categories over those Core Drives and the model stops being a chart about features and becomes a map of which motivation each feature is actually pulling. The alignment is unusually clean, and it explains the decay that Kano observed but never fully accounted for.

Must-Be Quality Is Core Drive 8: Loss & Avoidance

A must-be feature is felt only in its absence, and that is the exact fingerprint of Core Drive 8 (CD8): Loss & Avoidance. CD8 motivates behavior through the desire to avoid something negative, and must-be quality is negative-avoidance made physical. The customer is not moved to buy by a locking hotel door. They are moved to never return by its failure. When you are working on must-be features, you are not building satisfaction, you are defusing loss, and the design goal is invisibility. A perfect must-be feature is one the customer never consciously notices, because noticing it means it broke.

Performance Quality Is Core Drive 2: Development & Accomplishment

One-dimensional features live in Core Drive 2 (CD2): Development & Accomplishment, the drive of measurable progress and “more is better.” Performance features are the ones customers consciously compare and track, which is why they behave linearly: the customer is running a progress bar in their head and satisfaction rises as the number climbs. This is the competitive axis, the one where being demonstrably better than the alternative is legible. It is also, exactly like a progress bar, subject to diminishing returns once the number exceeds what the user can perceive.

Attractive Quality Is Core Drive 7 and Core Drive 1

Delighters run on Core Drive 7 (CD7): Unpredictability & Curiosity, the drive of surprise and positive violation of expectation. That is the literal mechanism of delight, and it is why an expected delighter is a contradiction in terms: once CD7 has no surprise to work with, the delight evaporates. The most durable delighters also recruit Core Drive 1 (CD1): Epic Meaning & Calling, because a surprise that also feels meaningful lingers longer than a surprise that is merely pleasant. A support agent who solves your problem in four minutes is a CD7 delighter; a company that quietly does the right thing for you when it did not have to is CD7 and CD1 together, and the second one is remembered for years.

The Decay Is a Core Drive Migrating

Here is the insight the Octalysis lens adds that Kano’s own chart cannot show. When a delighter decays into a must-be, what is happening underneath is that the feature is migrating from CD7 to CD8. It starts as a surprise, which is Unpredictability and Curiosity. Repetition erodes the surprise through hedonic adaptation until the feature is simply expected, and an expected feature that would now be missed is Loss and Avoidance. The feature did not change. The Core Drive powering the customer’s reaction to it changed, from a white-hat drive that makes people feel good to a black-hat drive that makes them feel a potential loss. Category decay is a Core Drive migration, and once you see it that way you can predict it instead of being surprised by it.

The Design Principle: Fund the Black Hat, Ration the White Hat

Octalysis distinguishes White Hat drives, which make people feel powerful and fulfilled, from Black Hat drives, which move behavior through urgency and loss. Must-be quality sits in black-hat CD8; delighters sit in white-hat CD7 and CD1. The naive read is that you should chase the white-hat, feel-good delighters and treat the black-hat must-be’s as a chore.

Kano says the opposite, and it is the most important design instruction in this entire piece. Fund the black-hat must-be quality first and completely, because its failure causes the loss that ends the relationship, and no amount of white-hat delight survives a broken foundation. Then spend your white-hat delight deliberately and sparingly, knowing every delighter you ship raises the baseline and starts its own decay clock. The goal is a product whose must-be quality is invisible and flawless, whose performance quality competes honestly, and whose delighters are chosen with the full knowledge that you are buying temporary love and will have to buy it again. That is the difference between a design strategy and a sugar high.

Practical Steps

Concrete actions, in order of how quickly you can put them to work.

1. Run the two-question test on your top features. For each one, ask yourself the functional and dysfunctional questions honestly: how would customers feel if it were present, and how would they feel if it were gone. The gap sorts must-be from delighter faster than any workshop. You can do this on a whiteboard before you ever field a formal survey.
2. Timestamp every Kano result. The moment you categorize a feature, write the date next to it and a re-check reminder. A Kano category with no expiry date is a liability, because the categories decay and the chart will not tell you. Treat any study older than a year as a hypothesis, not a fact.
3. Fund must-be quality to completion before anything else. Make it a rule, not a judgment call: no delighter gets budget while a must-be feature is broken. Must-be failures cause churn, and churn is the only outcome that makes every other investment moot. Defuse the losses first.
4. Hunt for indifferent features and kill them. The most valuable output of a Kano study in a mature product is the list of things nobody cares about. Find the features that move satisfaction in neither direction, sunset them, and redeploy the budget to must-be and attractive quality. Stopping work is a strategy.
5. Pair every category with a cost. Kano tells you the type of feature and nothing about its price. Put an effort estimate next to each category before you prioritize, because a cheap delighter and an expensive one are not the same decision, and the model will happily let you confuse them.
6. Segment before you trust an average. Reverse quality hides inside population averages, where one segment’s delighter cancels another’s irritation. Break your Kano results down by customer type before you act on them, or you will ship a feature that half your users resent.
7. Attach a decay plan to every delighter you ship. Assume the delight is temporary and decide, in advance, what replaces it when it fades to baseline. A delighter without a successor is a cliff. The teams that keep customers are the ones who treat delight as a pipeline, not an event.

The Kano Model Was the Beginning, Not the End

Kano walked into the problem of customer satisfaction with an engineer’s refusal to accept that it was unmeasurable, and he left behind a chart that has outlived nearly every other prioritization method of its era. The three categories are the famous part. The decay is the part worth keeping, because it is the part that turns a static taxonomy into a living account of how satisfaction actually behaves over time.

What he really found is that satisfaction is not a possession a company can acquire. It is a relationship that has to be maintained against a customer who is constantly adapting, whose delighters become expectations, and whose expectations can only ever be met or violated. There is no permanent win. There is a must-be foundation you keep from cracking, a performance axis you keep competing on, and a stream of delighters you keep replenishing as fast as the last batch fades. A product is never finished, because the customer’s baseline never stops rising.

That sounds exhausting until you turn it around. The same treadmill that makes satisfaction impossible to bank permanently is what makes it possible to keep winning, because a competitor who thinks they have arrived has already started to decay. The opportunity is always open for the team that understood, from the start, that delight is rented and must-be is sacred. Kano handed us the map. What we build on it is the part he left for us.

Frequently Asked Questions

What is the Kano model in simple terms?

The Kano model is a way of sorting product features by how they affect customer satisfaction. Its key insight is that features do not all behave the same way. Must-be features are expected and only cause dissatisfaction when missing. Performance features raise satisfaction the better you deliver them. Attractive features, or delighters, produce a big jump in satisfaction when present but cost nothing when absent. It was created by Noriaki Kano in 1984 and is widely used for feature prioritization.

What are the five categories in the Kano model?

Must-be quality (expected features that only cause dissatisfaction when absent), one-dimensional or performance quality (features where more is better in a linear way), attractive quality or delighters (unexpected features that thrill when present and cost nothing when missing), indifferent quality (features customers do not care about either way), and reverse quality (features that make some customers less satisfied when present). Kano’s original 1984 paper named the first three; indifferent and reverse were added as the model matured.

Who created the Kano model and when?

Noriaki Kano, a professor of quality management at the Tokyo University of Science, published the model in 1984 with co-authors Nobuhiko Seraku, Fumio Takahashi and Shin-ichi Tsuji, in a paper titled “Attractive Quality and Must-Be Quality” in the Journal of the Japanese Society for Quality Control. It grew out of Frederick Herzberg’s two-factor theory of workplace motivation, applied to product quality, and reached Western product management in the 1990s.

What is the difference between must-be, performance, and delighter features?

Must-be features are the price of admission: present, they earn nothing; absent, they cause strong dissatisfaction. Performance features behave the way we intuitively expect, with satisfaction rising in proportion to how well they are delivered, and they are the axis where competition happens. Delighters, or attractive features, are unexpected extras that produce satisfaction out of proportion to their effort while their absence goes unnoticed. Only delighters can lift satisfaction meaningfully above neutral; must-be features cap out at zero.

How does the Kano questionnaire work?

For each feature it asks two questions: a functional one (“How would you feel if the product had this feature?”) and a dysfunctional one (“How would you feel if it did not?”). Each offers the same five answers, from “I like it that way” to “I dislike it that way.” Crossing the two answers in a lookup table classifies the feature as must-be, performance, attractive, indifferent, or reverse. The dysfunctional question is the clever part, because it surfaces must-be needs customers never think to mention.

Why do delighters become expectations over time?

Because of hedonic adaptation. Humans adapt to whatever becomes normal, so a pleasure experienced repeatedly resets the baseline it is measured against. A feature that delighted because it beat expectations stops delighting once it becomes the expectation. Kano called this the natural decline of quality: attractive features migrate to one-dimensional and then to must-be. A phone camera was a delighter in 2007 and is a must-be today. This is why no Kano study stays accurate indefinitely and why delight has to be continually replenished.

What are the main weaknesses of the Kano model?

Three big ones. First, its categories decay over time and the model presents them as if they were stable, so studies expire silently. Second, it measures stated preference rather than behavior, which makes it weak at discovering genuinely new delighters, since people cannot forecast their reaction to surprises they have not imagined. Third, it tells you a feature’s category but nothing about its cost, so it must be paired with an effort estimate before it can actually guide prioritization.

How does the Kano model relate to gamification and motivation design?

Closely, and as a warning. Most gamification sells delighters, which are attractive-quality features that run on Core Drive 7 (CD7): Unpredictability & Curiosity. Kano’s decay principle means those delighters fade to expectations through hedonic adaptation, which is the most common reason gamified systems lose steam. In Octalysis terms, must-be quality maps to Core Drive 8 (CD8): Loss & Avoidance and delighters to CD7 and Core Drive 1 (CD1): Epic Meaning. The mature lesson is to fund the must-be foundation first and treat delight as a renewable resource rather than a permanent win.

References

1. Kano, N., Seraku, N., Takahashi, F., & Tsuji, S. (1984). Attractive quality and must-be quality. Journal of the Japanese Society for Quality Control, 14(2), 39–48.
2. Herzberg, F., Mausner, B., & Snyderman, B. B. (1959). The Motivation to Work. John Wiley & Sons.
3. Herzberg, F. (1968). One more time: How do you motivate employees? Harvard Business Review, 46(1), 53–62.
4. Berger, C., Blauth, R., Boger, D., Bolster, C., Burchill, G., DuMouchel, W., et al. (1993). Kano’s methods for understanding customer-defined quality. Center for Quality Management Journal, 2(4), 3–36.
5. Matzler, K., & Hinterhuber, H. H. (1998). How to make product development projects more successful by integrating Kano’s model of customer satisfaction into quality function deployment. Technovation, 18(1), 25–38.
6. Löfgren, M., & Witell, L. (2008). Two decades of using Kano’s theory of attractive quality: A literature review. Quality Management Journal, 15(1), 59–75.
7. Mikulić, J., & Prebežac, D. (2011). A critical review of techniques for classifying quality attributes in the Kano model. Managing Service Quality, 21(1), 46–66.
8. Kahneman, D., & Tversky, A. (1979). Prospect theory: An analysis of decision under risk. Econometrica, 47(2), 263–291.
9. Tversky, A., & Kahneman, D. (1991). Loss aversion in riskless choice: A reference-dependent model. Quarterly Journal of Economics, 106(4), 1039–1061.
10. Brickman, P., & Campbell, D. T. (1971). Hedonic relativism and planning the good society. In M. H. Appley (Ed.), Adaptation-Level Theory (pp. 287–305). Academic Press.
11. Frederick, S., & Loewenstein, G. (1999). Hedonic adaptation. In D. Kahneman, E. Diener, & N. Schwarz (Eds.), Well-Being: The Foundations of Hedonic Psychology (pp. 302–329). Russell Sage Foundation.
12. Chou, Y. (2015). Actionable Gamification: Beyond Points, Badges, and Leaderboards. Octalysis Media.

Related Reading

• Two-Factor Theory: An S-Tier Behavioral Designer’s Guide. The workplace-motivation theory Kano borrowed his asymmetry from.
• The Lean Startup: An S-Tier Behavioral Designer’s Guide. The experimental loop that covers Kano’s blind spot on discovering new delighters.
• Design Thinking: An S-Tier Behavioral Designer’s Guide. The discovery engine that feeds Kano its candidate features.
• Net Promoter Score: An S-Tier Behavioral Designer’s Guide. The loyalty metric that tells you customers are unhappy without telling you which features to fix.
• The Endowment Effect: An S-Tier Behavioral Designer’s Guide. The loss-aversion mechanism that draws the must-be curve.
• Gamification and AI: Motivation Design for the AI Age. Where the Kano decay curve is compressing fastest.

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?