Product Discovery Brief for Product Managers: template, structure and example

When to use it

Create it at the start of Discover, before time is spent on research or concepting, so the work has a clear brief rather than a vague remit. Use it when your team needs a common basis for decisions and you want senior stakeholders to challenge the thinking early, before cost and effort increase. It suits a specific goal or decision where the problem, users and questions can be stated plainly. It is the right document when discovery is exploratory and you need to separate what is known from what is still uncertain.

When not to use it

If you have already validated the problem and are ready to commit to a bet, move to the Product Hypothesis Document instead. If discovery spans a portfolio or requires executive funding and strategic endorsement, the Head of Product's brief operates at that level. Avoid it as a status report; it is a direction-setter, not a progress update.

What you need before you start

• The goal or decision that makes discovery needed now, and the customer and business outcome sought
• The problem or opportunity space and the target users, customers and segments it centres on
• The riskiest assumptions and hypotheses across problem, value, feasibility and adoption risk
• The planned research and analysis activities, and how evidence will be captured
• What is in and out of scope for this discovery
• Named input from Product Owner, design, engineering, data, delivery, customer insight, sales and marketing

Recommended structure, section by section

1. Summary — The discovery scope, the decision needed, the target users, and the learning outcome. One short paragraph.
2. Goal and Decision — The context and reason discovery is needed now, the customer and business outcome sought, and the decision it must enable. A few tight sentences.
3. Problem and Users — The problem or opportunity space being explored and the target users, customers and segments it centres on. A short paragraph.
4. Questions and Assumptions — The questions discovery must answer and the riskiest assumptions and hypotheses to test, tied to problem, value, feasibility and adoption risk. A structured list.
5. Scope and Approach — What is in and out of scope, the planned research and analysis activities in sequence, and how evidence will be captured. A short list.
6. Success and Decision Checkpoint — The evidence threshold, the learning outputs, and the checkpoint for deciding to proceed, pivot or stop. A few sentences.

What good looks like

A good Product Discovery Brief is easy to follow and gives you confidence in the thinking behind it. The reader can see the link between the information presented and the decision being asked for, with evidence separated from opinion, assumptions explained and trade-offs made visible. A new reader can describe the purpose of the discovery, understand the recommended next step, see who has approved it, and identify what would make it need updating.

Quality checklist

• The question discovery must answer is clear, and scope and exclusions are stated
• Evidence, risks, decisions and named owners are captured before sign-off is requested
• Assumptions are explained and trade-offs are visible, with evidence separated from opinion
• The success threshold and the proceed, pivot or stop checkpoint are defined
• Reviewers confirm the recommendation, decision required, accountable owner, risks, dependencies and next review date
• Final sign-off sits with the Product Manager, with agreement from accountable product, design and delivery leads

Who creates it, and when

In Gensudo this document is a governed template for:

• Product Manager in the Discover phase (as “Product Discovery Brief”)

Where it sits in the flow

Before this document: Customer Problem Statement for Product Managers

This unblocks: Market Research Report for Heads of Product · Competitive Analysis for Product Managers · Opportunity Assessment for Product Managers

Prefer to see one finished? Read a complete, cited Product Discovery Brief for Product Managers example for a early-years edtech product.

Writing one from scratch? Read the step-by-step guide: How to Write a Product Discovery Brief: Steps, Examples and Checklist.

Frequently asked questions