01 / UNDERSTAND
What is Kano analysis?
Kano analysis explores how people respond to an attribute being provided or absent. Its central distinction is that requirements do not all affect satisfaction in the same way. An expected condition may cause dissatisfaction when missing without creating special appreciation when present.
The model originates in work by Noriaki Kano and colleagues. A common questionnaire approach asks a functional question about an attribute’s presence and a dysfunctional question about its absence. Classification depends on the pair of answers, not a single importance rating. Categories inform a discussion of requirements; they do not automatically settle cost, obligation or implementation order.
Common response options express liking, expecting, neutrality, tolerance and dislike. Keep the chosen questionnaire’s wording and evaluation matrix consistent; changing the response convention changes what can be classified.
Why use Kano Analysis?
An organisation may spend heavily on an attractive addition while an expected condition remains unreliable. Kano analysis helps examine this asymmetry. It is also useful for challenging the assumption that all respondents value an attribute in the same way. An aggregate label can conceal materially different expectations within the audience.
When to use it
USE IT WHEN
There are concrete candidate attributes whose satisfaction effects need investigation.
A team wants to distinguish expected conditions from improvements or optional additions.
A questionnaire can reach people with relevant experience and be piloted before wider use.
When to choose another method
Use User Interviews when the attributes or wording are still speculative.
Use Concept Testing to explore a complete proposition and its commitments.
Use RICE Scoring or Impact / Effort Matrix to discuss investment after understanding needs and constraints.
What you’ll need
Describe attributes in language participants understand and choose a defined context. Decide who should answer and how that group will be reached. Use a consistent Kano question and response convention with a documented classification table. Pilot both presence and absence questions, since a confusing negative condition can produce misleading pairs. Keep raw pairs and missing responses so the analysis can be checked.
Understanding the Kano categories
Keep the elements that help answer your question and support a decision.
Expected conditions: absence causes dissatisfaction, while provision may be taken for granted.
Satisfaction improves with provision or performance, and dissatisfaction increases without it.
Welcome additions whose absence is tolerated rather than strongly disliked.
The attribute makes little difference to the respondent’s reported satisfaction.
The respondent prefers the attribute’s absence; inspect which audience or context explains this preference.
A contradictory or unexpected pair that warrants checking wording, understanding or response quality rather than forcing a preference label.
02 / PUT IT INTO PRACTICE
How to run and interpret Kano analysis
Keep evidence and assumptions distinct. Revisit your work when new information changes your understanding.
01
Specify the context
Choose the service situation and audience before selecting attributes.
Explore how commuters arrange a bike repair around their workday.
02
Describe one attribute
Avoid bundling several capabilities or implying a preferred answer.
A dependable collection window is different from an animated tracking map.
03
Draft paired questions
Keep the same condition in the presence and absence versions.
Ask about receiving a dependable collection window and then not receiving one.
04
Pilot interpretation
Ask people to explain the questions and response options in their own words.
Check whether window means a promise or merely an estimate.
05
Collect consistent pairs
Preserve answers together and record missing or contradictory responses.
Do not replace a skipped absence question with an assumed answer.
06
Classify and inspect variation
Use the documented table, then review the distribution rather than only the most frequent label.
An attribute may be expected by one group and optional for another.
07
Make a contextual decision
Combine the response pattern with evidence, delivery constraints and obligations.
Investigate reliability before choosing a decorative addition because it looks attractive.
Example: expectations around a bike repair collection
Fictional scenario: a bike repair service compares a dependable collection window, progress photos and a live map. One invented response pair treats the collection window as expected when provided and unwelcome when absent; under a common Kano evaluation table, that pair is classified as must be. Another pair welcomes progress photos but tolerates their absence, producing an attractive classification.
These pairs illustrate the logic only. They are not survey findings and cannot establish how a wider audience would answer. The team would inspect distributions and context before assigning an overall label.
The practical decision is to examine whether the service can keep a collection promise reliably. Progress photos may be useful later, but an attractive category alone does not justify building them first. A satisfaction category is one input to a decision, alongside consequences, feasibility and evidence.
03 / BELOW THE SURFACE
Below the surface: the classification belongs to the description
A category can change because the promise changed, even when the feature name did not.
DESCRIPTION
What promise did respondents evaluate?
Keep exact wording and relevant context.
VARIATION
Whose expectations differ?
Inspect the distribution before naming an aggregate category.
DELIVERY
Can we provide the condition as described?
Do not transfer an ideal promise to a weaker implementation.
Consider a collection window described as an estimate and then as a dependable commitment. Respondents may interpret these as different attributes. If the delivered service provides only an estimate, a study about a dependable promise does not establish its likely satisfaction effect.
Preserve the exact wording with each response distribution. Ask what conditions participants imagined and whether delivery can support those conditions. Do not transfer the category from an idealised description to a weaker implementation. If feasibility changes the promise, revise the attribute and investigate again.
The same discipline applies across audiences and over time. Report the context and variation instead of treating a category as an inherent property of a feature. This makes the result easier to challenge and more useful for design decisions.
Kano Analysis companion worksheet
The original two page companion records context, attributes, paired questions, the response convention, distributions and decision conditions. The second page checks wording, variation and delivery implications. It is a study planning and interpretation sheet. Use the linked method references for the standard evaluation table; the PDF does not classify answers automatically.
Practical tips
Pilot the absence question as carefully as the presence question.
Keep exact attribute wording beside the analysis.
Report unusual pairs and audience differences rather than hiding them.
Common mistakes
Classifying an attribute from only an importance score.
Treating the largest category as unanimous preference.
Prioritising attractive additions while ignoring essential conditions or obligations.
What you’ll get
An account of how a defined audience responds to particular service conditions. Use it to refine requirements and choose questions for further investigation. Do not turn the categories into a delivery ranking without considering cost, reliability, obligations and uncertainty.