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
What's wrong with the rational model We Don’t Really Know the Goal When We Start We Usually Don’t Know the Decision Tree – We Discover It as We Go The Nodes Are Really Not Design Decisions, but Tentative Complete Designs The Goodness Function Cannot be Evaluated Incrementally The Desiderata and Their Weightings Keep Changing The Constraints Keep Changing Frederick P. Brooks, Jr., What's Wrong With This Model? Changing constraintsDeciding what to designThe situation talks back