Purpose
When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight.
Product Discovery Decision method
Kano Model
Classifies product attributes by how their presence and absence affect customer satisfaction, using paired questions.
Classifies product attributes by how their presence and absence affect customer satisfaction, using paired questions.
How does each feature affect satisfaction when present or absent?
- Participants
- 10-50
- Time
- 1-2 Tage
The steps are a practical sequence; adapt them to the method’s purpose and available evidence.
Features
Select individual attributes
Break concepts into attributes respondents can evaluate independently and understand consistently.
Functional
Ask functional questions
For each attribute ask how respondents feel if it is present. Use the same five options: like it; must be that way; neutral; can live with it; dislike it.
Dysfunctional
Pair dysfunctional questions
Ask the mirrored question for the feature’s absence; keep both answers paired for each respondent.
Analysis
Apply evaluation table and inspect spread
Classify each pair as A/O/M/I/R/Q, aggregate frequencies and investigate Q, reverse, ties and segments.
Revisit the model when evidence, context or outcomes change. Record what changed and why.
A good fit when
Use it when: Feature Strategy, Roadmap Tradeoffs. The group can provide the evidence and authority the method requires.
Ideal for
- Feature strategy
- Roadmap tradeoffs
- Differentiation
Not good for
- Technical dependencies
- Urgent fixes
Outputs
Kano analysis
Paired answers per feature, evaluation table and distribution of A/O/M/I/R/Q categories.
Category distribution with uncertainty
Recorded scope, date, participants, source version, owner, changed assumptions, and the reason for each revision.
Response-pair matrix
Example responses per feature
Record both answers from the same respondent for each feature; then classify them using the Kano evaluation table.
| Feature and response pair | Feature | Functional | Dysfunctional | Category |
|---|---|---|---|---|
| Response pair 1Record one respondent’s answers for one feature | Reschedule online | Like it | Dislike | O · One-dimensional |
| Response pair 2Record one respondent’s answers for one feature | Choose reminder time | Like it | Neutral | A · Attractive |
1. Feature
- Response pair 1
- Reschedule online
- Response pair 2
- Choose reminder time
2. Functional
- Response pair 1
- Like it
- Response pair 2
- Like it
3. Dysfunctional
- Response pair 1
- Dislike
- Response pair 2
- Neutral
4. Category
- Response pair 1
- O · One-dimensional
- Response pair 2
- A · Attractive
The matrix records each respondent’s functional and dysfunctional answer together. The canonical A/O/M/I/R/Q evaluation table appears in the method example.
First step
Break concepts into attributes respondents can evaluate independently and understand consistently.
Good to do first
Deep dive
How it works
It classifies answers to functional questions so that basic, performance, and delight factors become legible on the same grid. This lets roadmap decisions align more with customer experience than with sheer feature count.
In detail
The Kano Model works because it distinguishes features by their effect on satisfaction, breaking up linear prioritization logic. Good use looks at the reaction to a feature's presence and absence instead of merely asking about importance. This reveals which features only meet expectations, which can delight, and which investment brings hardly any additional effect.
Facilitation
Prepare a manageable set of clearly worded features so respondents or participants don't answer with bundled solutions. The decision becomes solid once a feature the team considers a delighter shows only basic-need behavior in the responses. Close with a clear classification and a note on which features need further evidence or segmentation.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Kano Model: WorksheetPrepare the decision, source evidence and next review.markdown
Kano Model: WorksheetPrepare the decision, source evidence and next review.
markdownkano-working-template.md
Prepare the decision, source evidence and next review.
Kano Model: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Run the method Time: See catalog planning range; no universal duration.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Shared visual workspace, source evidence, and an agreed decision question.
- Roles: Researcher, representative respondents, product decision-maker, analyst.
- Advance information: Collect existing data, examples, constraints and relevant stakeholder perspectives.
- Overall time needed: Several days or weeks for recruiting and responses; allow 60–90 min for classification.
- Setup: For each individual feature ask two questions: response if it is present (functional) and response if it is absent (dysfunctional). Use the same five answers: like it; must be that way; neutral; can live with it; dislike it. Classify each pair with the evaluation table as Attractive, One-dimensional, Must-be, Indifferent, Reverse or Questionable; then report frequencies and segments.
Prepare for the work steps
Features: Select individual attributes
- Product options and relevant customer segments
Functional: Ask functional questions
- Attribute wording and consistent answer scale
Dysfunctional: Pair dysfunctional questions
- Same attributes and unchanged response scale
Analysis: Apply evaluation table and inspect spread
- Answer pairs, Kano table and segment data
Response-pair matrix
| Feature and response pair | Feature | Functional | Dysfunctional | Category |
|---|---|---|---|---|
| Response pair 1 | ||||
| Response pair 2 |
- Response pair 1: Record one respondent’s answers for one feature
- Response pair 2: Record one respondent’s answers for one feature
Keep each respondent’s paired answers together. Do not replace this evaluation with a feature popularity score.
Attractive Quality and Must-Be Quality · Kano et al. (1984)
Features: Select individual attributes
Expected artifact: Atomic attribute list
Atomic attribute list
Entry:
...
- Does each item contain one feature?
Functional: Ask functional questions
Expected artifact: Functional answer per respondent and feature
Functional answer per respondent and feature
Entry:
...
- Is the positive question neutral and clear?
Dysfunctional: Pair dysfunctional questions
Expected artifact: Complete answer pairs
Complete answer pairs
Entry:
...
- Does every functional answer have its paired question?
Analysis: Apply evaluation table and inspect spread
Expected artifact: Category distribution with uncertainty
Category distribution with uncertainty
Entry:
...
- Are distributions shown rather than only the winning class?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/kano/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Product Strategy
RICE Scoring
Instead of Kano Model, when reach, impact, confidence, and effort should count as a numeric comparison and no expectation categories are needed.
Product Discovery
Opportunity Scoring
Moves customer problem, solution idea, and evidence toward a concrete result through "collect outcomes from discovery", "define an importance scale", and "calculate and sort the score".
Product Discovery
Jobs to Be Done
Reconstructs switching motives, progress, and desired outcomes so opportunities emerge from real customer situations.
Product Discovery
Landing Page Test
Tests value proposition and offering through a landing page, so conversion data supports early product decisions.
Product Discovery
Hypothesis Prioritization Canvas
Moves customer problem, solution idea, and evidence toward a concrete result through "take over the hypothesis list", "define the risk scale", and "select the top hypotheses for the next tests".
Product Strategy
ICE Scoring
Moves target group, value, goals, and priorities toward a concrete result through "prepare the idea backlog", "define scales for I, C, and E", and "select top ideas for testing or building".
Constraints and origin
MediumWorkshop + async1-2 Tage
Profile
- Method form
- Decision method
- Participants
- 10-50
- Time
- 1-2 Tage
- Maturity
- Established
- Origin
- Noriaki Kano
Next up: MoSCoW