That definitely happens, but I think a lot of the blunders are due to good intentions with poor execution or not enough thought into the need and demand.
Things like adding features to solve a problem, when those problems only affect a small percentage of users, is something I see a lot. Especially in the beginning of a product when you’re not 100% sure what you’re making or who you’re making it for and you want to appease all of your customers so you don’t lose them.
Or the feature added is too complex to be useful for a user without training / tutorials, of which few users will undertake that time investment.
I have yet to be on a team where features were not trying to directly address a customer issue / complaint, but maybe I’ve been lucky.
Things like adding features to solve a problem, when those problems only affect a small percentage of users, is something I see a lot. Especially in the beginning of a product when you’re not 100% sure what you’re making or who you’re making it for and you want to appease all of your customers so you don’t lose them.
Or the feature added is too complex to be useful for a user without training / tutorials, of which few users will undertake that time investment.
I have yet to be on a team where features were not trying to directly address a customer issue / complaint, but maybe I’ve been lucky.