What criteria would you use to prioritize product features when stakeholder opinions vary widely?

In my final year of college, I worked on a project where our team had to develop a mobile app. Each member had different ideas for features, leading to disagreement. To prioritize, we held a brainstorming session where everyone presented their ideas. We then used a simple voting system to gauge interest. After that, we evaluated each feature based on user value and implementation effort. For instance, while one member wanted advanced statistics, we realized most users preferred a simple user interface. This method helped us focus on the most valuable features for our users, leading to a successful project presentation.

During my time volunteering for a local NGO, we faced differing opinions on activities for a community event. To determine what to prioritize, I suggested we conduct a survey among community members. We gathered feedback on what activities they found most appealing. This data helped us focus on the most desired features, like workshops and games. By aligning our decision with community preferences, we increased participation significantly compared to previous events, showing the importance of stakeholder input in prioritizing features.

In my first role as a junior product assistant, I was involved in a project where different departments had conflicting views on which features to develop for an update. I organized a meeting with representatives from each department to discuss their needs. We created a prioritization matrix that included factors like customer feedback, revenue potential, and technical feasibility. For example, while sales wanted new promotional tools, customer support emphasized fixing existing issues. The matrix helped us reach a compromise that balanced immediate fixes with long-term enhancements, improving both customer satisfaction and sales.