Intro to Kano Analysis

Bloggers in the same "circle" as I have recently paid a fair amount of attention to Kano analysis. I wrote in a previous entry that true Kano analysis differs a bit from popular portrayals. What follows is an introduction to Kano analysis. I intend this introduction merely to explain what it is and what people do with it.

You use Kano analysis to help you decide what to put in your product. It helps you determine the relative importance of features or requirements.

With Kano analysis, you categorize possible attributes of your product as:

attractive - satisfies users when present but does not dissatisfy users when not present
one-dimensional - satisfies users when present and dissatisfies them when not present
must-be - taken for granted, but dissatisfies users when not present
indifferent - results in neither user satisfaction nor user dissatisfaction
reverse - dissatisfies users when present and satisfies them when not present

Informed Kano analysis requires researching your market. One way of obtaining quantitative data is to conduct a survey. Kano recommended using pairs of questions such as:

If the product has feature x, how would you feel?
1. I like it that way.
2. It must be that way.
3. I am neutral.
4. I can live with it that way.
5. I dislike it that way.

If the product does not have feature x, how would you feel?
1. I like it that way.
2. It must be that way.
3. I am neutral.
4. I can live with it that way.
5. I dislike it that way.

From the answers to the questionnaire, you use a somewhat complex algorithm for evaluating the importance of each feature.

Comments

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

Cauvin

Search This Blog