# Product Brief

A short, problem-focused document that frames a product opportunity, its intended users, strategic value, evidence, assumptions, constraints, and success signals.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-brief/>)

## What it means

A product brief is a lightweight framing document used before a team commits to a detailed solution. It explains the opportunity: whose problem matters, what happens today, why solving it supports strategy, what evidence exists, which assumptions remain uncertain, and what outcomes would justify further investment.

## Why it matters

Teams often rush from an interesting request to features and estimates. A product brief creates a deliberate pause for alignment and discovery without demanding a full specification. It gives decision-makers enough context to compare opportunities and gives researchers, designers, and engineers a common question to investigate.

## When to use it

Create a brief when an opportunity enters discovery, when a stakeholder proposes a substantial initiative, or when several teams need a common starting point. Use it before a PRD or delivery commitment. For tiny improvements, a clearly written problem statement may provide sufficient framing.

## How it works

1. Name the opportunity and identify the accountable owner and relevant collaborators.
2. Describe the target users, current situation, problem, and supporting evidence.
3. Connect the opportunity to product strategy and expected customer and business outcomes.
4. List assumptions, constraints, risks, dependencies, and questions that discovery must address.
5. Define decision criteria and next steps without prematurely prescribing a complete solution.

## A practical example

A collaboration product receives requests for automatic meeting summaries. Its brief identifies remote team leads as the initial audience, documents time lost reconstructing decisions, links interview evidence, notes privacy and language risks, and defines success as faster retrieval of agreed actions rather than simply shipping transcription.

## Where it breaks

A brief provides direction, not delivery-ready detail. If written only by the requester, it may present advocacy as evidence or omit affected users. If expanded into a large specification, it loses its speed and exploratory purpose. Teams must still test assumptions before committing significant resources.

## Common mistakes

- Opening with a preferred feature instead of the user problem.
- Using broad market claims without linking evidence or confidence levels.
- Turning the brief into a fixed contract rather than a discovery starting point.

## Sources

1. [Product Brief: Definition, Template & Best Practices](<https://www.productboard.com/glossary/product-brief/>) — Productboard · Professional guide
2. [How to create a product requirements document \(PRD\)](<https://www.atlassian.com/agile/product-management/requirements>) — Atlassian · Professional guide

## Related topics

- [Product Requirements Document](<https://wiki.soroush.uk/topic/product-requirements-document/>)
- [Product Vision](<https://wiki.soroush.uk/topic/product-vision/>)
- [Problem Framing](<https://wiki.soroush.uk/topic/problem-framing/>)
