Kano Analysis

What is Kano Analysis?

Kano Analysis is a customer-focused prioritization method that helps organizations understand how different product or service features influence customer satisfaction. Developed by Japanese professor Dr. Noriaki Kano in the 1980s, the model recognizes that not all customer requirements contribute equally to satisfaction.

Some features are simply expected—customers may never mention them until they're missing. Others create increasing satisfaction as they improve, while a few unexpected features can delight customers and differentiate an organization from its competitors.

By classifying customer requirements into categories, Kano Analysis helps teams focus improvement efforts where they create the greatest value for customers.

Why Kano Analysis Matters

Many organizations assume every customer request deserves equal attention.

In reality, investing heavily in the wrong features may add cost without improving customer satisfaction.

Kano Analysis helps organizations:

Understand what customers truly value.
Differentiate between expected and exciting features.
Prioritize improvement initiatives.
Allocate development resources more effectively.
Improve customer satisfaction while controlling costs.
Identify opportunities for innovation.

Instead of asking only "What do customers want?", Kano Analysis asks: "How will delivering this feature actually affect customer satisfaction?"

Kano Analysis model illustrating how different product and service features influence customer satisfaction, including Must-Be (Basic), Performance, Excitement (Delighters), Indifferent, and Reverse requirements, with a satisfaction-versus-feature graph showing how customer expectations change as features are added.

Explore Kano Analysis

When to Use Kano Analysis

Kano Analysis is particularly valuable when:

Designing new products or services.
Improving existing products.
Prioritizing customer requirements.
Developing product roadmaps.
Evaluating enhancement opportunities.
Conducting Voice of the Customer (VOC) studies.
Planning continuous improvement initiatives.
Balancing customer expectations with development costs.

It is commonly used in Lean Six Sigma, product management, service design, UX design, software development, and innovation projects.

How Kano Analysis Works

The Kano Model groups customer requirements into several categories based on their relationship to customer satisfaction.

Basic (Must-Be) Requirements: These are the minimum expectations customers assume will be present. Meeting them does not increase satisfaction. Failing to meet them creates strong dissatisfaction. Examples include: Safe products, accurate billing, reliable operation, clean facilities.

Performance Requirements: Performance requirements have a direct relationship with customer satisfaction. The better these features perform, the happier customers become. Examples include: Faster delivery, longer battery life, better fuel economy, higher product reliability.

Excitement (Delighter) Requirements: These are unexpected features customers may never request because they don't expect them. When present, they create excitement and delight. When absent, customers are usually not dissatisfied because they never expected them. Examples include: Complimentary upgrades, unexpected gifts, personalized recommendations, exceptional customer service experiences.

Additional categories that may be considered include:

Indifferent Requirements: These features have little impact on customer satisfaction. Whether present or absent, customers generally don't care.

Reverse Requirements: Some customers actually prefer a feature not to exist.

Remember that one group's improvement may reduce another group's satisfaction. This highlights the importance of understanding different customer segments.

Key Concepts in Kano Analysis

Several important ideas underpin the Kano Model.

Customer Expectations Change: Today's exciting feature often becomes tomorrow's basic expectation. For example: Free Wi-Fi in hotels once delighted customers. Today it is simply expected. Organizations must continually innovate to stay ahead.
Voice of the Customer: Kano Analysis often begins with customer interviews and surveys designed to understand both stated and unstated needs. Traditional surveys ask: "Do you want this feature?" Kano surveys ask two questions: "How do you feel if the feature exists?", and "How do you feel if the feature does not exist?" The combination helps classify each requirement into its Kano category.
Strategic Prioritization: Resources are limited. Kano Analysis helps organizations invest in features that produce the greatest improvement in customer satisfaction rather than simply adding more features.

Common Pitfalls to Avoid

Common mistakes in performing Kano Analysis include:

Assuming every customer requirement has equal value.
Ignoring changing customer expectations.
Focusing only on requested features.
Treating all customers as one homogeneous group.
Neglecting Voice of the Customer research.
Forgetting to periodically update Kano classifications.
Investing heavily in features customers do not value.

Where Kano Analysis Fits in Lean Six Sigma

Within Lean Six Sigma, Kano Analysis is most commonly used during the Define phase of DMAIC. It complements Voice of the Customer activities by helping teams determine which customer requirements should receive the greatest attention during improvement efforts. Kano Analysis also supports:

Critical-to-Quality (CTQ) development.
Product and service design.
Design for Six Sigma (DFSS).
Quality Function Deployment (QFD).
Customer journey mapping.
Innovation planning.
Continuous improvement prioritization.

By understanding not only what customers expect—but how different requirements influence satisfaction—teams can design solutions that both solve problems and create competitive advantage.

What Is Kano Analysis in Simple Terms?

Kano Analysis is a method for understanding which product or service features customers simply expect, which improve satisfaction, and which create delight, helping organizations focus their improvement efforts where they matter most.