Minimum Awesome Product An Article by Carlos Beneyto theuxblog.com Show image 0 Show image 1 Users are accustomed to a minimum of quality, and they expect that of all new products. If our product does not [meet basic expectations of quality], people will automatically believe that it is a bad product and they will not take it seriously. It is not what they expect. Hence my suggestion that the MVP has died and the MAP: Minimum Awesome Product was born. Understanding the Kano ModelDon't Serve Burnt PizzaWhat happens to user experience in a minimum viable product? qualityuxfeaturessoftware
When users never use the features they asked for An Article by Austin Z. Henley web.eecs.utk.edu We deployed our tool. Almost no one used it. The handful that did use it, used it once or twice and barely interacted with it. After a few days, zero people were using it. Why did they tell me they wanted these features? featuresuxresearch