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.
Quick take
If you want to prioritise features effectively, understand which delight users, which are expected, and which don’t matter.
Related Services
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.
Before you start, 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 to evaluate, which user groups to include, and how glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term outcomes will be used.
Prepare structured questions to capture functional and emotional glossaryResponseA response is the data or result returned by a server after receiving a request.Open glossary term.
Run the method.
Kano analysis is evaluative and comparative.
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. Ask how they feel if it is present and if it is absent. Categorise features as 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. Analyse results to guide glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term.
Focus on capturing both expectations and emotional reactions.
Capture and make sense of it.
The value comes from actionable glossaryPrioritisationPrioritisation is the process of ranking tasks, features, or initiatives based on their importance, impact, and effort.Open glossary term.
After analysis: summarise 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 category, highlight those with highest satisfaction impact, inform glossaryRoadmapA roadmap is a strategic plan that outlines the direction, priorities, and timeline for a product or initiative. It communicates what will be delivered and why, rather than just listing features.Open glossary term decisions, and identify differentiation opportunities.
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 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 effectively and maximise user satisfaction.
No guesswork. No assumptions. Just glossaryDataData is raw information collected and stored for analysis, processing, or decision-making.Open glossary term-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 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 based on their effect on user satisfaction.
When should you use Kano analysis?
During product planning, glossaryRoadmapA roadmap is a strategic plan that outlines the direction, priorities, and timeline for a product or initiative. It communicates what will be delivered and why, rather than just listing features.Open glossary term definition, or guideFeature PrioritisationRanking features by user value, business value, effort, and risk to focus roadmap delivery on highest-impact outcomes.Open guide.
What can you test?
Must-Haves, 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, Delighters, and other feature attributes.
Why is it important?
It ensures design and development focus on 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 that truly impact user satisfaction.
Does Kano analysis improve UX?
Yes. It helps create products that meet expectations and glossaryDelightMoments that exceed user expectations.Open glossary term users without wasting resources.