Opportunity Prioritisation in Product Research

Turn a backlog of research-surfaced opportunities into a ranked, decision-ready shortlist. A practical scoring framework bridging synthesis and roadmap input.

Why Prioritisation Is Where Research Value Is Won or Lost
What Counts as a Product Opportunity
A Four-Dimension Opportunity Scoring Framework
Running a Prioritisation Workshop with Stakeholders
Real Example: From 22 Opportunities to a Three-Item Shortlist
Common Mistakes That Undermine Opportunity Prioritisation
Connecting Prioritised Opportunities to the Roadmap
Frequently Asked Questions

Why Prioritisation Is Where Research Value Is Won or Lost

Synthesis is generative by nature. A well-run discovery sprint produces far more opportunities than any product team can act on, and that abundance is the problem. Skip the prioritisation step and teams fall back on gut feel — or on whoever speaks loudest in the planning meeting.

The gap between a rich affinity map and a ranked shortlist is exactly where research loses credibility with stakeholders. A wall of clustered sticky notes is not a decision. A scored, tiered shortlist is. Opportunity prioritisation converts insight into roadmap input, and scoping it cleanly is the first move: it belongs after synthesis and before solution ideation.

This post sits within our Insight to Impact workflow, which covers the full arc from research planning through to stakeholder action. Here we focus on the prioritisation step itself — the mechanics of scoring, the workshop structure, and the hand-off format that keeps research visible in roadmap conversations.

What Counts as a Product Opportunity

An opportunity is an unmet need, friction point, or outcome gap experienced by a user or buyer. It is not a solution, and it is not a feature request. “Users cannot track their progress between sessions” is an opportunity. “Add a dashboard” is a solution — and a premature one.

Fix the distinction between an insight and an opportunity early. An insight is an observation: something you learned about behaviour, context, or motivation. An opportunity is the actionable problem space that observation points toward. Collapse the two and you end up with vague, unscoreable items that stall workshops.

Well-formed opportunities tend to come from structured interview synthesis, usability test findings, win-loss analysis, churn research, and survey open-ends coded for theme. Each source carries different evidential weight, which matters once you reach scoring.

Framing discipline pays downstream dividends. An opportunity written as a user outcome gap — “buyers cannot compare total cost across contract options before committing” — scores reliably on frequency, severity, and evidence confidence. An opportunity written as a vague theme — “pricing complexity” — does not.

A Four-Dimension Opportunity Scoring Framework

Most prioritisation frameworks — RICE, ICE, weighted scoring matrices — are designed for solutions. They ask how much reach a feature will have, how confident you are it will work, and how much effort it requires. Those are the right questions once you have chosen a problem to solve. They are the wrong questions before that choice is made.

The framework below scores problem spaces. It produces a comparable rank across opportunities, surfaces where evidence is thin, and separates the act of understanding from the act of deciding.

The four dimensions

1. Frequency (1–5) How often do users encounter this problem? Score 1 if it affects a narrow segment in rare circumstances; score 5 if it appears across the majority of your user base in routine workflows. Evidence from interview synthesis and survey data both feed this dimension.

2. Severity (1–5) How significantly does the problem affect the user when it occurs? A minor inconvenience scores low. A friction point that causes task abandonment, financial loss, or churn scores high. Usability findings and churn research are particularly useful here.

3. Strategic Fit (1–5) How well does addressing this opportunity align with the current business direction — target segment, growth lever, or declared outcome for the quarter? A high-frequency, high-severity problem in a segment you are deliberately exiting should score low on strategic fit. This dimension keeps the list honest about trade-offs rather than optimising purely for user pain.

4. Evidence Confidence (1–5) How well-evidenced is this opportunity? Score 1 for a single anecdotal mention; score 5 for a pattern validated across multiple methods — corroborated in interviews, confirmed in survey data, and visible in behavioural analytics. A score of 2 or 3 does not disqualify an opportunity; it flags it as a candidate for further research before roadmap inclusion.

Scoring and weighting

Each dimension runs from 1 to 5. A raw total out of 20 gives an initial rank. For early-stage products, strategic fit and frequency typically warrant higher weighting — the priority is finding the problems most central to core job completion. For scaling products with established user bases, severity and evidence confidence deserve more weight, because the cost of acting on a poorly understood problem is higher.

Evidence confidence deserves its own emphasis. Treat a single interview quote as equivalent to a finding validated across 40 survey responses and you will inflate confidence in weak signals. High frequency with low confidence is a trigger for more research — not immediate roadmap inclusion.

Relation to the opportunity solution tree

The opportunity solution tree — a tool for mapping how opportunities nest under desired outcomes and how solutions connect to those opportunities — is a natural complement to this framework. Scoring tells you which nodes to work on first; the tree gives you the structural context for how opportunities relate to one another. The two tools answer different questions and are most useful in sequence.

Running a Prioritisation Workshop with Stakeholders

Keep the workshop small: a product manager, the lead researcher, and a design lead. All three are decision-capable; none is present merely to observe. A larger group diffuses accountability and tilts toward consensus-seeking over calibrated disagreement.

Pre-work Before the session, the researcher prepares an opportunity long list — typically eight to fifteen items after an initial cull — with a brief evidence summary for each: source, volume of supporting data, and any direct observations that illustrate the problem. Participants review this independently before arriving. Scoring on the day without prior reading wastes session time and produces shallower scores.

Session structure Open with independent scoring. Each participant scores every opportunity across all four dimensions without discussion. This prevents anchoring — the first number spoken in a group typically pulls the rest toward it. Once individual scores are recorded, surface the outliers: opportunities where scores diverge by two or more points on any dimension. Those outliers contain the most useful information.

