PM Quest · Practice cases · Learning resources

Navigating Product Roadmap Shifts from Critical User and Stakeholder Feedback

Behavioral · intermediate

Describe a situation where critical user feedback or a key stakeholder's strong objection led you to significantly alter your planned product roadmap or a specific feature's design. How did you navigate that?

Write your approach on PM Quest

Community approaches

Pavlo’s approach

There was a moment during a product development when we realized that the we were trying to target the less valuable users, while the most important users staid without enough attention. We had a long planned roadmap and were going through it according to the plan with metrics clearly indicating that we were doing good. However, a group of users who really needed an appreciated our product was formed quietly and we didn't think about their needs. One day we received a feedback with feature request from one of such users. Deeply analyzed why she requested those features, we found that there were many similar users and all of them had purchased the maximum tier of the product. First, I gathered and illustrated all the data. Then I presented it to key stakeholders. After receiving the approvement of roadmap adjustment from key stakeholders, I communicated the changes with the team. Finally I adjusted all the documentation, planning phases and set new metrics needed for tracking progress.