How do you prioritize features in a product roadmap when there are conflicting stakeholder demands?

During my final year in college, I worked on a group project to develop a mobile app for our course. We had conflicting ideas on which features to include; some team members wanted to focus on user interface design while others emphasized functionality. To resolve this, I suggested we conduct a quick survey among potential users to gather feedback on what features they valued most. This data helped us prioritize features based on user needs, not just personal preferences. We ended up implementing a simple yet effective interface that included the most requested functionalities. This experience taught me the importance of using user feedback to guide prioritization and how to mediate discussions within a team.

As a volunteer for a local non-profit, I helped organize community events. When planning our annual festival, different stakeholders had varying priorities; the marketing team wanted to attract more sponsors, while the community group focused on family-friendly activities. To address this, I facilitated a brainstorming session where we listed all proposed features and their potential impact. We then rated each feature based on feasibility and alignment with our mission. This collaborative effort resulted in a balanced roadmap that included sponsor engagement opportunities alongside activities for families, ensuring a successful event that met everyone's needs. It reinforced my belief in the value of inclusive decision-making.

In my first job at a startup, I was involved in product discussions where different departments often had conflicting feature requests. For instance, the sales team pushed for customer relationship features while the tech team wanted to enhance backend efficiency. I initiated weekly meetings to discuss these requests and their alignment with our product vision. We created a prioritization framework that included user impact, business value, and implementation complexity. By systematically evaluating each request, we were able to create a balanced roadmap that satisfied both teams while moving the product forward. This experience taught me the importance of clear communication and structured prioritization in a collaborative environment.