Problem-Opportunity Scoring Model

Needs can come from different users of your product, or from different internal stakeholders who sometimes may conflict with each other. For example, one stakeholder may want you to incorporate in your product the ability to snap photos and post them on social media. Another stakeholder may want an Artificial Intelligence (AI) system that is able to understand human language and perform tasks as directed.

As a Product Manager, you know that you will not be able to satisfy all of these needs at once. There are different ways to prioritize the needs and one that I like to use is the Problem-Opportunity Scoring Model. I like this model because it grounds the decision on a deeper understanding of the problem each stakeholder is trying to solve, providing for better context in making a decision.

Evaluating problems and needs

Start by understanding each need in detail, especially the problem that your user or stakeholder is trying to solve (I find it useful to write these as problem statements focusing on the context, the user, the problem, and the impact to the user). Then, define a few dimensions that make sense for you and that can help quantify each need. For example, you may consider the following dimensions:

Severity = How severe is the problem when users experience it?

Frequency = How frequently does the problem occur?

Population size = Are there few or many people experiencing it?

Value = What is the value to the customers and/or to the business if we solve this?

Opportunity = Does solving this need create a greater opportunity for the business?

Next, estimate these dimensions for each of the needs you have in your list. Assign a score of 1 to 10 to each dimension; 10 being the highest. Use relative estimation to compare different needs, and you do not need to use all of the values (e.g., different needs may score “2” for the same dimension).

Once you have scored each need across the dimensions, you can add the values and rank the needs from highest to lowest. This gives you a sense of the priorities and which need to solve first.

Evaluating features and ideas

There are many familiar frameworks that PMs use to evaluate features: RICE, Kano Model, WSJF, Impact-Effort Matrix, etc. These are well established frameworks and I will not delve into the details. The Problem-Opportunity Scoring Model can be applied to evaluating features and ideas too.

Simplified Scoring

The Problem-Opportunity Scoring Model is a useful framework to evaluate ideas and score them. The challenge is to choose the right criteria to score the ideas on. This is where the “art” of Product Management cannot be replaced by a programmatic framework: each situation and each product is different, and you need to apply your judgment to make decisions.

Here’s what I’d suggest: start simple, and deepen your evaluation as you go. Here is a simplified scoring matrix across 4 key dimensions:

Dimension	What You’re Evaluating	Score 1-5
Impact	Combined user value + business value. Will this idea move important metrics?
Feasibility	Effort, technical complexity, dependencies. Can we actually build this?
Strategic Fit	Alignment with company vision, roadmap themes, core competencies
Confidence	How validated is this? Do we have data/research supporting the problem-solution fit?

Simple scoring guide:

• 1-2: Low (questionable value, very hard, misaligned, or highly speculative)
• 3: Medium (moderate on this dimension)
• 4-5: High (strong value, feasible, aligned, or well-validated)

Expanded Idea Scoring

For your top 5-10 ideas, you can go deeper with additional criteria. Here again, use your judgment to select the criteria that make sense for your product, your industry, or your customers. Here is a list of additional criteria you may want to consider:

• Problem-Solution Fit: How well does this solution address the underlying problem?
• Data availability: Do we have the right data / model to support it?
• Market Timing: Is now the right time? Are users/market ready?
• Market Size: How big is the market for this idea?
• Competitive Positioning: Does this strengthen our moat or create vulnerability?
• Dependencies: What needs to happen first? Who do we need buy-in from?
• Risk Assessment: What could go wrong? What’s the downside if we’re wrong?

Idea Validation

Consider that an idea is just an idea – until you do something about it. It may seem a great idea or an “absolute winner”, but until you validate it with your users, you don’t really know it. So, in addition to evaluating/scoring your ideas, you might also want to prototype or do user research to validate assumptions. More on this later.

e different outputs. This makes regression testing more complicated (among other things).