Sometimes, sometimes not. It depends. My mantra is still "Don't give users what they want, but what they need." Product Design is a one to many relationship,

Sometimes, sometimes not. It depends. My mantra is still "Don't give users what they want, but what they need." Product Design is a one to many relationship, while users are one to one tightly knit into their app. It isn't to discredit their input, it just needs to make sense in the whole picture: What if the one guy who reports 70% of all the features that would be cool and necessary to have, but 99% aren't using the product like he does? Is there another way to achieve that he wants even better, easier, faster, more reliably etc.? What if a a/b test showed, that they outright ignore or complain about such new features? Not building sounds so cool and rebellious, but it isn't about the not to build but overall product strategy and product itself that is the decision maker so to say. Because, you build a product in the first place, didn't you? Product Design and improvement is brutally hard. Backwards compatibility is the one thing you have to take into account all times. This can create the greatest friction there is and kill products. So how do you introduce a better way, that breaks with old traditions? Don't build it or use brainpower to solve the puzzle? Heads up to all the Platform Leads, Founders, Product Designers - tough world, but if it works it is heaven on earth. :D