How do you determine which features to include in a product roadmap?

During my final year at university, I worked on a project to develop a campus app designed to enhance student engagement. We began by gathering feedback from students to identify their main pain points, such as finding study groups and accessing campus resources. We prioritized features like a study group finder and event calendar based on this feedback. Using a simple prioritization matrix, we weighed each feature against user impact and development complexity. This approach allowed us to focus on the most valuable features first while ensuring we addressed student needs effectively.

In my part-time job at a local coffee shop, I noticed that customers often asked for healthier snack options. Taking the initiative, I proposed that we survey our regulars to understand their preferences better. After analyzing the responses, I recommended adding items like gluten-free pastries and vegan snacks. I presented this data to the manager, highlighting how these additions could attract more customers and increase sales. By using customer feedback to guide our decisions, we revamped the menu and saw a positive response from patrons.

In my first job at a startup, I was involved in discussions about our product features. We maintained an ongoing backlog of potential features, and I learned to evaluate them based on user feedback, market trends, and business goals. For instance, when we received requests for better analytics tools, I helped compile data on user engagement and presented it to our team. By aligning our roadmap with user needs and business strategy, we successfully launched a new analytics feature that significantly improved user satisfaction and retention.