Gumshoe · Method reference

Kano analysis

Classify features by how their presence or absence shifts user satisfaction.

Conceptual illustration of kano analysis.
Effort
Medium
Participants
Needed
Remote friendly
Yes
Evidence / output
Direct user

What it is

A model that sorts features into categories (must-be, performance, and attractive or delighter, plus indifferent and reverse) based on how each affects user satisfaction, so teams can tell basic expectations apart from differentiators.

When to use it

During Synthesize or Ideate, when a backlog mixes table-stakes features with potential delighters and you need to decide what to build and in what order.

Why (value)

Separates features that only cause dissatisfaction when missing (must-be) from those that scale with investment (performance) and those that surprise and delight (attractive). It keeps teams from over-investing in basics or ignoring differentiators.

How to run it

  1. List candidate features.
  2. For each, ask users a paired functional and dysfunctional question (how they feel if the feature is present, and if it is absent).
  3. Map each response pair to a Kano category using the standard evaluation table.
  4. Aggregate across respondents to classify each feature.
  5. Prioritize: satisfy all must-be features first, choose performance features by cost and benefit, then invest selectively in delighters.

Inputs and outputs

  • Inputs: A candidate feature list and a sample of real users to survey.
  • Outputs: Features classified by Kano category, with a prioritization order.

Time and effort

Medium. Writing the paired questions and surveying enough users takes more effort than a quick internal matrix.

Evidence and limitations

Kano results are direct-user when gathered from real users, but they reflect stated preference at one moment, not revealed behavior. Categories drift over time as delighters become expected. The classification depends on well-written paired questions; a weak survey produces misleading categories. See Evidence and limitations.

Tips and pitfalls

  • Write the functional and dysfunctional questions carefully; ambiguous wording corrupts the classification.
  • Treat categories as time-sensitive; revisit as the market shifts.
  • Do not run Kano on internal guesses alone; without users it is just an opinion matrix.

Variations

Full survey-based Kano, a lighter team-estimate version for early triage, and continuous or discrete analysis of the response data.

Need help planning research or facilitating this method?

Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.

Discuss your project with Gumshoe Explore Gumshoe services

Sources and further reading

  • UX Tigers, “100 UX methods.”
  • NN/g, “The Kano Model: Critical and Satisfying Product Qualities.”

Explore related methods

  • RICE scoring — Rank initiatives with a formula of reach, impact, confidence, and effort.
  • Impact-effort prioritization — Plot options by impact and effort to spot the quick wins and avoid the money pits.
  • MoSCoW prioritization — Sort requirements into Must, Should, Could, and Won't to agree on scope.
  • Surveys — Ask a defined set of questions to many people to measure attitudes and self-reported behavior at scale.

A general practice reference. This page does not establish that a method was used on a particular client project or that an outcome was measured.