Opportunity Assessment for Heads of Product: template, structure and example

When to use it

Create it in Discover when an opportunity could shift portfolio direction, funding or strategic position and senior stakeholders need a common basis for the decision. Use it to give executives something they can challenge early, before investment scales. It carries the opportunity into the Innovation Pipeline Register with evidence, a recommended decision and review cadence in place.

When not to use it

If the question is really about one team's specific customer problem, MVP scope and delivery effort, the Product Manager's Opportunity Assessment is the better fit. Skip it while the underlying problem is still unvalidated, where discovery work comes first. And once an opportunity is approved and funded, move to pipeline and delivery planning rather than reassessing it here.

What you need before you start

• The decision required, why the opportunity is being assessed now, and the target metrics it should influence
• Customer and market evidence of need, urgency, frequency, willingness to pay and demand signals
• A first-cut business rationale across revenue, retention, expansion, margin, strategic position or risk reduction
• Commercial context: buyer, budget owner, value metric, pricing or packaging, sales motion and success implications
• Competitive and alternative context, including how the need is met today and switching costs
• Feasibility and constraints across technical, operational, commercial, legal, security, data and regulatory dimensions

Recommended structure, section by section

1. Executive Summary — The opportunity, customer and business value, main risks, confidence level and recommended decision: pursue, shape, park or reject.
2. Purpose, Decision Context and Success Metrics — Why this opportunity is being assessed, the decision required and the target metrics it should influence.
3. Opportunity Definition — The opportunity, customer problem or demand behind it, target use case, timing and why action is relevant now.
4. Customer and Market Evidence — Evidence of need, urgency, frequency, willingness to pay, target segments and demand signals.
5. Value and Business Rationale — Potential value across revenue, retention, expansion, margin, strategic position or risk reduction, with a first-cut business rationale.
6. Commercial Model and GTM Fit — Buyer, budget owner, value metric, pricing or packaging implications, sales motion, onboarding impact and customer success implications.
7. Solution Hypotheses and Scope — Possible approaches at a high level, their assumptions, and what would and would not be in scope.
8. Competitive and Alternative Context — How the need is met today, competitors and substitutes considered, switching costs and how entry would be differentiated.
9. Feasibility and Constraints — Technical, operational, commercial, legal, security, data and regulatory feasibility, plus key dependencies.
10. Risks, Assumptions and Unknowns — The assumptions, risks and open questions that determine viability, ranked by potential impact on the decision.
11. Validation Plan and Kill Criteria — The experiments, research or analysis needed next, success thresholds, decision rules and conditions under which the opportunity should be stopped.
12. Options and Recommendation — Options considered, trade-offs across value, effort, risk, revenue, retention and speed, and the recommended decision with rationale.
13. Evidence, Assumptions and Confidence — Evidence sources, confidence level, assumption log, contradictory signals and further validation needed.
14. Ownership and Review Cadence — Who owns the assessment, next steps, review point and how the decision is recorded.

What good looks like

A strong Opportunity Assessment lets another product lead grasp the issue without a long verbal explanation. It is specific enough to guide action yet concise enough to be used, with the right evidence, stated assumptions, visible agreements and clear trade-offs. Senior stakeholders can see the recommended decision, the metrics it should move, the kill criteria and the review point, and understand what would make it need updating.

Quality checklist

• The executive summary states the recommended decision (pursue, shape, park or reject) with confidence level
• The decision context and target success metrics are explicit and agreed
• Commercial model and go-to-market fit are addressed, not just customer value
• The validation plan sets success thresholds, decision rules and kill criteria for stopping
• Options are compared across value, effort, risk, revenue, retention and speed with a clear recommendation
• Assumptions, risks and unknowns are ranked by their impact on the decision
• Ownership, review cadence and how the decision is recorded are named before sign-off

Who creates it, and when

In Gensudo this document is a governed template for:

• Head of Product in the Discover phase (as “Opportunity Assessment”)

Where it sits in the flow

Before this document: Customer Problem Statement for Product Managers · Market Research Report for Heads of Product

This unblocks: Validation Findings Report for Product Managers · Business Case for Heads of Product

Writing one from scratch? Read the step-by-step guide: How to Write an Opportunity Assessment: Steps, Examples and Checklist.

Frequently asked questions