Curated Resource ( ? )

Using The Kano Model To Prioritize Product Development - Mind the Product

Using The Kano Model To Prioritize Product Development - Mind the Product

my notes ( ? )

The image is bad - it's a graph, not a grid, unless you can somehow make a negative investment. Anyway, the model distinguishes "between basic and differentiating features.. improving certain aspects only serves to maintain basic expectations, whereas improving other aspects can delight customers with less effort"

Basic features should be met because failing to do so will cost you dearly, but investing beyond meeting user expectations is wasteful: noone will rave about it.

"features that delight the user... score very highly on satisfaction and ... may not take as much investment... [but] will migrate from delightful to basic... something they expect " over time

Read the Full Post

The above notes were curated from the full post

Related reading

More Stuff I Like

More Stuff tagged project management , product/market fit

See also: Digital Transformation , Change & Project Management , Business

Cookies disclaimer saves very few cookies onto your device: we need some to monitor site traffic using Google Analytics, while another protects you from a cross-site request forgeries. Nevertheless, you can disable the usage of cookies by changing the settings of your browser. By browsing our website without changing the browser settings, you grant us permission to store that information on your device. More details in our Privacy Policy.