How do you approach determining the key features to include in a new product roadmap?

During my final year at college, I worked on a team project to develop a mobile app aimed at helping students manage their coursework. To determine the key features for our app's roadmap, we conducted surveys among our peers to understand their needs. We found that students were particularly interested in features like assignment reminders, a calendar for deadlines, and study group functionalities. We prioritized these based on the frequency of requests and the potential impact on user experience. This approach not only helped us stay focused but also ensured that we were building something that would genuinely benefit our users.

I volunteered for a non-profit organization that aimed to create a fundraising platform for local charities. My role involved gathering insights from charity representatives about what features they would want. We organized focus groups where we discussed potential functionalities such as donation tracking, event management, and social sharing options. By prioritizing these features based on the feedback we received and the challenges the charities faced, we created a product roadmap that aligned with their goals. This experience taught me the importance of collaboration and user input in building effective products.

In my first role as a product assistant, I supported the product manager in developing a new software feature. I helped analyze customer feedback and usage analytics to identify the most requested features. We discovered that users wanted enhanced reporting capabilities and improved integrations with other tools. By participating in team discussions and analyzing data together, I learned how to evaluate trade-offs and prioritize features that aligned with our business strategy. This experience reinforced the importance of a data-driven approach and team collaboration in product development.