How do you approach gathering user feedback when developing a product strategy?

During my final year in college, I worked on a group project to develop a mobile app aimed at improving campus navigation for new students. To gather user feedback, we conducted surveys among incoming freshmen. I created simple, targeted questions to understand their needs and preferences regarding app features. After analyzing the responses, we discovered that most students valued real-time updates on campus events and detailed maps. We incorporated this feedback, which significantly improved the app's usability and relevance. The end result was a product that not only won our class project competition but was also used by the university in subsequent years.

In my volunteer role with a local community center, I helped organize events aimed at engaging youth. To gather feedback, I initiated informal discussions with attendees after each event. By asking open-ended questions about their experiences and suggestions for future events, I was able to gather valuable insights. For instance, many attendees expressed interest in workshops rather than just social gatherings. Based on this feedback, we adjusted our strategy to include more hands-on activities, which led to increased participation and a more engaged community.

In my first job as a junior product assistant, I was involved in a team that was developing a new feature for an existing software product. We organized user testing sessions where we invited clients to interact with the prototype. I facilitated these sessions and took meticulous notes on their reactions and suggestions. One major insight was that users found the navigation confusing. We prioritized simplifying the user interface based on their feedback. This not only enhanced the product but also strengthened our relationship with our clients, as they felt their voices were heard in the development process.