What is the Kano Model?

The Kano model is a technique used in product development and customer satisfaction research to understand and classify customer preferences. It was developed by Professor Noriaki Kano of Tokyo University in the 1980s.

A simplified introduction to the Kano model focuses on three categories: basic, performance, and delight

.

• Basic features are those that are essential for the product to be considered usable, and their absence would result in extreme dissatisfaction. Examples of basic features for a car could include functioning brakes, headlights, and steering.

• Performance features are those that provide a linear increase in customer satisfaction when their level is increased. Examples of performance features for a car could include fuel efficiency, horsepower, or safety features.

• Delight features are those that exceed customer expectations and provide a significant boost in customer satisfaction. They are often unexpected or unique features that differentiate the product from others in the market. Examples of delight features for a car could include a built-in GPS, a panoramic sunroof, or a massage seat.

The Kano model uses customer surveys to determine how customers feel about each feature and categorize them accordingly. By understanding which features are basic, performance, or delight, organizations can prioritize product development efforts, allocate resources more effectively, and better meet customer needs.

The Kano model is widely used in industries such as automotive, software, and consumer electronics, but can be applied to any product or service where customer satisfaction is important.

Why it matters

It helps teams question whether more features will create the satisfaction they expect for a particular user group.

Example

Consider a team choosing improvements for an online checkout. Research suggests that customers treat secure payment as a basic expectation, respond positively to shorter checkout time, and sometimes appreciate an unexpected convenience such as remembering a preferred collection location. The team uses Kano questions with relevant customers to examine those responses rather than assigning categories from its own opinions. It first addresses missing basics, then weighs other opportunities against cost and evidence of value. Preferences vary across customers and can change with experience. The model informs prioritization, but the team still needs to evaluate the complete journey and delivery constraints.

Common misunderstanding

The familiar basic, performance, and delight categories are a simplified introduction, not permanent properties of features. An attribute that delights one customer group may be expected by another. Expectations can also change, so yesterday's differentiator may become tomorrow's minimum requirement.

Research the relevant users and the conditions in which they experience the offering. Do not assume that examples from another product establish a category for yours. The model informs prioritization, but delivery cost, accessibility, risk, and the overall experience still need consideration.

Related terms

Customer Journey Map · Personas · Outcome-Based Planning

Explore questions like this with other practitioners through the Agile Community Network, nuAgility's free live community event and podcast.