The Kano model for feature ideas: what delights, what is expected, what nobody cares about
Run this method in IdeaHone
Creates a space with the entities and scoring criteria of this method, ready for your next session.
The team argues for an hour about whether the feature is important. Half say customers will leave without it, the other half say nobody will notice. Both are often right, because the real question is not whether it is important but which kind of important. The Kano model, developed by Noriaki Kano in the 1980s, gives you five kinds, a short survey to tell them apart and a different decision for each.
Why impact is the wrong word
Most scoring methods ask for one number: impact. Features break that number. Hot water in a hotel room adds nothing to satisfaction, because every guest expects it, yet a cold shower ruins the stay. A handwritten welcome note costs nothing when missing, yet the guest who finds one tells friends about it. Kano separates the two. Use it when you have 10 to 40 candidate features for a product or service and the debate keeps circling; for a first cut of mixed ideas the impact and effort matrix is faster.
The five categories
The running example is a hotel stay.
Must-be
Expected. Absence hurts, presence goes unnoticed. Hot water in the shower: nobody writes a review praising it, everybody writes one when it is cold.
Performance
More is better, in proportion. Wifi speed: slow annoys, fast pleases, and every step in between moves satisfaction.
Attractive (delighters)
Unexpected. Absence does not hurt, presence delights. A handwritten note from reception welcoming you by name: nobody misses it, and those who get it remember it.
Indifferent
Nobody cares either way. A branded pen on the desk: present or absent, the review reads the same.
Reverse
Some customers dislike it. A host who explains every amenity at check-in: a welcome for one guest, an intrusion for the next.
How the questionnaire works
For each feature you ask two questions. How would you feel if this were present? How would you feel if this were absent? Both get the same five answer options: I like it, I expect it, I am neutral, I can live with it, I dislike it.
The pair of answers places the feature in a category. The key combinations:
| If present ... | ... and if absent | Category |
|---|---|---|
| I expect it | I dislike it | Must-be |
| I like it | I dislike it | Performance |
| I like it | I am neutral | Attractive |
| I am neutral | I am neutral | Indifferent |
| I dislike it | I like it | Reverse |
"I like it" for both present and absent means the person misread the question; mark it as questionable.
Collecting the answers with a survey link
The answers should come from customers, and customers do not sit in your workshop. In IdeaHone the Kano activity has a Survey step for that: you write each feature the way a customer would say it, create a link and send it out. Respondents open it on their phone, answer the two questions per feature and are done in a few minutes.
- No account, nothing about the person. Respondents do not sign in. IdeaHone stores the answers and nothing else: no name, no email, no cookie.
- One link per group. Customers, sales and support each get their own link, in English, German or Spanish. The results show each group's category side by side.
- The team guesses first. While answers come in, the facilitator sees only how many there are. The team classifies the features without seeing the answers, so the guess stays honest.
- Ten answers decide. From 10 answers on, the customers' category counts and the team's guess sits next to it. Where the two disagree, IdeaHone marks a surprise, which is the agenda for step 4 below. Answers that contradict themselves are left out.
- A link ends by itself. After 14 days or 50 answers, unless you set other limits, or whenever you close it.
Running it in a workshop
- List the candidate features in customer language. "Late checkout until 14:00", not "checkout flexibility module". If a customer would not say it, rewrite it.
- Ask 10 to 20 customers or proxies the two questions per feature. Proxies are people who talk to customers daily, not people who talk about them. Send the survey link a week or two before the session.
- Tally the category per feature. The most frequent category wins. Note the runner-up when the split is close.
- Discuss the surprises. Put the features the team loved that came back indifferent on the wall first and say it out loud: "We would have built this. Nobody wanted it."
- Decide by category. Must-be first, no debate. Performance ranked by cost, which is where weighted scoring earns its place. Delighters: one or two as bets, not five. Indifferent: dropped. Reverse: dropped or made optional.
- Record the category with each idea. Category and survey date stay next to the feature, so the next debate starts from data.
Ask the sales team and the support team the same two questions, separately, and lay their answers next to the customers'. Sales tends to overrate delighters, support tends to overrate must-bes. The gaps are the conversation.
Delighters decay into must-bes over time. Yesterday's surprise is today's expectation, and the note that charmed guests becomes the note they complain about when it is missing. Date every category.
Where Kano surveys mislead you
- Asking the team instead of customers. The team knows the roadmap and the competitor demo, and that knowledge contaminates the answers. Survey customers or close proxies, nobody else.
- Features described in internal words. "Unified account layer" gets "I am neutral" from everyone, because nobody understands it. Describe what the customer experiences.
- Treating indifferent as "later". Indifferent means the customer does not care. "Later" keeps it on the list, where it costs attention every quarter. Say no and write down why.
- A survey of 3 people presented as data. Three answers are three opinions. Below 10 respondents, call it a conversation.
Score and prioritise ideas with your team
IdeaHone scores ideas against your criteria, shows them on a matrix and keeps the reasons, so the decision is clear and traceable.
What is the Kano model?
A method from Noriaki Kano (1980s) that sorts product and service features into five categories by how they affect customer satisfaction: must-be, performance, attractive, indifferent and reverse.
Do respondents need an account?
No. In IdeaHone they open a link and answer; nothing that identifies them is stored. The organisation that sends the link decides who receives it.
How do you run a Kano survey?
For each feature, ask customers how they would feel if it were present and how if it were absent, each with the five answers like, expect, neutral, live with, dislike. The pair of answers places the feature in a category; the most frequent category wins. In IdeaHone you send the questions as a link and the evaluation happens on its own.
Can you use the Kano model in a workshop?
Yes, as long as the answers come from customers or close proxies, not from the team in the room. Send the survey link beforehand, let the team make its guess in the session, then compare it with the customers' answers, discuss the surprises and decide by category.
