What are the best ways to prioritize product roadmap conflicts?

Prioritizing product roadmap conflicts is all about understanding what your customers need most and balancing that with what's actually possible to do. It's important to keep an eye on the long-term goals of your product while listening to your team's ideas. Sometimes, you have to make tough decisions because not everything can be a priority. It's about focusing on what will have the biggest impact on your product's success right now.

The shorter time estimation is also an importan criteria, any combination of criteria divided by time estimation could be the best priorization criteria

I define my criteria based on a clear product strategy! This means: 1. Understanding the why of the product, idea, or feature. 2. Doing research and validation about the market, users, willingness to pay, and product. 3. Defining the outcome I want to reach. 4. Defining the go-to-market strategy 5. Aligning business, product, and user needs.

Gather feedback should come from the following sources: 1. Users 2. Interaction 3. Stakeholders 4. Third parties 5. Market Once you have this information, try to identify what insights are common between audiences and prioritize them against business, user, and product needs. Include them in the roadmap, and start the process again. Remember to have a continuous discovery process to maintain your product delivering value.

Before you can prioritize anything, you need to have a clear set of criteria to evaluate and compare different options. These criteria should reflect your product strategy, target market, value proposition, and key metrics, such as customer value, business value, technical feasibility, and risk and uncertainty.

Once you have the information selected, prioritize your roadmap based on business, user, and product needs and expected outcomes. Remember to include in this prioritization your team, main users, stakeholders, and third parties. Once you have a final version of your roadmap, share the document with all people that is required. I will say that to all the audiences presented above. Be aware of filtering the information according to the audience.

From my experience, your roadmap should be reviewed and iterated it once you finish each sprint. If you are launching a new product or MVP, probably is not going to be that often, but I your product is already in the market you should iterate constantly. A roadmap can be affected by: 1. Users needs 2. Interaction - Funnels of conversions 3. Stakeholders 4. Third parties 5. Market Be aware of the impact vs effort of each decision you are making in your roadmap to prioritize value delivery.

Regarding the prioritization techniques, I love to use RICE, because you can find a balance between impact, effort, and probability.