What is it?
The Kano Model helps you understand how different product or service features affect customer satisfaction. It separates basic expectations, performance features and unexpected delights so improvement effort can be aimed more intelligently.
What's it really for?
Kano explains why organisations can add impressive features while customers remain irritated. Delight does not compensate for a missing basic. A hotel may offer a pillow menu, but the experiment loses some of its charm when the room is not clean.
You know when…
A team proudly demonstrates the clever new feature. It uses artificial intelligence, produces a colourful dashboard and took four months to build. A customer asks whether the password reset now works.
The room becomes educational.
Have a go
- List the features or service characteristics customers experience.
- Ask how people feel when each is present and when it is absent.
- Classify each as basic, performance, delight, indifferent or unwanted.
- Fix missing basics before investing heavily in delight.
Why it works
Not all requirements behave in the same way. Some are only noticed when they fail, some create more satisfaction as performance improves, and some pleasantly surprise people because they were never expected. The model makes those different relationships visible.
Look for…
Look for basic needs that have become invisible internally, performance needs where more genuinely matters, and delights that may become tomorrow's expectations. Indifferent features are useful too; they identify effort the organisation values more than the customer does.
Watch out…
Customer expectations move. Yesterday's delight becomes today's normal and eventually tomorrow's complaint. Revisit the analysis, use evidence from real customers and avoid classifying features according to how proud the design team feels about them.
Worth noticing…
Customers do not reward every success. Some things are simply the price of being allowed to play.
Try next…
Use a CTQ Tree to turn important needs into measurable requirements. Use an Impact–Effort Matrix when several possible improvements need sequencing.