Kano Model

The Kano model is an analytical framework that classifies product and service features according to their effect on customer satisfaction. Developed by Noriaki Kano in 1984, the model challenges one-dimensional views of quality by plotting feature execution against customer emotional response. It categorizes attributes into must-be, performance, attractive, indifferent, and reverse requirements. By mapping user sentiment through paired functional and dysfunctional survey questions, organizations can strategically prioritize resources, resolve mandatory baselines, and introduce competitive differentiators.

0/5 explored

How well deliveredexcellent

Key facts

Originator: Noriaki Kano
Publication Year: 1984
Primary Categories: Must-be, Performance, Attractive
Survey Question Types: Functional and dysfunctional
Quantitative Metrics: Better and Worse satisfaction coefficients
Lifecycle Phenomenon: Kano drift

By Matthew Savas — Founder of Kaizumi. Reviewed 1 September 2026.

The Kano model is an analytical framework that classifies product and service features according to how they influence customer satisfaction and perception. Developed within quality management and operational strategy, the framework replaces the assumption that customer satisfaction increases linearly with product functionality. Instead, it demonstrates that different categories of requirements produce distinct emotional and behavioral responses when they are fulfilled or neglected. Teams use the framework to interpret voice of customer data, maintain rigorous customer focus, and allocate engineering and development resources efficiently. By categorizing features based on direct user feedback, organizations can identify baseline operational requirements, differentiate their offerings from competitors, and eliminate non-value-added investments.

Origins and historical development

Noriaki Kano, a professor at the Tokyo University of Science, developed the model in the late 1970s and published it in 1984 alongside colleagues Fumio Seraku, Fumiyoshi Takahashi, and Shinichi Tsuji. Their foundational paper, published in the journal of the Japanese Society for Quality Control, challenged the prevailing view of customer satisfaction. Prior to Kano's work, standard quality systems generally treated customer satisfaction as a one-dimensional continuum where providing more attributes or higher performance directly produced higher customer satisfaction.

Kano and his co-authors drew upon motivation-hygiene theory from organizational psychology to propose a two-dimensional structure. This structure separates the objective execution level of a feature on one axis from the subjective customer satisfaction level on the other. The model spread through global quality management and Six Sigma programs during the 1990s. While initially applied to physical manufacturing and consumer goods, the Kano model is now standard practice across product management, service design, systems engineering, and software development.

Core feature categories

The Kano model evaluates features along two intersecting dimensions: the degree of achievement or execution, ranging from absent to fully implemented, and the customer's emotional response, ranging from extreme dissatisfaction to extreme satisfaction. Based on these axes, features fall into three primary categories and three secondary classifications.

Must-be features

Must-be features represent the basic, mandatory expectations of a product or service. Customers consider these requirements fundamental and take their presence for granted. When a must-be feature is missing or defective, customers experience extreme dissatisfaction and anger. Conversely, when a must-be feature is executed perfectly, it does not increase customer satisfaction above neutral; it merely prevents dissatisfaction.

In automotive manufacturing, brakes serve as a standard example of a must-be feature. If an automobile lacks functioning brakes, the customer is furious and the product is unusable. However, if the brakes function flawlessly, the customer remains indifferent because baseline stopping capability is a mandatory prerequisite for vehicle operation.

Performance features

Performance features produce satisfaction in direct, linear proportion to how well they are delivered. When performance features are absent or poorly executed, satisfaction falls; as execution improves and capability increases, satisfaction rises steadily. These are the characteristics on which competitors openly contest market share and against which customers explicitly compare competing brands.

Fuel economy in an automobile exemplifies a performance feature. Higher distance traveled per unit of fuel directly increases customer satisfaction, while lower fuel economy decreases satisfaction. When engineering teams balance competing performance parameters, such as engine power versus fuel economy, they frequently analyze trade-off curves to select the optimal design target within their cost constraints.

Attractive features

