Comments on: UIEtips: Understanding the Kano Model – A Tool for Sophisticated Designers http://www.uie.com/brainsparks/2011/01/18/uietips-kano-model/ UIE\'s latest insights on the world of design Sat, 18 May 2013 00:44:50 +0000 hourly 1 http://wordpress.org/?v=3.4.1 By: James http://www.uie.com/brainsparks/2011/01/18/uietips-kano-model/comment-page-1/#comment-165393 James Mon, 12 Sep 2011 15:43:27 +0000 http://www.uie.com/brainsparks/?p=3132#comment-165393 Flickr indeed were pioneers 'back in the day'. Perhaps they'd do well to read this article and rediscover some of the energy and ideas that made Flickr so exciting when it first came out: sadly, it's barely changed (or innovated) since. Flickr indeed were pioneers ‘back in the day’. Perhaps they’d do well to read this article and rediscover some of the energy and ideas that made Flickr so exciting when it first came out: sadly, it’s barely changed (or innovated) since.

]]> By: Rachel Oxburgh http://www.uie.com/brainsparks/2011/01/18/uietips-kano-model/comment-page-1/#comment-157687 Rachel Oxburgh Mon, 07 Mar 2011 11:46:34 +0000 http://www.uie.com/brainsparks/?p=3132#comment-157687 My issue with the Kano graphs is that they are somewhat ambiguous and that this ambiguity allows (in my view) for misleading interpretation. The horizontal axis (investment) appears to represent both whether a feature is present and whether it is well-executed. I would agree that absence of an 'excitement feature' can not disappoint a user, but I would argue that the presence of a poorly executed/sub-functional excitement feature can indeed lead to disappointment and frustration. I think it's an important points as the implication of the curve drawn is that you can't fail to add value with excitement features but in fact they need to be well executed and properly functional in order not to disappoint. My issue with the Kano graphs is that they are somewhat ambiguous and that this ambiguity allows (in my view) for misleading interpretation. The horizontal axis (investment) appears to represent both whether a feature is present and whether it is well-executed. I would agree that absence of an ‘excitement feature’ can not disappoint a user, but I would argue that the presence of a poorly executed/sub-functional excitement feature can indeed lead to disappointment and frustration. I think it’s an important points as the implication of the curve drawn is that you can’t fail to add value with excitement features but in fact they need to be well executed and properly functional in order not to disappoint.

]]> By: Joe Baz http://www.uie.com/brainsparks/2011/01/18/uietips-kano-model/comment-page-1/#comment-155925 Joe Baz Wed, 19 Jan 2011 03:22:40 +0000 http://www.uie.com/brainsparks/?p=3132#comment-155925 Anecdotally speaking, I've found this to be the case by seeing how critics compare software applications. When listing the pros and cons, they are very quick to highlight the cons of the application, be it feature or UX related. Ironically enough, for the software applications that work as expected they are not jumping for joy in their review. So the criticism is not parallel for software applications that don't innovate and build those excitement factors. The cost of doing business in the world of software is much higher today than it was thanks to folks like Google and Apple. Anecdotally speaking, I’ve found this to be the case by seeing how critics compare software applications.

When listing the pros and cons, they are very quick to highlight the cons of the application, be it feature or UX related. Ironically enough, for the software applications that work as expected they are not jumping for joy in their review.

So the criticism is not parallel for software applications that don’t innovate and build those excitement factors. The cost of doing business in the world of software is much higher today than it was thanks to folks like Google and Apple.

]]>