How to Write an Opportunity Assessment: Steps, Examples and Checklist

Start from the customer problem and the evidence behind it, not the idea. State what the opportunity actually is, test how well it fits your strategy, and estimate the value honestly — ranges, not false precision. Lay out the realistic options, including doing nothing, then confront the assumptions and risks that could undo the case. Close with one recommendation, the specific decision you need, and a named owner. A reader who was never in the room should be able to judge whether the idea deserves deeper validation.

By Gensudo Team · Updated 23 July 2026

When you need this document

Write an opportunity assessment during Discover, once a validated customer problem has surfaced but before anyone commits research budget, design time or engineering effort to it. It is the bridge between an interesting signal and a deliberate decision to investigate. If you are being asked for funding rather than permission to validate, you have moved past this document — that is a business case.

Gather these first

The customer problem evidence that triggered the idea — interviews, support themes, usage data or a customer problem statement
Your current product strategy or portfolio priorities, so fit can be tested rather than asserted
A rough sense of market or segment size for the affected users
Known competitor moves or alternatives customers already use
The realistic options on the table, including the do-nothing baseline
The name of the person who will own the next step if the recommendation is accepted

Step by step

Write the opportunity as a problem, not a solution
Before anything else, express the opportunity in one or two sentences that name who is affected, what they struggle with, and why it matters now. Resist describing the feature you have in mind — the moment the document opens with a solution, every later section becomes advocacy rather than assessment. If you cannot state the problem without mentioning your solution, that is the first sign the opportunity is under-evidenced.
What good looks like: A colleague can repeat the opportunity back to you without using the name of any proposed feature.
Assemble the evidence and label its strength
Gather what you actually know: customer conversations, support volumes, usage patterns, market signals, sales feedback. For each piece, note where it came from and how strong it is — three enterprise customers asking is different from one loud voice in a workshop. Separate observed facts from your interpretation of them, and say plainly what you do not yet know rather than papering over the gaps.
What good looks like: Every claim in the document traces to a source a sceptical reviewer could check, and the gaps are stated rather than hidden.
Test strategic fit honestly
Put the opportunity against your stated strategy and current priorities and ask whether it genuinely advances them. This is where many assessments go soft: almost anything can be argued into 'strategic alignment' with enough creativity. Be specific about which objective it serves, what it would displace, and whether it belongs to this team at all. A genuinely good opportunity that belongs elsewhere is still a 'not us' recommendation.
What good looks like: The fit argument names a specific strategic objective and acknowledges what this work would push aside.
Size the value in honest ranges
Estimate the potential value — revenue, retention, cost saved, risk reduced — using ranges and stated assumptions rather than a single confident number. At this stage precision is fake; what reviewers need is the order of magnitude and the reasoning. Show your working: the segment size, the plausible adoption, the value per user, and which of those numbers you are least sure of.
What good looks like: The value estimate shows its assumptions and a reviewer can see which single number, if wrong, would collapse the case.
Set out the options, including doing nothing
Frame at least two or three genuine responses to the opportunity: pursue it now, defer and gather more evidence, address it a different way, or leave it alone. Give the do-nothing option a fair hearing — what actually happens if you ignore this for a year? An assessment with only one option is a pitch. The comparison forces you to articulate why now, and why this way.
What good looks like: Each option gets a fair paragraph, and the do-nothing case is described concretely rather than dismissed.
Surface the assumptions and risks that could kill it
List what must be true for the opportunity to be real — about demand, willingness to pay, feasibility, timing — and what could go wrong if you proceed. Rank them by how badly they would hurt and how uncertain you are. The most useful line in this section is the riskiest assumption, because that is exactly what the validation work should test first.
What good looks like: The riskiest assumption is named explicitly and points directly at what validation should test first.
Land one recommendation with a decision and an owner
Finish with a single recommended next step — validate, defer, or drop — the specific decision you are asking reviewers to make, who owns the follow-on work, and when the assessment should be revisited. Avoid the hedge of recommending 'further discussion'. If you are recommending validation, say what evidence would change your mind, so the next document has a clear job.
What good looks like: A reviewer can approve or reject the recommendation in one sitting because the ask, owner and next review date are all explicit.

Common mistakes

The assessment is a disguised pitch — one option, written to justify a feature the author already wants to build. — Write the options section before the recommendation, and give doing nothing a genuine paragraph. If every path leads to the same answer, reviewers will spot the reverse-engineering.
Value is stated as one precise number ('£2.4m ARR uplift') with no visible assumptions. — Use ranges with the working shown — segment size, adoption assumption, value per user. Precision at this stage signals overconfidence, not rigour, and invites reviewers to attack the number instead of the opportunity.
Strategic fit is asserted in a sentence ('aligns with our growth strategy') rather than argued. — Name the specific objective the opportunity serves and what it would displace. If you cannot say what loses priority to make room, the fit claim is empty.
Evidence and opinion are blended, so reviewers cannot tell what was observed from what the author believes. — Attribute every claim — 'six of nine interviewed admins raised this' reads very differently from 'users are frustrated'. Keep interpretation in its own sentences, clearly flagged as yours.
The document ends without an ask, so it gets discussed but nothing is decided. — Close with the exact decision required, one recommendation, a named owner and a review date. An assessment that does not request a decision is a briefing note.

Before you call it done

The opportunity is stated as a customer problem, without naming a solution
Every factual claim has a checkable source, and known gaps are stated plainly
Strategic fit names a specific objective and what the work would displace
Value is expressed as a range with assumptions visible
At least two options are assessed, and doing nothing gets a fair hearing
The riskiest assumption is identified and points at what validation should test
The recommendation, decision required, owner and next review date are explicit

Frequently asked questions

How long should an opportunity assessment be?

Two to four pages is usually enough. The document's job is to support a validate-or-drop decision, not to exhaust the topic — depth comes later, in validation work and the business case. If it is running longer, you are probably including material that belongs in a follow-on document, or compensating for weak evidence with volume.

How is an opportunity assessment different from a business case?

An opportunity assessment asks whether an idea deserves deeper validation; a business case asks whether a validated opportunity deserves funding and organisational commitment. The assessment comes first, works with rougher evidence, and its worst outcome is a little wasted research. The business case carries financial rigour — costs, returns, commercial assumptions — because its worst outcome is a funded failure.

What if the evidence is thin — should I still write one?

Yes, and say so plainly. An honest assessment built on thin evidence is still useful: it tells reviewers exactly what is unknown and what the cheapest way to find out would be. The failure mode is not thin evidence — it is thin evidence dressed up as conviction. State what you know, what you assume, and what you would test first.

Who should sign off an opportunity assessment?

Typically the product manager owns the document and the recommendation, with agreement from the accountable product, design and delivery leads. Reviewers should be approving something specific: the recommendation, the decision required, the named owner, the key risks and the date it gets revisited. In Gensudo, the Opportunity Assessment template carries this sign-off guidance alongside every section.

Start from the structured template

See the full Opportunity Assessment for Product Managers template and structure, or draft it in Gensudo with cited evidence.

Get started