Product Discovery Brief for Heads of Product: template, structure and example

When to use it

Create it when discovery needs to serve portfolio direction and executive confidence, not just a single team's next step. Use it to state the core question and the customer, value, usability, feasibility and commercial hypotheses worth testing, so senior leaders can challenge the thinking before funding or strategic direction is committed. It suits discovery where methods and thresholds must be defensible to finance, technology and commercial partners. Reach for it when consistent product decision-making across teams depends on a shared, evidenced brief.

When not to use it

If the work is one team exploring a specific goal and decision, the Product Manager's Product Discovery Brief is the better fit and lighter to run. If commercial viability is already the open question, move to the Commercial Viability Assessment. Do not use it to record delivery progress; it exists to frame discovery and set the decision rules, not to report status.

What you need before you start

• The core discovery question and why it matters now, tied to the product or commercial outcomes it would unlock
• The customer, value, usability, feasibility and commercial hypotheses to test
• The customer, market, product and competitive context, with segment, persona, job-to-be-done, pains and current alternatives
• The discovery methods, activities, participant plan and the evidence and instrumentation to gather
• Confidence thresholds and the decision rules for proceed, pivot, park or stop
• Named input from Product Directors, finance, technology, commercial, operations, customer insight and executive sponsors

Recommended structure, section by section

1. Summary — The discovery question, why it matters now, the target customer or segment, and the decision it will inform. A few tight sentences.
2. Discovery Question and Hypotheses — The core question to answer and the customer, value, usability, feasibility and commercial hypotheses to test, and the product or commercial outcomes that make it worth running. One short paragraph.
3. Background and Target Customer — The customer, market, product and competitive context that frames the discovery, and the segment, persona, job-to-be-done, pains and current alternatives it centres on. A short paragraph.
4. Approach and Methods — The discovery methods, activities and participant plan, the evidence and instrumentation to be gathered, and what the discovery will and will not cover. A short paragraph.
5. Success Criteria and Decision Rules — What would count as a strong answer, the thresholds for confidence, and how findings will drive a proceed, pivot, park or stop decision. Three to five items.
6. Risks, Timeline and Next Steps — The riskiest assumptions, constraints and dependencies, the timeline, roles and decision owner, and the outputs the discovery will produce and where they hand off next. A short paragraph.

What good looks like

The best Product Discovery Brief feels practical: it teaches the reader what matters, then helps them act. Quality means the brief is supported by evidence rather than personal preference, with the right evidence for the document type, assumptions explained, agreements shown 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 discovery question is clear and the hypotheses across customer, value, usability, feasibility and commercial risk are stated
• Scope and exclusions are defined, with methods and participant plan set out
• Confidence thresholds and proceed, pivot, park or stop decision rules are explicit
• Evidence, risks, decisions and named owners are in place before sign-off is requested
• Reviewers challenge and agree the recommendation, accountable owner, risks, dependencies and next review date
• Final sign-off sits with the Head of Product, with senior leadership endorsement where funding, risk or strategic direction is affected

Who creates it, and when

In Gensudo this document is a governed template for:

• Head of Product 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

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

Frequently asked questions