Skip to main content

Digging into Kano model: conducting study and analyzing results

Kano study could be a highly needed touch point with your customer. During the study, you can ask critical questions and get to the essence of your customer's needs, perceptions, and motivations. Asking "why?" is a superpower.

Kano analysis helps you uncover personas 

When analysing the responses to the Kano study - you might spot significant differences in a customer reaction to a particular topic. It might be an indication that you have uncovered a new persona. Every product has different user and customer personas.
In user-centered design and marketing, personas are fictional characters created to represent the different user types. 
Personas are multidimensional. The following persona types could apply to almost any product: early adopter, early majority, late majority, laggards. Those archetypes might have significantly different emotional reactions to certain features of your product. Moreover, when features change type - that could be spotted with a persona. Kano study could give you such insights.

Prioritizing results and comparing product features

How to analyse Kano study results to find out what features are the most preferable for customers?

Add importance question

One way is to add a feature importance question to a pair of functional\dysfunctional questions. For every feature, you ask customer one additional question: "how important this feature is?" An answer should be provided on a scale from 1 to 9, from "Not at all important" to "Extremely important".

Another way is to do a statistical analysis of Kano study results. Standard deviation will help you spot the significance of results.  This method has been described by Bill DuMouchel.

Jan Moorman in her excellent UXmag article suggests another, visual way to present Kano study results. It lists product features and satisfaction\dissatisfaction scales against them.
Features sorted by the most potentially dissatisfying, if not included, on top. By looking at such picture you immediately see what features you should focus on. This is a useful way to present Kano study results to the dev team and other parts of a business.

How to discover "Attractive" features

Customers are not expecting attractive features, therefore those are hard to uncover by just asking the Kano questions. What can you do to discover these? The best way is to do qualitative research: observation, interviews, focus groups. You need to understand how your customers are solving their problems and then be creative to figure out how your solution might help them to be more effective\satisfied.

Improving existing features has a limit

Kano model clearly shows that your product will not be hugely successful if you'll focus only on the optimisation of existing features. Improving "must-have" features might reduce customer dissatisfaction, but it will not help you leap forward.  Without attractive features, without delighters, your product will be "just another one".

How many customers should you ask?

The answer is pretty simple (in theory): you need as many people to get statistical confidence. For some studies 6 respondents are enough, for some it could be 12, 24, 48, 64...etc. The following basic rules apply: you need a representable group of participants. To spot the more significant differences, you need fewer participants. While more granular results require more respondents.
Tip: When defining your participants' list check how chosen people correspond to your personas.

Best practices to conduct a Kano study

  • Ensure the chosen participants represent your target group (definition of a persona)
  • Let participants experience features rather than hear about them (present your prototype or watch them using your product)
  • Record participants reactions to your product
  • Do the statistical analysis on the result to make sure you have statistically significant results

Prioritization rule: M > O > A > U

Popular posts from this blog

Product management and operations tools - Jira Product Discovery review

  JPD is a new player in the market of product management software. Jira (and the whole Atlassian suite) has been one of the most popular tool stacks for teams to deliver software products. Now they're adding a missing piece - product discovery.

Product Vision: an elevator pitch for your product

On this blog, I write a lot about making data-driven decisions . But what if you just starting to think about your product? You have a vague idea and nothing more. No point to go for prototyping or even talking to customers as you don't know yet who to talk to and what to talk about. In such situation - start from creating a product vision.

2 simple but powerful filters for your problem and product ideas

Nowadays lots of people and companies want to innovate. They want to generate new ideas and turn them into profitable products. But how would you separate good ideas from not so good ones? How would you make sure you invest only in good ideas?