How do you prioritize features in a product roadmap when faced with limited resources?

During my final year in college, I was part of a team working on a mobile app project for a local business. We had limited time and resources, so we needed to prioritize features that would deliver the most value to the client. We conducted a quick survey of potential users to identify which features they found most appealing. Based on the feedback, we focused on implementing a user-friendly interface and a basic functionality that met the core needs of the business. This approach not only helped us stay within our timeline but also resulted in a successful presentation to the client, who appreciated our focus on their most critical needs.

While volunteering at my university's student club, we often organized events with limited budgets and time. One particular semester, we had to choose between hosting a workshop or a networking event. We decided to gather input from club members on social media to gauge interest. The feedback indicated a strong desire for networking opportunities, so we prioritized that event. We leveraged partnerships with local businesses to secure sponsorships, which allowed us to deliver a successful event that brought together students and industry professionals. This experience taught me the importance of actively engaging stakeholders and making informed decisions based on their feedback.

In my first job as a junior product associate, we were tasked with rolling out a software update with limited developer resources. I collaborated with the product manager to analyze user feedback and usage data. We identified that users struggled with a specific feature that caused frequent support tickets. By prioritizing the fix for this feature over less critical updates, we were able to enhance user satisfaction significantly. This experience underscored the importance of aligning product roadmaps with actual user needs and leveraging data-driven insights to make prioritization decisions.