The Kano model is a framework that sorts customer needs by how their presence or absence changes satisfaction. Its three core categories are basic needs (must-be), performance needs (one-dimensional), and delighter needs (attractive). The point: satisfaction is not linear, so not every quality gap is worth the same effort.
Noriaki Kano and his co-authors introduced the model in a 1984 paper, and it has been cited thousands of times since, but on a plant floor it is less a marketing tool and more a triage rule. It tells you which defects and which attributes to fix first when you cannot fix everything at once. This guide covers the categories, how to classify a need, and how to turn the classification into a work order. For where this sits among improvement tools, see our overview of lean manufacturing.
What is the Kano model?
The Kano model is a theory of customer satisfaction that maps how well a product meets a given need against how satisfied the customer feels, and shows that the relationship differs by category of need. It was developed by Noriaki Kano, Nobuhiko Seraku, Fumio Takahashi, and Shin-ichi Tsuji and published in 1984 as Attractive Quality and Must-Be Quality in the Journal of the Japanese Society for Quality Control. The central insight is that satisfaction is asymmetric: the same amount of fulfillment produces very different reactions depending on which kind of need it serves.
Think of it as three curves on the same chart. A basic need is a flat line at the bottom until it fails, then it plunges. A performance need is a straight diagonal, more is better, less is worse, proportionally. A delighter is a curve that stays flat when absent and shoots up when present. Same axes, three shapes, three different rules for where to spend your improvement effort.
What are the three main Kano categories?
The three categories that matter most in practice are basic needs, performance needs, and delighter needs, and each carries a different rule for prioritization.
Basic needs (must-be quality) are the price of entry. Customers assume them and never mention them, so fulfilling them earns no praise, but a failure causes sharp, disproportionate dissatisfaction and quiet defection. A food product that is safe and correctly labeled, a machined part within spec, an order that ships complete: these are basics. You do not get points for meeting them; you lose the customer for missing them. In quality terms, basics are the defects that trigger root cause analysis and complaints, and they are almost always where triage should start.
Performance needs (one-dimensional quality) are the ones customers evaluate consciously and linearly, more is better, less is worse, in proportion. Price, yield, on-time delivery rate, throughput, response time. Customers will trade these off against each other and against cost. This is where competitive comparison lives and where measured improvement pays off in visible satisfaction.
Delighter needs (attractive quality) are the unexpected extras. Their absence causes no complaint because the customer never expected them, but their presence produces outsized satisfaction. A delighter is what differentiates, until competitors copy it. Over time, today's delighter becomes tomorrow's performance need and eventually a basic. Anti-lock brakes were once a delighter; now they are a legal basic. The model is a snapshot, not a permanent map.
| Category | If present | If absent | Plant example | Priority rule |
|---|---|---|---|---|
| Basic (must-be) | No credit | Strong dissatisfaction | Correct spec, safe product, complete order | Fix first, these lose customers |
| Performance (one-dimensional) | Satisfaction rises | Dissatisfaction rises | On-time rate, yield, lead time | Improve measurably to compete |
| Delighter (attractive) | Strong satisfaction | No complaint | Proactive status updates, extras | Add after basics are solid |
The categories are not permanent labels, they drift in one direction over time. An attribute almost always starts life as a delighter, becomes a performance need as customers learn to expect and compare it, and finally settles into a basic that no longer earns any credit at all. The drift is one-way and it is relentless, which is why a classification done once and filed away goes stale. What differentiated you three years ago is table stakes now.
How do you classify a need using the Kano method?
You classify a need by asking customers two questions about it: one functional and one dysfunctional. The functional question asks how they would feel if the product had the attribute; the dysfunctional question asks how they would feel if it did not. Each is answered on a five-point scale from "I like it" to "I dislike it," and the pair of answers maps to a category on a standard Kano evaluation table.
The pairing is what reveals the category. If a customer likes having the attribute but only tolerates its absence, it is a delighter. If they expect it and dislike its absence but shrug at its presence, it is a basic. If their feeling tracks the fulfillment in both directions, it is a performance need. Two extra answers matter: indifferent (the customer does not care either way, do not spend on it) and reverse (the customer actively dislikes the attribute, its presence hurts). Indifferent and reverse results are how the survey saves you from building things nobody wants.
The most common mistake here is classifying from the inside. Engineering assumes an attribute is a delighter because it was hard to build; sales assumes another is a basic because one loud customer complained. Neither is evidence. Classify from what a representative set of customers actually says or does, surveys where you can run them, and complaint, return, and audit data where you cannot. The category belongs to the customer, not to the effort you spent.
How do you use the Kano model to prioritize quality work?
Use the Kano model as a triage sequence: secure the basics, then compete on performance, then differentiate with delighters. The order is not optional, because the categories are not equal. A plant that adds a delighter while a basic is broken is polishing the trim on a car with no brakes. Here is the sequence.
- List the attributes customers actually judge you on. Pull them from complaints, returns, audit findings, and voice-of-customer notes, not from an internal wish list. Anchor them in real critical-to-quality characteristics.
- Classify each one. Use the functional/dysfunctional question pair, or classify from evidence when you cannot survey. Complaints and recalls flag basics; competitive comparisons flag performance needs.
- Fix broken basics first. Any basic need that is failing goes to the top of the list regardless of how small it looks, because it is losing customers quietly. Route these through root cause analysis and verify the fix held.
- Bring performance needs up to competitive level. Once basics are solid, invest measured improvement where more is visibly better, yield, on-time delivery, lead time, and track it.
- Add delighters deliberately. Only after the first two are handled, pick one or two attractive attributes to differentiate. Expect them to erode into performance needs over time.
- Re-classify on a cadence. Categories migrate. Today's delighter becomes tomorrow's basic, so revisit the classification yearly and after any major market shift.
The Kano model: by the numbers
The model rests on documented, primary research rather than consultant lore:
- The original paper, Attractive Quality and Must-Be Quality (Kano et al., 1984, Journal of the Japanese Society for Quality Control), established the categories and the asymmetric-satisfaction theory that underpins every later version.
- The American Society for Quality maintains reference material on the model as part of its quality tools situating it alongside the other structured methods a quality team uses.
- Kano's categories are explicitly time-dependent: attractive attributes migrate to one-dimensional and then to must-be as customers come to expect them, which is why the classification must be repeated rather than fixed.
Where does the Kano model fit with other quality tools?
The Kano model sits at the front of the quality toolchain, it decides what to work on, before other tools decide how. It pairs naturally with the methods a plant already runs: once Kano flags a broken basic, you drive it out with root cause analysis and lock the fix in with a quality audit checklist so it stays fixed. Performance needs are the attributes you put on the scoreboard and watch trend. Delighters are the deliberate extras you add only after the foundation is sound.
The classification only pays off if you can act on it, and acting on it depends on knowing which basics are actually failing, which is a data problem before it is a strategy problem. When defects, complaints, and returns are logged on paper and reconciled at month-end, a failing basic can bleed customers for weeks before anyone sees the pattern. When capture is digital and current, the broken basic surfaces the same day, and the Kano triage runs on real signal instead of stale tallies. That is the shift CLS made moving off clipboards, and it is the loop Harmony builds for plants. If you are also working the problem-side of quality, the companion piece on Kepner-Tregoe analysis covers how to pin down a hard-to-find defect once Kano has told you it matters. Secure the basics, compete on performance, delight on purpose, and do it in that order.