Explainer Established Frameworks

Kano Model — Customer Satisfaction Types

Classifying features by how they affect satisfaction and delight, with Maslow as its loose ancestor, and where it shows up in your work.

Generated
November 18, 2026, 3:24 PM MT
Created
November 18, 2026, 3:22 PM MT
Built from
  • wiki/concepts/kano-model.md
  • wiki/concepts/maslows-hierarchy.md

Industry standard

Classifies features by how they affect customer satisfaction and delight. Survey-grounded (the Kano questionnaire).

"More is better" isn't universal.

Origin

Kano: Kano, Seraku, Takahashi & Tsuji, 1984. Cite it by author when you use it.

5categories
1984"Attractive Quality and Must-Be Quality"
Surveygrounded

Categories

BasicThresholdExpected, and painful when absent
PerformanceLinearSatisfaction scales with it
DelighterAttractiveUnexpected joy; absence isn't punished
Indifferent—Customers don't care
Reverse—More of it bothers some customers

How it's used

Key insight"More is better" isn't universal; a roadmap balances Basic, Performance and Delighter features.
MethodSurvey-grounded (the Kano questionnaire).
Maslow's Hierarchy (1943)Kano's conceptual ancestor: functional needs before delight. A loose metaphor with weak empirical support.

In your frameworks and projects

Your own work, kept separate from the standard above. Your frameworks are the six D's ("Car is IE"), STARTIFY and RADAR.

AI Agent for PMRanking framework. The Kano Agent proposes a classification with reasoning and confidence; no formula.
STARTIFYInforms R: Relevance to Customer Experience — "Would customers actually notice if this disappeared?"
RADARJustifies the protected ~20% strategic-bets bucket: nobody asks for what doesn't exist yet.