To (ab)use a completely overused quote "If I had asked people what they wanted, they would have said faster horses" -- Henry Ford You should most certainly lis

To (ab)use a completely overused quote "If I had asked people what they wanted, they would have said faster horses" -- Henry Ford You should most certainly listen to your customers, after all, if you're not serving them, what's the point in the product? However, you shouldn't be reacting to their requests to the detriment of the product either. Do you AB test new feature ideas? Do you gather data to suggest that the requested feature is actually going to make a positive impact? Do you measure impact after releasing a feature to see if it was the right call? If not, how the heck can you ever actually know if you're building something better? You don't need to ignore your customers, but you also don't need to change priorities so often. Make a roadmap for X months and stick to it (we use 3 months, but something else might work better for you). Use the time that the roadmap is being worked on by the tech team to do discovery and research so that you know what the most valuable requests from your customers are. Collect metrics, create prototypes (design/ux prototypes, not technical prototypes) and test them with your customers, do customer interviews. Then when you're ready to, you'll have better prioritisation, and your teams will have had the space and stability to release the previous features (and hopefully had tech investment time as well to keep your systems maintainable).