This workshop guide turns the Kano Model pocket guide into a practical facilitation resource for teams that need to understand which customer requirements must be protected, improved, delighted, deferred, or removed.
Overview
Organizations often assume that customer satisfaction improves linearly as more requested features are delivered. Kano analysis challenges that assumption. Some requirements prevent dissatisfaction but do not create delight. Some produce proportional satisfaction gains. Some surprise customers when present but do not hurt when absent. Some do not matter. A few may actively create dissatisfaction.
The workshop teaches participants to classify customer needs and use those classifications to guide investment. Instead of treating every customer request as equal, teams learn to ask what kind of need they are hearing and what satisfaction return they should expect.
Customers cannot always tell you what will delight them, but the Kano Model helps you find the difference between basics, performance drivers, and delight opportunities.
Who This Workshop Is For
Quality, product, service, and customer-experience teams translating VOC into action.
DMAIC teams defining CTQs, improvement priorities, or customer requirements.
Product managers and process owners deciding where to invest limited resources.
Leaders trying to understand why delivered customer requests did not improve satisfaction.
Teams designing surveys, service improvements, QFD inputs, or feature roadmaps.
Learning Objectives
Explain the five Kano need categories and their satisfaction behavior.
Distinguish Must-Be, One-Dimensional, Attractive, Indifferent, and Reverse requirements.
Design functional and dysfunctional Kano question pairs.
Use the Kano evaluation logic to classify responses.
Calculate and interpret satisfaction and dissatisfaction coefficients.
Segment Kano results by customer type.
Build a Kano Priority Matrix for investment decisions.
Core Concept: Satisfaction Is Not Linear
The Kano Model classifies customer requirements by how fulfillment and non-fulfillment affect satisfaction. This matters because the right investment strategy differs by category. Must-Be requirements need reliability and protection. One-Dimensional requirements need competitive performance. Attractive requirements need innovation leverage. Indifferent features should not consume scarce resources. Reverse features should be eliminated or segmented carefully.
Must-Be
Basic expectations. Their absence creates dissatisfaction, but their presence rarely delights.
One-Dimensional
Performance requirements. More fulfillment creates more satisfaction; poor performance creates dissatisfaction.
Attractive
Delighters. Their presence can create strong satisfaction; their absence may not hurt yet.
Indifferent
Features or attributes that do not materially affect satisfaction for the segment studied.
Reverse
Features that some customers dislike when present and may prefer absent.
Category Migration Over Time
Kano categories are not permanent. Today's Attractive feature can become tomorrow's One-Dimensional expectation and eventually a Must-Be. This migration happens as competitors copy features, customers become familiar with new standards, and market baselines rise.
The strategic lesson is clear: customer research cannot be a one-time exercise. Teams need a cadence for tracking whether delight features are becoming expected features and whether prior investments are losing differentiation value.
Kano Survey Design
A Kano questionnaire uses paired questions for each requirement. The functional question asks how the customer feels if the feature is present. The dysfunctional question asks how the customer feels if the feature is absent. The pairing reveals non-linear satisfaction dynamics that simple importance ratings miss.
Each question uses five response options: I like it that way, it must be that way, I am neutral, I can live with it that way, and I dislike it that way. The combination of answers is classified through the Kano evaluation table.
- Define a specific feature or process requirement in customer language.
- Write one functional question about the requirement being present.
- Write one dysfunctional question about the requirement being absent.
- Avoid leading language or bundled requirements.
- Collect enough responses by segment to support decisions.
- Exclude questionable responses and investigate reverse patterns.
Satisfaction and Dissatisfaction Coefficients
After classifying responses, teams can calculate two useful values. The Satisfaction Coefficient estimates how much fulfillment can increase satisfaction. The Dissatisfaction Coefficient estimates how much non-fulfillment can reduce satisfaction. Together, they help prioritize action more intelligently than category labels alone.
A high Satisfaction Coefficient with low dissatisfaction impact often points to an Attractive opportunity. A low Satisfaction Coefficient with strongly negative dissatisfaction impact indicates a Must-Be requirement that must be protected.
Airline Boarding Case Example
The source guide uses airline boarding because it contains clear customer segments, operational constraints, and many possible requirements. On-time departure, clear announcements, mobile boarding-pass reliability, overhead bin availability, real-time status updates, family pre-boarding, gate-agent friendliness, and upgrade offers can fall into different Kano categories.
The case shows why teams must not treat all requested improvements the same. Some boarding attributes are non-negotiable basics. Others are performance battlegrounds. A few may be delight features for specific segments.
Kano Priority Matrix
The final deliverable of the workshop is a priority matrix that converts VOC results into investment logic. It helps teams decide what to fix first, where to compete, where to innovate, what to stop funding, and what to remove.
Tier 1: Must Address
Must-Be requirements below threshold performance. These are foundational and urgent.
Tier 2: Competitive Investment
One-Dimensional requirements where better performance creates direct satisfaction return.
Tier 3: Innovation Leverage
Attractive requirements with strong satisfaction coefficients and practical feasibility.
Tier 4: Defer or Eliminate
Indifferent features consuming resources without customer value.
Tier 5: Actively Remove
Reverse features causing dissatisfaction for the segment studied.
Workshop Flow
The source guide is intended for a 4-hour session. This agenda turns Kano analysis into an applied VOC prioritization exercise.
0:00-0:20 Opening and VOC Problem
Discuss why giving customers what they ask for does not always create satisfaction.
0:20-0:55 Kano Categories
Teach the five categories and satisfaction curves with simple product and service examples.
0:55-1:25 Category Migration
Analyze examples of delight features that became expected basics.
1:25-2:00 Survey Pair Design
Teams write functional and dysfunctional questions for three requirements.
2:00-2:15 Break
Facilitator reviews question clarity and removes bundled requirements.
2:15-2:50 Evaluation and Coefficients
Practice classifying responses and interpreting satisfaction and dissatisfaction coefficients.
2:50-3:25 Airline Boarding Case
Apply Kano thinking to boarding-process requirements and customer segments.
3:25-3:50 Priority Matrix
Build a tiered action plan for one product, process, or service.
3:50-4:00 Commitment
Each participant identifies one Kano question pair to test in their work.
Facilitator Notes
Keep examples concrete. Kano is easiest to understand through familiar customer experiences.
Do not allow teams to bundle several requirements into one survey item.
Challenge assumptions about what customers value. The point of Kano is to test, not guess.
Discuss segmentation early because the same feature can mean different things to different customer groups.
Emphasize that Must-Be items must be reliable before delight investments can compensate.
Discussion Questions
Which requirements in your product or service are likely Must-Be, One-Dimensional, and Attractive today?
Where has your organization improved a feature without seeing proportional satisfaction gain?
Which Attractive feature is most at risk of migrating into a Must-Be expectation?
What three requirements would you test first with Kano question pairs?
How would you segment customers for Kano analysis?
What would surprise leadership most about a Kano Priority Matrix for your organization?
Participant Takeaways
Customer satisfaction is not a simple more-features equation.
Need categories determine the right investment strategy.
Kano paired questions reveal dynamics standard surveys miss.
Segment results because different customers may classify the same feature differently.
Attractive features depreciate as markets learn to expect them.
Related Learning Resources
Closing Message
The Kano Model helps teams listen smarter, not just louder. It turns customer feedback into strategic choices about basics, performance, delight, waste, and dissatisfaction.
Customers may not always articulate what will delight them. Kano gives quality professionals a disciplined way to discover it.