The Kano Model classifies customer requirements into basic, performance, excitement, indifferent, and reverse attributes so teams can prioritize features and quality characteristics by their effect on satisfaction.
Definition
The Kano Model is a customer-requirements framework that explains how different features affect satisfaction. Basic needs are expected and cause dissatisfaction when missing. Performance needs increase satisfaction as performance improves. Excitement needs delight customers when present but may not be expected.
The model helps teams avoid treating every requirement as equally important. It connects Voice of the Customer work to prioritization, design decisions, CTQs, and product or service strategy.
History
Noriaki Kano introduced the model in the 1980s as a way to understand quality beyond one-dimensional requirement fulfillment. It became widely used in quality planning, product development, service design, QFD, and Design for Six Sigma.
The model remains useful because customer expectations change. Today’s delighter can become tomorrow’s basic requirement.
When to Use
Use the Kano Model when prioritizing features, service attributes, CTQs, product improvements, or customer-experience investments. It is useful during VOC analysis, QFD, DMADV, roadmap planning, and competitive differentiation.
Do not use Kano as a substitute for technical feasibility, risk, cost, or regulatory review. It should be one input to decisions.
Step-by-Step
- Define the customer segment and offering.
- Collect customer needs using interviews, surveys, complaints, and observation.
- Write clear functional and dysfunctional Kano questions.
- Classify responses into basic, performance, excitement, indifferent, or reverse attributes.
- Prioritize requirements using satisfaction impact, dissatisfaction risk, cost, and strategy.
- Translate priority needs into measurable CTQs.
- Review periodically because expectations evolve.
Examples
- Software: Reliable login is basic, faster response is performance, and smart workflow suggestions may delight.
- Manufacturing: correct fit is basic, short lead time is performance, and proactive design support may delight.
- Healthcare: privacy is basic, appointment availability is performance, and proactive follow-up can delight.
Common Pitfalls
- Surveying the wrong customer segment.
- Writing vague feature statements.
- Assuming delighters remain delighters forever.
- Ignoring basic requirements while chasing excitement features.
- Not translating results into CTQs.
- Using the model without cost and feasibility review.