Kano Model Analysis Tool

A way to sort features by how they affect satisfaction. Must-be features are expected, so nobody thanks you for them but everyone notices when they're missing. Performance features give more satisfaction the better they are. Attractive features delight people who didn't expect them. Indifferent features change nothing either way.

For each feature you ask two questions: "How would you feel if the product had this?" and "How would you feel if it didn't?" The answers are the same five each time: I like it that way, I expect it that way, I'm neutral, I can live with it, I dislike it that way. Each pair of answers maps to one category in the Kano evaluation table.

Better is (Attractive + Performance) divided by (Attractive + Performance + Must-be + Indifferent). It shows how much adding the feature could lift satisfaction. Worse is the same count with Performance and Must-be on top, shown as a negative. It shows how much leaving it out could hurt. Reverse and Questionable answers are left out of both.

The category shown is the one with the most answers. On a tie the tool picks Must-be first, then Performance, Attractive and Indifferent, and marks it as a tie. A lot of Questionable answers usually means people misread the question, so check the wording. How many people you need depends on how mixed your users are, so treat a small sample as a hint, not proof.

Yes. Add each answer pair with a count, or paste one respondent per line, such as "like, dislike". Your list is kept in this browser and shared with the RICE, ICE and MoSCoW modes. Log in to save it, or download a CSV.