Strategy
Kano Analysis
A practical product and UX prioritisation method for classifying features by their effect on user satisfaction.
How to run Kano analysis to classify features as must-haves, performance drivers, and delighters, then prioritise roadmap decisions.
What it is
Kano analysis is a UX and product method used to categorise glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term or product attributes based on how they affect user satisfaction.
It identifies three main types of glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term: Must-Haves, glossaryPerformancePerformance refers to how quickly and efficiently a system responds to user actions and processes tasks.Open glossary term Features, and Delighters.
The method captures user perceptions through guideSurveysCollecting structured feedback at scale to understand user attitudes, sentiment, and self-reported behaviour.Open guide, interviews, or glossaryFeedbackFeedback is the system response that informs users about the result of their actions. It helps users understand what has happened and what to do next.Open glossary term.
The focus is on understanding which glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term drive satisfaction and which are unnecessary.
Key takeaway
The goal is to prioritise development and design efforts to maximise user happiness and resource efficiency.
When to use it
Use this method when you need to prioritise glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term.
It is most useful when:
It is less useful when:
Kano analysis is often used alongside JTBD, personas, and usability testing.
How to run it
Set up properly
Be clear on the glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term you are evaluating, which users you are asking, and how the results will be used. Kano needs a manageable feature set; twenty features produces forty questions and abandoned guideSurveysCollecting structured feedback at scale to understand user attitudes, sentiment, and self-reported behaviour.Open guide.
Word the paired questions carefully. The method depends on asking about presence and absence separately, and people find the absence question strange unless it is framed well.
Run the method
Kano analysis classifies glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term by how their presence and absence affect satisfaction. Its glossaryInsightAn insight is a meaningful understanding that explains why something is happening and what it means.Open glossary term is that these are not symmetrical: some features only ever disappoint, and some only ever glossaryDelightDelight is a moment in an experience that exceeds what the user expected, usually through care taken over a detail they assumed would be ignored. It builds preference rather than satisfaction.Open glossary term.
- Present each glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term to users individually, described in terms of what it would let them do.
- Ask the paired question: how they would feel if it were present, and how they would feel if it were absent.
- Categorise from the glossaryResponseA response is the data or result returned by a server after receiving a request.Open glossary term pair: must-have, glossaryPerformancePerformance refers to how quickly and efficiently a system responds to user actions and processes tasks.Open glossary term, delighter, indifferent, or reverse.
- Watch for indifferent and reverse results. glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term nobody wants, and features some people actively dislike, are the most valuable findings.
- Analyse across segments, since a delighter for one group is frequently an irrelevance to another.
Remember that categories migrate. Today's delighter becomes tomorrow's must-have once competitors have it, so Kano results have a shelf life.
Capture and make sense of it
The value comes from understanding asymmetry. After the analysis, document:
- Must-haves, whose absence causes disproportionate damage
- glossaryPerformancePerformance refers to how quickly and efficiently a system responds to user actions and processes tasks.Open glossary term glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term, where more genuinely is better
- Delighters worth investing in, and indifferent glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term worth cutting
- Differences between segments, since a delighter for one is an irrelevance to another
Use this to prioritise. The clearest use is defensive: making sure the must-haves are solid before spending anything on glossaryDelightDelight is a moment in an experience that exceeds what the user expected, usually through care taken over a detail they assumed would be ignored. It builds preference rather than satisfaction.Open glossary term.
Key takeaway
Use this to balance investment and user delight.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If glossaryFeatureA feature is a specific piece of functionality within a product that delivers value to users. It represents something users can do or experience as part of the overall product.Open glossary term are misprioritised, resources are wasted.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps ensure features resonate with users and maximise satisfaction.
Get in touch
If this sounds like something you need, we can help you perform Kano analysis to prioritise features effectively and maximise user satisfaction.
No guesswork. No assumptions. Just data-driven UX decisions.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is Kano analysis in UX?
It is a method for categorising product features based on their effect on user satisfaction.
When should you use Kano analysis?
During product planning, roadmap definition, or feature prioritisation.
What can you test?
Must-Haves, Performance features, Delighters, and other feature attributes.
Why classify features rather than rank them?
It ensures design and development focus on features that truly impact user satisfaction.
Does Kano analysis improve UX?
Yes. It helps create products that meet expectations and delight users without wasting resources.
Quick take
If you want to prioritise features effectively, understand which delight users, which are expected, and which don’t matter.
Related Services
