How do you prioritize features during the product design phase, especially when facing conflicting user needs?

During my final year project at university, I worked on developing an app for student collaboration. We conducted surveys and interviews with potential users to understand their needs. When faced with conflicting preferences—some users wanted a simple interface, while others desired advanced features—I prioritized by creating a minimal viable product (MVP) that included essential functionalities, like messaging and file sharing. This allowed us to gather feedback and iterate on the design based on actual user interaction, ensuring that the most critical needs were met while preparing for future enhancements.

As a volunteer for a local NGO, I helped design an app aimed at connecting volunteers with community service opportunities. We faced conflicting user needs; some volunteers preferred a straightforward signup process, while organizations wanted detailed profiles to vet volunteers. To address this, I facilitated a workshop where we mapped out user journeys and identified common ground. We decided to implement a dual approach: a simplified signup for volunteers and a comprehensive verification process for organizations. This solution catered to both parties while maintaining user friendliness.

During my internship at a tech startup, I was part of a team tasked with enhancing an existing mobile application. We encountered conflicting requests from users who wanted new features while others reported issues with the current ones. I suggested we use a prioritization matrix to evaluate features based on user impact and development effort. By doing this, we focused on fixing critical bugs first, which improved user satisfaction, before rolling out new features. This experience taught me the importance of balancing immediate user needs with longer-term product goals.