故事 · 狩野纪昭的「满意」之问 Origin Story · Noriaki Kano's Question About Satisfaction
1984 年，东京理科大学教授狩野纪昭(Noriaki Kano)对一个被默认成立的假设发起了挑战： 「满意度真的和需求满足程度成正比吗？」他通过对每条需求问两个相反的问题 —— 「有了它你怎么想？」「没有它你又怎么想？」 —— 发现客户需求其实分成三种截然不同的类型： 必备型（缺了就不满，有了也无感，像刹车）、期望型（越多越满意，像油耗）， 以及兴奋型（没有不怪你，有了惊喜，像意外的贴心彩蛋）。 更妙的是，他还发现需求会随时间退化：今天的惊喜，明天就成了理所当然。 In 1984, Tokyo University of Science professor Noriaki Kano challenged an assumption everyone had taken for granted: "Is satisfaction really proportional to how well a need is met?" By asking each requirement two mirror-image questions — "How do you feel if it is present?" and "How do you feel if it is not?" — he uncovered three fundamentally different types of need: must-be (its absence enrages, its presence is unnoticed — like brakes), one-dimensional (more is linearly better — like fuel economy), and attractive (its absence is forgiven, its presence delights — like an unexpected, thoughtful detail). Better still, he found needs decay over time: today's delighter is tomorrow's baseline.

1 Kano 二维图：三型需求，三条命运 The Kano Diagram: Three Needs, Three Destinies

拖动滑块drag the slider

2 三型需求的双问识别法 Identifying the Three Types by the Two-Question Test

必备型 Must-beMust-be
有了：理所当然
没了：强烈不满
例：刹车、登录安全、餐厅卫生 Present: taken for granted
Absent: strong dissatisfaction
Examples: brakes, login security, restaurant hygiene
期望型 One-dimensionalOne-dimensional
越多越满意
越少越不满
例：油耗、续航、网速、价格 More → happier
Less → angrier
Examples: fuel economy, battery life, network speed, price
兴奋型 AttractiveAttractive
有了：惊喜
没了：无所谓
例：贴心彩蛋、超预期赠品 Present: delight
Absent: no objection
Examples: thoughtful Easter eggs, an unexpected gift

3 现实里的 Kano Kano in the Real World

需求分级：先把每条需求归到三型，再决定投入 —— 别在必备型上堆资源刷存在感。 Need triage: classify every requirement into the three types first, then decide where to spend — don't pour budget into must-bes hoping for applause.
资源分配：必备型做到「合格」即止，期望型按竞争投入，剩余弹药押在兴奋型上做差异化。 Resource allocation: take must-bes to "compliant" and stop; match the market on one-dimensional needs; bet the remaining budget on attractive features to differentiate.
兴奋型差异化：一两个让人「哇」的小惊喜，往往比把基础功能堆到顶更能打动客户。 Differentiate with delighters: one or two well-aimed "wow" moments move customers more than stacking baseline features to the ceiling.
需求退化：今天的兴奋型迟早变必备型，必须持续创新补充新的惊喜，否则被对手抹平。 Decay is inevitable: today's attractive becomes tomorrow's must-be. Keep refilling the pipeline of delight, or competitors will flatten your edge.
一句话In One Line
Kano 模型推翻了一个朴素直觉：满意度并不是需求满足程度的简单线性函数。 必备型是入场券 —— 做到头也只换来「不抱怨」，少一点就满盘皆输； 期望型是竞技场 —— 谁做得多谁就多得分，是和对手正面拼刺刀的地方； 兴奋型才是护城河 —— 客户没想到、对手没做到，一点点就能引爆口碑。 所以聪明的设计者会把基础功能做扎实、把资源省下来押在惊喜上。 但别忘了：惊喜会过期。空调、倒车影像、刷脸支付都曾是兴奋型，如今全成了必备型 —— 创新若停下，护城河就被时间填平。 The Kano model overturns a tempting intuition: satisfaction is not a simple linear function of how well a need is met. Must-bes are the entry ticket — perfect them and you only earn "no complaints"; miss them and the whole game is lost. One-dimensional needs are the arena — more delivery, more points, and a place where you go head-to-head with the competition. Attractive needs are the moat — what the customer never asked for and rivals haven't shipped; a small dose ignites word of mouth. So a sharp designer nails the basics, then saves ammunition for the delighters. But don't forget: delight has an expiration date. Air-conditioning, reversing cameras, face-ID payment were once attractive — today they're must-bes. Stop innovating and time fills your moat for you.
常见误用Common Mistakes
在必备型上堆资源求好评（刹车做到飞起也没人夸）。必备型做到合格即可，把弹药省给兴奋型。 Piling resources onto a must-be chasing praise — flawless brakes still earn zero applause. Take must-bes to compliant and stop; save the ammunition for attractive features.
把 Kano 分类一次定死、永不复审。兴奋型会退化成必备型，需求归类要定期重测。 Classifying once and never revisiting. Attractive features decay into must-bes — re-run the classification on a regular cadence.
只追兴奋型，忽视必备型（彩蛋很炫但刹车失灵）。必备型缺一不可，它是兴奋型生效的前提。 Chasing delighters while neglecting must-bes — fancy Easter eggs mean nothing if the brakes fail. Must-bes are non-negotiable; they are the precondition for any delighter to land.

Kano 模型