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

During my final year in college, I worked on a group project to develop a mobile app aimed at helping students organize their study schedules. We had limited time and resources, so we convened to prioritize features. We created a list of potential features and discussed each one’s impact on user experience and feasibility. For example, we decided that a simple calendar integration feature was critical, while advanced analytics could wait for a future version. We used a quick voting system where each team member could vote on their top three features, which helped us reach a consensus quickly. This experience taught me the importance of collaboration and balancing user needs with available resources.

As a volunteer for a local non-profit, I helped organize community events with a tight budget and a small team. We needed to prioritize which events to hold based on community interest and available funding. We conducted a survey to gather feedback on what types of events would attract the most participants. Based on the responses, we prioritized a free health workshop first because it had the highest demand. This taught me the significance of community feedback and how to make informed decisions based on limited resources, ensuring that we maximized our impact without overspending.

In my first job as a junior product assistant, I was part of a team that developed a new feature for a web application. We faced resource constraints and had to decide which features to implement first. I suggested using the RICE framework, evaluating each feature based on Reach, Impact, Confidence, and Effort. For instance, we determined that a user feedback collection tool would have a high impact with moderate effort, whereas a complex reporting feature would require more resources without immediate benefit. This structured approach helped us align with our stakeholders and deliver value to our users effectively.