SiliciumHex FieldKit

Design to Cost · Value

Kano Classification

Sort features by customer reaction: basics, performers, delighters — and question the ones nobody would miss.

  • Time45 min
  • FormatSmall group
  • StageValue

Kano Classification: what it is and why it works

Kano classification sorts product features by how customers react to their presence or absence. Basic, or must-be, features are expected: their absence causes dissatisfaction, but adding more does not increase satisfaction. Performance features increase satisfaction roughly in proportion to how well they are delivered. Delighters are unexpected: their absence goes unnoticed, but their presence creates a positive reaction. Features to which customers are indifferent also appear. Classifying features with real users shows where extra cost buys satisfaction and where it does not.

Cost tends to follow requirements, and when every requirement is presented as essential, cost grows without discrimination. The Kano model, introduced by Noriaki Kano in 1984, gives a structured way to challenge that. Over-delivering a basic feature is usually wasted money; small investments in delighters can differentiate a product strongly; and performance features deserve investment in proportion to what customers will pay. Categories also shift over time, as today's delighters become tomorrow's basics. Kano analysis complements price-value alignment, which checks what customers pay for, and QFD, which translates prioritized needs into technical characteristics. A value perception map adds the competitor view.

What you need

  • A list of the product's main features or attributes, including candidate new features
  • Access to users or customers from the relevant segments
  • A simple survey or interview guide, for example paired questions on how users feel if a feature is present or absent
  • Approximate cost per feature from the cost breakdown

What you get

  • Each feature classified as basic, performance, delighter or indifferent, by segment if needed
  • Basic features where the product over-delivers at high cost
  • Low-cost delighters worth adding or highlighting
  • A rebalanced investment plan across features

When to use it

When every requirement arrives as “must have” and the cost follows.

How to do it, step by step

  1. List the main features or attributes of the product.
  2. Classify each with users: basic (expected), performance (more is better), delighter (unexpected plus).
  3. Find features users class as basic but that cost a lot to over-deliver.
  4. Find cheap delighters that differentiate.
  5. Rebalance investment: minimal on saturated basics, deliberate on delighters.

Worked example: Electric pallet trucks for distribution centers

Illustrative scenario — figures are realistic but not from a real company.

A manufacturer of electric pallet trucks for warehouses and distribution centers was preparing a model refresh. Product management had a list of 14 features, all marked as essential, and the target cost was being exceeded by about $400 per truck.

  1. The team selected nine features for classification, including emergency stop, charge indicator, run time per charge, lithium-ion opportunity charging, a full-color display, a premium painted cover, fleet telematics and a tablet mount.
  2. They interviewed 45 users: operators and fleet managers at eight sites, using paired questions about each feature's presence and absence.
  3. Emergency stop and charge indicator came out as basic. The full-color display, costing about $140 compared with $45 for a simple monochrome display, was also seen as basic: operators wanted charge level and hours, nothing more.
  4. Run time and opportunity charging were clear performance features for multi-shift sites. Telematics was a delighter for fleet managers and indifferent for operators. A $12 tablet mount was a strong delighter for operators.
  5. The premium painted cover, worth about $65, was classified as indifferent by both groups.

Result. The team switched to a monochrome display, used a standard painted cover, added the tablet mount as standard and offered telematics as a fleet package. The net result was about $150 saved per truck, with more to come from battery options. They noted that safety-related basics such as the emergency stop were never part of the cost discussion.

Open it in the FieldKit Design to Cost app → Get the Design to Cost template pack — join the waitlist

Common pitfalls and how to avoid them

  • Classifying features from internal opinion rather than asking users.Use interviews or a simple paired-question survey with real users from each key segment.
  • Averaging results across segments that react very differently.Analyze segments separately and consider options or packages for segment-specific features.
  • Treating a basic feature as a cost reduction target when it relates to safety or compliance.Keep safety and compliance features fixed; look only for over-delivery beyond requirements.
  • Assuming categories are permanent.Revisit the classification at each major product update, because delighters tend to become basic over time.

Frequently asked questions

What are the Kano model categories?

The main categories are must-be or basic features, which customers expect; one-dimensional or performance features, where more is better; and attractive features or delighters, which are unexpected and create a positive reaction. Kano analysis also identifies indifferent features, which customers do not care about, and reverse features, which some customers actively dislike.

How do you run a Kano survey?

For each feature, ask two questions: how the user would feel if the feature were present, and how they would feel if it were absent, with answers such as like it, expect it, neutral, can tolerate it and dislike it. The combination of answers places the feature in a category. Survey a representative group of users per segment and look for clear patterns.

Do Kano categories change over time?

Yes. Features that delight customers when first introduced often become expected as competitors adopt them and users get used to them. A feature that was a delighter a few years ago may now be a basic requirement. That is why Kano classification should be repeated when a product is updated or when the market changes significantly.

Origin

Kano model of customer satisfaction — Noriaki Kano, Tokyo University of Science, 1984.

Related methods

More in “Value”

Find what the customer actually values — and what they never asked for.