After years of leading product, I came to the conclusion that there always needs to be a process in place between customer feedback and development. All feedbac

After years of leading product, I came to the conclusion that there always needs to be a process in place between customer feedback and development. All feedback is appreciated, acknowledged, saved. If it 's not critical feedback (ie crash), feedback/feature request bucket will be reviewed regularly and then assessed based on: user benefit (how much does experience improve) impact (how many users will benefit from this) consequences (will other users/features suffer from this) ROI (how will it impact the company's, not purely monetary) requirement (time/cost to implement) goal/mission (does it align) Long story short: we NEED user feedback but it cannot dictate the roadmap (and therefore the mission). If you find yourself repeatedly needing to change your roadmap it might mean you're too quick/loose adding elements to it. Hope this helps!