How do you define a user's needs when starting a new product design project?

During my final year in college, I worked on a project where we designed a mobile app aimed at helping students manage their study schedules. To define user needs, my team and I conducted surveys among students to understand their study habits and challenges. We also held focus groups where we discussed features that could help them stay organized. Through this process, we discovered that students wanted reminders and a visual calendar feature to track their progress. By synthesizing this feedback, we prioritized these features in our design, which ultimately led to a more effective and user-friendly app.

While volunteering for a local non-profit, I was part of a team tasked with improving their community outreach program. To identify the needs of the community, we organized interviews and feedback sessions with local residents. Many expressed a need for more accessible information about available resources. We compiled our findings and recommended creating a user-friendly website that showcased these resources. This experience taught me the importance of directly engaging with users to understand their needs and ensure that the solutions we proposed were relevant and impactful.

In my first job as a junior designer, I was part of a team that was redesigning an e-commerce website. We started by analyzing existing user feedback and conducting usability tests. One key finding was that users struggled with the checkout process. We organized workshops where users could share their experiences and suggestions. Based on their input, we simplified the checkout process and added progress indicators. This resulted in a significant decrease in cart abandonment rates. This experience reinforced my belief in the value of continuous user engagement throughout the design process.