Attractive features provide unexpected value and delight when present, but cause zero dissatisfaction when omitted. Because customers do not actively anticipate or ask for these capabilities, the absence of an attractive feature does not degrade the user experience. However, delivering an attractive feature creates disproportionate positive satisfaction and acts as a strong competitive differentiator.

A heated steering wheel is an example of an attractive feature in standard passenger vehicles. If an automobile does not have a heated steering wheel, customers do not lodge complaints or view the vehicle as defective. When the feature is included, it delights the user and enhances their overall perception of the product.

Secondary categories

In addition to the three primary categories, user surveys may reveal three secondary classifications:

Indifferent features: Characteristics that do not influence customer satisfaction in any way, whether they are present, absent, executed poorly, or executed well. Resources spent on indifferent features represent pure operational waste.
Reverse features: Attributes that cause dissatisfaction when present and satisfaction when absent. This situation occurs when certain user segments prefer simplicity or specific workflows that the feature impedes.
Questionable results: Data points that show internal contradictions in user responses, indicating that the survey question was poorly phrased, the user misunderstood the question, or an error occurred during data collection.

Survey methodology and feature classification

Teams determine the Kano category of a feature using a structured, paired-question survey administered to representative customers. For every feature under evaluation, the survey presents two distinct questions: a functional question and a dysfunctional question.

The functional question asks how the customer feels if the feature is present or fully implemented. The dysfunctional question asks how the customer feels if the feature is absent or not implemented. For each question, the respondent must select one of five standardized answers:

I like it
I expect it
I am neutral
I can tolerate it
I dislike it

The evaluation process pairs the functional response with the dysfunctional response to map the feature into an evaluation matrix:

If the customer likes the feature when present and dislikes its absence, the feature is classified as Performance.
If the customer expects the feature when present or can tolerate it, but dislikes its absence, the feature is classified as Must-be.
If the customer likes the feature when present and is neutral toward or can tolerate its absence, the feature is classified as Attractive.
If the customer selects neutral, tolerate, or expect across both functional and dysfunctional states, the feature is classified as Indifferent.
If the customer dislikes the feature when present and likes it when absent, the feature is classified as Reverse.
If the customer selects identical extreme options, such as liking both presence and absence or disliking both presence and absence, the response is recorded as Questionable.

Quantitative analysis and satisfaction coefficients

When surveying large user populations, responses for a single feature often distribute across multiple categories. To quantify the overall aggregate sentiment, teams calculate the customer satisfaction coefficient, which consists of two metrics: the Better coefficient and the Worse coefficient.

To calculate the Better coefficient, add the total number of Attractive responses to the total number of Performance responses. Then, divide that sum by the total count of Attractive, Performance, Must-be, and Indifferent responses combined. The resulting number ranges from zero to one. Values closer to one indicate that implementing the feature has a strong positive effect on customer satisfaction.

To calculate the Worse coefficient, add the total number of Must-be responses to the total number of Performance responses. Divide that sum by the total count of Attractive, Performance, Must-be, and Indifferent responses combined. Express this resulting number as a negative value, which ranges from zero to negative one. Values closer to negative one indicate that failing to implement the feature causes severe customer dissatisfaction.

Comparing the absolute values of the Better and Worse coefficients allows teams to see whether a feature acts primarily as a customer acquisition driver, a retention safeguard, or a baseline operational requirement.

Feature lifecycle and dynamic drift

Kano classifications are not permanent. Over time, customer expectations shift through a process known as Kano drift. As technologies mature and competing organizations replicate successful innovations, market baselines rise.

The typical drift path progresses in a consistent sequence:

A novel capability enters the market as an Attractive feature, delighting early adopters while leaving non-users unbothered by its absence.
As competing products adopt the capability, customers begin comparing execution levels directly, transforming the attribute into a Performance feature.
Over time, the attribute becomes an industry standard. Customers now expect it universally, converting it into a Must-be feature.