Calibration discussion focuses on the evidence. When a PM scores severity at 4 and the researcher scores it at 2, the question is not who is right — it is what evidence each person is drawing on. If the PM is extrapolating from a sales conversation and the researcher is drawing on eight usability sessions, the researcher’s score is better grounded. Evidence arbitrates; seniority does not.

Output tiers Produce three tiers rather than a single ranked list:

Act Now — high scores across all four dimensions; sufficient evidence to justify roadmap consideration
Investigate Further — high frequency or severity but low evidence confidence; the right response is more research, not immediate action
Parking Lot — low scores on multiple dimensions now, but documented for future reference

The tiered format is more honest than a ranked list. It acknowledges that some items are not ready for action, rather than implying that item five is simply less important than item four.

For guidance on presenting this output to a wider stakeholder audience, see our post on communicating research findings to stakeholders.

Real Example: From 22 Opportunities to a Three-Item Shortlist

On a product discovery engagement with a B2B SaaS team, synthesis from a six-week discovery sprint produced 22 distinct opportunities. The team had interviewed customers, reviewed support ticket themes, and run a churn survey with open-ended questions. The output was thorough — and paralysing. The backlog ranged from high-frequency onboarding friction to niche reporting gaps that affected fewer than 5% of active accounts.

Applying the four-dimension framework as a pre-workshop scoring exercise collapsed the 22 items to five candidates above a threshold total of 14 out of 20. Three scored consistently high across all dimensions. Two were borderline: one had high frequency scores but an evidence confidence rating of 2, because the signal had emerged in only three interviews and had not been tested in the survey.

The workshop produced a three-item Act Now shortlist in under two hours. The high-frequency, low-confidence item prompted a focused discussion. The PM’s instinct was to include it — the pattern had also appeared in recent sales calls. The researcher’s position was that three qualitative mentions and anecdotal sales feedback did not meet the threshold for roadmap confidence. The resolution: scope a four-week targeted study to test whether the pattern held across a broader sample, with a clear decision point built into the next planning cycle.

The team entered quarterly planning with a scored, evidence-backed shortlist and a defined research pipeline — rather than a slide deck of themes that each team member would have interpreted differently.

Common Mistakes That Undermine Opportunity Prioritisation

Scoring solutions disguised as opportunities. If your long list contains items like “build a progress tracker” or “improve the onboarding flow,” you are scoring proposed solutions, not problem spaces. Reframe before scoring: what is the user outcome gap that a progress tracker would address?

Ignoring evidence confidence. The most common scoring error is treating a single compelling interview quote the same as a finding corroborated across multiple methods. One vivid anecdote inflates frequency and severity estimates; the confidence dimension is the corrective.

Consensus-seeking over calibration. Average divergent scores without discussing them and you discard the signal in the disagreement. A score of 3 reached by averaging a 5 and a 1 tells you nothing useful. The 5 and the 1 tell you that two people are drawing on different evidence — and that gap is worth examining.

Treating the shortlist as permanent. Opportunities should be revisited as evidence accumulates and context shifts. A parking lot item from one quarter may become an Act Now item the next if churn data or a competitor move changes its strategic fit score.

Skipping the parking lot. Discarded opportunities need a documented home. Without one, the same low-priority items resurface in every planning session because no one can remember why they were previously set aside.

Connecting Prioritised Opportunities to the Roadmap

The hand-off format that works consistently is an opportunity card: a single-page summary containing the opportunity statement, the evidence summary, the score breakdown across all four dimensions, and a recommended next step — validate, build, or monitor.

That last field matters. Not every Act Now opportunity is ready to be built. Some need a validation study first. The card makes the researcher’s recommendation explicit without requiring the researcher to be present in every roadmap conversation.

Prioritised opportunities feed directly into an opportunity solution tree: scored items become the nodes the team focuses on, and solution ideation only begins once the problem space is confirmed. This sequence — prioritise problems, then explore solutions — is the discipline that prevents premature commitment before the problem is well understood.

The researcher’s role in roadmap conversations is to keep evidence visible, not to become a roadmap owner. A PM who can point to a scored opportunity card and explain why an item is on the roadmap has internalised the research. That is the signal the job is done.

For broader context on how this fits into a full research programme, see our product research hub.

Frequently Asked Questions

What is the difference between opportunity prioritisation and feature prioritisation?

Opportunity prioritisation ranks problem spaces — unmet needs and friction points — before any solution is defined. Feature prioritisation ranks proposed solutions. Run opportunity prioritisation first and you stop teams committing to a solution before the problem is well understood. The two processes are sequential, not interchangeable.

How many opportunities should be on a shortlist after prioritisation?

A working shortlist should contain three to five Act Now opportunities. That range gives the product team meaningful focus without forcing false trade-offs between genuinely different problem spaces. Items that score high on frequency but low on evidence confidence belong in the Investigate Further tier, not the shortlist.

How does an opportunity solution tree relate to opportunity prioritisation?

An opportunity solution tree maps how opportunities nest under desired outcomes, and how solutions then map to opportunities. Prioritisation scoring tells you which nodes in that tree to work on first. The two tools are complementary: scoring provides the rank; the tree provides the structural context.

Can opportunity prioritisation work without a dedicated researcher?

Yes, but the evidence confidence dimension becomes harder to score reliably. Product managers running their own discovery should apply extra scrutiny to confidence scores and be willing to delay roadmap inclusion when evidence is thin. Without researcher oversight it is easier to over-score confidence — the most consequential scoring error in the framework.

About Glasgow Research — Glasgow Research helps B2B SaaS teams turn customer and market research into product decisions. Work with us.