How do you prioritize various validated problems?

One way I like to prioritize problems is based on the level of risk these will pose to the final solution. Which are the riskiest assumptions or riskiest bets that will affect the success of your product? (Risk can be defined crudely in terms of Low, Medium, High or in some cases you might have a model with some sensitivity analysis built in). Regardless, if you can quantify the risk (and thus impact) of the problem to the final solution, you have a clear blueprint of where to begin. A related m ...Read More

There isn't a single right answer to this but a framework I've found useful factors in user persona, problem severity, market size, fit with company's strengths and finally, a set of vocal early adopters. Clear User Persona: Can we clearly describe who has this problem? If the answer is vague or scattered, that’s a red flag. Problems tied to a well-defined user tend to be easier to validate and solve. Underserved Problem : Is this something current tools or workflows don’t solve well? Look for h ...Read More

Usually, there is a pre-determined prioritization framework that your product org should use to prioritize which problems to work on. There are multiple inputs with different weightage that are used in the prioritization framework, depending on the phase of the product, business and company. The most common inputs are: business and strategic product priorities degree of user friction (eg: adoption blocker vs nice to have) market and sales priorities (eg: is delivery of a feature important to win ...Read More

Prioritizing validated problems ensures you are focusing on the most pressing problem that will have the largest impact. It is finding out what will give you the biggest bang for your buck. Prioritization requires a thoughtful and strategic approach. Here are some ways to prioritize various validated problems: Assess the impact: Evaluate the impact of each problem on the user and the business. This can include factors such as how many users are affected, how much time or money is lost due to the ...Read More

I typically take the following into consideration for prioritising (in no particular order): Assess impact: Evaluate the magnitude and consequences of each problem. Align with business objectives: Prioritize problems that align with strategic goals. Evaluate urgency: Consider the severity and time sensitivity of each problem. Consider feasibility: Assess the resources and complexity required to address each problem. User feedback and demand: Give priority to problems frequently reported by users ...Read More

It depends on the product outcomes you are looking to drive based on your company goals. For e.g. if your NPS is really low then understand what is causing that NPS to be low and prioritize those. If your customers are churning then figure out why and prioritize that. If you have a lot of great capabilities but you are not making money then figure out whether you need to invest in repackaging and pricing. Every company has come combination of customer growth, retention, and monetization investme ...Read More

For a new 0 to 1 product offering, prioritization is biased for rapid learning, user adoption and market feedback. So encourage thinking in the following dimensions:  Core value differentiation:  Prioritize features that drive a strong, compelling reason for why your product exist  Prioritize and focus on executing the single most compelling problem that reiterates your product’s unique value proposition  Once your top priority problem to solve for is identified, use the standard effort vs. impa ...Read More