Automotive safety features illustrate this lifecycle. Anti-lock braking systems and backup cameras initially entered the commercial market as attractive options on luxury vehicles. As adoption expanded, consumers began comparing stopping distances and sensor quality across mainstream models, making them performance features. Today, regulatory mandates and consumer expectations have transformed both technologies into must-be features that every vehicle must provide.

Strategic prioritization rules

The primary objective of Kano analysis is to guide product roadmaps, capacity allocation, and engineering spend. To achieve optimal customer satisfaction within budget constraints, organizations apply a strict sequence of prioritization rules:

Fix every must-be feature first: Eliminate all non-conformances, defects, and omissions in must-be requirements. Products that fail to deliver must-be features are rejected by the market regardless of performance levels elsewhere.
Compete on performance features: Invest development capacity in performance features that offer the greatest marginal satisfaction gain relative to unit cost and execution effort.
Add attractive features where the budget allows: Selectively implement high-impact attractive features to differentiate the product from competing alternatives and create market interest.
Eliminate indifferent features: Remove indifferent attributes from development queues and product architectures to reduce manufacturing overhead, software complexity, and inventory costs.
Reverse any reverse features: Redesign or remove features that generate active customer dissatisfaction, or provide configuration settings that allow users to disable them.

By adhering to this hierarchy, development teams avoid the common error of adding novel, attractive capabilities to a product while leaving critical, must-be requirements incomplete or unreliable.

Integration with quality and lean frameworks

The Kano model acts as a front-end filter for downstream continuous improvement and product development systems. Within lean management, it prevents overprocessing and overproduction by defining the precise boundaries of customer value.

In Quality Function Deployment, practitioners place Kano survey results into the House of Quality matrix. Must-be attributes establish non-negotiable engineering thresholds, performance attributes populate competitive benchmarking rows, and attractive attributes inform design innovations. This alignment ensures that engineering tolerances, supply chain parameters, and quality control plans directly reflect the classification of each feature, maximizing customer satisfaction while minimizing unnecessary operational costs.

Frequently asked questions

What is Kano drift?: Kano drift is the natural erosion of customer delight over time as market baselines rise and technologies mature. A feature typically enters the market as an attractive differentiator, transitions into a performance attribute as competitors adopt it, and ultimately becomes a mandatory must-be requirement. For example, backup cameras and anti-lock brakes debuted as luxury differentiators but eventually became expected baseline standards.
How are the Better and Worse satisfaction coefficients calculated in Kano analysis?: The Better coefficient is calculated by dividing the sum of Attractive and Performance responses by the total count of Attractive, Performance, Must-be, and Indifferent responses combined. The Worse coefficient divides the sum of Must-be and Performance responses by that same total, expressed as a negative value. The Better score ranges from zero to one to measure positive satisfaction impact, while the Worse score ranges from zero to negative one to capture the risk of customer dissatisfaction.
What rules govern feature prioritization in the Kano model?: Teams must resolve all must-be features first, because a product that lacks baseline requirements is rejected by the market regardless of other attributes. Next, organizations invest development capacity into performance features that yield the highest marginal satisfaction gain, followed by attractive features if budget permits. Finally, indifferent features are eliminated to remove operational waste, and reverse features are redesigned, removed, or made optional.
What are indifferent and reverse features in the Kano model?: Indifferent features are characteristics that have no effect on customer satisfaction whether they are fully implemented, poorly executed, or completely absent. Reverse features are attributes that actively cause customer dissatisfaction when present and satisfaction when omitted. In practice, indifferent features represent operational waste that should be cut, while reverse features must be redesigned, removed, or configured to allow users to disable them.
How does the Kano model integrate with Quality Function Deployment?: Kano survey classifications transfer directly into the House of Quality matrix used in Quality Function Deployment. Must-be attributes define non-negotiable engineering specifications and baseline thresholds, performance attributes populate competitive benchmarking comparisons, and attractive attributes inform innovative design targets. This mapping ensures that downstream engineering tolerances, supply chain targets, and quality control plans align directly with user sentiment.

Terms

A3 Problem Solving Lean