Problem claim
Not yet statedNot stated yet.
Supporting: none recorded
Counter-evidence: none recorded
Assumptions: none linked
Open questions: none linked
Free editable template
Product Brief Template
Align on the problem, evidence, desired outcome, candidate direction, boundaries and unresolved decisions before detailed requirements create false certainty.
A product brief is intentionally lightweight. It should help the team decide whether to proceed, investigate further, compare directions, or stop, and it should make the evidence behind each claim inspectable instead of pretending a short document validates the opportunity by itself.
No loginAutosaves in this browserBrief Claim & Evidence MapInvestment Decision AuditPRD Handoff ContractMarkdown / JSON / PDF
Evidence-to-Investment Decision Contract
Keep the problem, evidence and next decision separate
Connect material claims to real evidence, keep counter-evidence and assumptions visible, and show what must still be learned or decided before deeper definition, without manufacturing certainty.
Draft / framing incompleteAudit: 0 blocker · 5 needs decision · 2 review · 2 infoDraft autosaves in this browser's local storage.
1. Decision this brief supports
A brief exists to unlock one bounded decision: investigate, compare directions, align, proceed, park or stop.
2. Problem claim
Describe what is happening today. The claim must not depend on the proposed solution being true.
3. Evidence and counter-evidence
Evidence is not proof. Record the source, what it supports or contradicts, and whether it is direct, repeated, proxy, interpretation or conflicting.
No evidence yet. Add the observations, data or requests behind the problem claim.
10× asset
Brief Claim & Evidence Map
Each material claim shows its status, the evidence that supports it, the evidence that weakens it, and the assumptions or questions it depends on.
Outcome claim
Not yet statedNot stated yet.
Supporting: none recorded
Counter-evidence: none recorded
Assumptions: none linked
Open questions: none linked
Direction claim
Not yet statedNot stated yet.
Supporting: none recorded
Counter-evidence: none recorded
Assumptions: none linked
Open questions: none linked
4. Why now and desired outcome
A real problem can exist without deserving immediate investment. An outcome is what changes, not what ships.
5. Candidate direction and alternatives
A direction is not a commitment. Keep it high level; detailed behavior belongs in the PRD. Record what could compete with it, including the alternative explanation and doing nothing.
Alternatives considered
No alternative recorded. Add a competing direction, an alternative explanation, or the do-nothing option.
6. Scope, non-goals and constraints
Constraints are separate from assumptions and risks. Non-goals matter more as ambiguity grows; a tiny reversible change may not need one.
No constraint recorded. If constraints are unknown, note that explicitly rather than assuming none.
7. Assumptions, risks and open questions
Assumptions are believed-but-unevidenced statements. Risks are potential negative outcomes. Open questions can block the next decision, matter later, or belong to the PRD.
Assumptions
No assumption recorded. If the direction depends on something unproven, record it here.
Risks
No risk recorded. Risks are potential negative outcomes, kept separate from assumptions.
Open questions
No open question recorded. Keep unresolved questions visible rather than hiding uncertainty.
8. Next decision contract
The brief ends in a decision, not a polish step. Small, low-risk changes may proceed directly without a PRD.
9. Living artifact
A brief is a living document. Record when it meaningfully changed and, optionally, what changed and why. This is a lightweight note, not version control.
Investment Decision Audit
Descriptive findings grouped by decision area. This is not a score, and an empty group is Ready.
0
Blockers
5
Needs decision
2
Review
2
Info
Evidence
missing- needs decision
No evidence recorded
The brief does not connect the problem claim to any source.
Why it matters: Without evidence the brief is a formatted opinion, not an investment case.
Suggested fix: Add at least one evidence item and mark whether it supports or contradicts the claim.
Problem
missing- needs decision
Problem claim is missing
The brief does not state the problem the initiative responds to.
Why it matters: A brief without a problem is a feature request with better formatting.
Suggested fix: Describe what is happening today, for whom, and why it matters.
- review
Affected user or segment is unclear
Neither the user field nor the problem frame names who experiences the problem.
Why it matters: A problem without an affected segment cannot be scoped or measured.
Suggested fix: Name the segment and the affected role or context.
Outcome
missing- needs decision
Desired outcome is missing
The brief does not state what should change if the initiative works.
Why it matters: Without an outcome the initiative cannot be judged worth deeper definition.
Suggested fix: State the user or business result that should change, not what ships.
Direction
missing- needs decision
Candidate direction is missing
The brief does not record the direction worth exploring.
Why it matters: Without a direction the team cannot decide what deserves deeper definition.
Suggested fix: Record a candidate direction at a high level, not detailed requirements.
Boundaries
missing- review
Scope is missing
The brief does not describe the boundary of the initiative.
Why it matters: Unclear scope lets the initiative expand during alignment.
Suggested fix: Describe what part of the workflow or product is in scope.
- info
No non-goals recorded
No non-goal is recorded; for a small, bounded change this may be unnecessary.
Why it matters: Non-goals matter more as ambiguity and adjacency grow, not universally.
Suggested fix: Add a non-goal if the initiative could expand; otherwise this can stay informational.
- info
No constraint recorded
No technical, policy, commercial, timing or operational constraint is recorded.
Why it matters: Unknown constraints are often discovered late; recording them early shapes the direction.
Suggested fix: Record any known constraint, or note explicitly that constraints are unknown.
Uncertainty
ReadyNo issue found in this area.
Next decision
missing- needs decision
Next decision question is missing
The brief does not state the decision it is meant to unlock.
Why it matters: Without a decision question the brief is a form, not a decision contract.
Suggested fix: Write the decision in one question, e.g. whether this direction deserves deeper definition.
PRD Handoff Contract
Carries the problem, evidence, direction, assumptions, boundaries and open decisions forward. It does not manufacture requirements, and it keeps unknown as unknown.
# PRD handoff, Untitled initiative This handoff carries what is known and what is not. It does not create requirements and it does not resolve open questions. ## Problem / outcome - Problem: not recorded - Problem claim status: Not yet stated - Desired outcome: not recorded - Outcome claim status: Not yet stated - Confirmed enough for deeper definition: not yet, treat the problem/outcome as still under evaluation ## Direction - Direction: not recorded - State: Not yet selected - Rationale: not recorded - Key assumption: not recorded - Trade-off: not recorded ## Evidence basis - No supporting evidence recorded. ## Assumptions to carry (still unresolved) - No unresolved assumption recorded. ## Boundaries - Scope: not recorded - Non-goals: not recorded - Constraints: none recorded (may be unknown). ## Open decisions inside the PRD - No open question recorded. ## Do not promote into requirements - The candidate direction is not yet selected; treat it as a hypothesis, not confirmed scope.
Need detailed behavior?
Use the PRD Generator when the problem and direction are sufficiently aligned. Small changes may skip it.
Still choosing between bets?
Use Prioritization when several candidates compete for capacity. This brief justifies one candidate, not the portfolio.
Problem not yet clear?
Use the Problem Statement Generator or Insight Clustering Helper before forcing a weak problem through a brief.
Strategy unresolved?
Use the Product Strategy One Pager or the Roadmap Template when the broader choices are not yet made.
Take the artifact with you
Copy, download, import or print
Markdown is for docs. JSON preserves the claim, evidence and decision semantics (schema v2) and can be imported again.
Privacy: this brief autosaves in this browser's local storage. It is not encrypted team collaboration or a secure document vault. Avoid confidential product or customer details when that storage model is inappropriate.
Product Brief, Untitled initiative
# Product Brief, Untitled initiative ## Decision this brief supports - ## User / context - ## Problem - - Problem claim status: Not yet stated ## Evidence ### Supporting evidence - No supporting evidence recorded. ### Counter-evidence / limitations - No counter-evidence recorded. (This is not proof that none exists.) ## Why now - (type: Unknown / assumption) ## Desired outcome - - Outcome claim status: Not yet stated - Target: No target yet ## Candidate direction - (Not yet selected) - Direction claim status: Not yet stated ## Alternatives considered - No alternative recorded. ## Scope - ## Non-goals - ## Constraints - No constraint recorded (may be unknown). ## Assumptions - No assumption recorded. ## Risks - No risk recorded. ## Open questions - No open question recorded. ## Next decision - Decision question: - - Options: - - Owner: - - Evidence required: - - Revisit condition: - - State: Not decided yet · proposed step: Investigate further ## PRD handoff, if applicable # PRD handoff, Untitled initiative This handoff carries what is known and what is not. It does not create requirements and it does not resolve open questions. ## Problem / outcome - Problem: not recorded - Problem claim status: Not yet stated - Desired outcome: not recorded - Outcome claim status: Not yet stated - Confirmed enough for deeper definition: not yet, treat the problem/outcome as still under evaluation ## Direction - Direction: not recorded - State: Not yet selected - Rationale: not recorded - Key assumption: not recorded - Trade-off: not recorded ## Evidence basis - No supporting evidence recorded. ## Assumptions to carry (still unresolved) - No unresolved assumption recorded. ## Boundaries - Scope: not recorded - Non-goals: not recorded - Constraints: none recorded (may be unknown). ## Open decisions inside the PRD - No open question recorded. ## Do not promote into requirements - The candidate direction is not yet selected; treat it as a hypothesis, not confirmed scope.
Use a product brief when
The team still needs alignment before detailed specification
- • The problem or opportunity is plausible enough to discuss but still contains important uncertainty.
- • You need a shared view of user, evidence, outcome, direction, boundaries, and non-goals.
- • Material claims need to be traceable to evidence, and to the evidence that contradicts them.
- • Writing detailed requirements now would create false certainty or waste effort.
Move to a PRD when
The initiative is selected and delivery decisions need more depth
- • The problem and intended outcome are sufficiently understood to justify the investment.
- • Product behavior, detailed scope, dependencies, edge cases, requirements, and rollout need to be reviewed.
- • Engineering, design, data, legal, or operations need a more precise decision record.
- • Requirements need traceability to goals and later delivery artifacts.
What makes a brief decision-grade
Four things a polished one-pager usually hides
Most product brief templates are a set of text areas. That is fine for writing, but it makes it easy to present an assumption as a fact, a stakeholder request as customer evidence, or a candidate direction as a commitment. This template makes those distinctions explicit.
Claim provenance
Each material claim, problem, outcome, direction, is connected to the evidence that supports it and the evidence that weakens it. A single observation stays an observation; a Sales report stays proxy evidence.
Counter-evidence stays visible
A strong brief becomes stronger by showing tension, not by deleting the cohort where the problem does not occur or the data that contradicts the assumed cause.
Assumptions and risks are separate
An assumption is something believed but not sufficiently evidenced. A risk is a potential negative outcome. Mixing them hides which belief the direction depends on and what could go wrong.
A real next-decision contract
The brief ends with a decision question, options, owner, evidence required, and a revisit condition, and it distinguishes a decision blocker from a detail that belongs in the PRD.
Preserve the problem
A product brief should not be a feature request with nicer formatting
Weak brief
Build saved searches because customers requested it.
The solution is already locked. The user behavior, evidence, desired outcome, constraints, and uncertainty are missing, and the request is treated as customer evidence.
Stronger brief
Recruiters repeat similar candidate searches daily and rebuild filters each session. Investigate a saved-search workflow that reduces repeated setup while preserving visibility into the active filters.
The direction is visible, but the problem and outcome still lead. Requirements can follow only if the evidence justifies the investment.
Artifact decision model
Use the smallest artifact that helps the next decision
Strategy, prioritization, roadmap, brief, PRD, and launch plan are not stages every team must complete. Small or reversible changes may skip formal documents entirely. Use an artifact when it reduces meaningful uncertainty or coordination cost.
| Artifact | Use it when | Primary output |
|---|---|---|
| Product Strategy | You need to decide where to focus and which product choices should constrain future investment. | Target segment, problem choice, strategic insight, bets, non-goals, success signals. |
| Prioritization | Several credible candidates compete for limited capacity and you need a defensible choice. | Compared candidates with impact, evidence, effort, strategic fit and hard constraints. |
| Roadmap | You need to communicate investment direction, sequence, horizons, and uncertainty. | Themes, initiatives, outcomes, priorities, horizons, confidence, dependencies. |
| Product Brief | An opportunity needs lightweight alignment before the team invests in deeper specification. | Problem, evidence, outcome, direction, boundaries, uncertainty, next decision. |
| PRD | A selected initiative needs deeper product definition for delivery and review. | Goals, requirements, scope, dependencies, behavior, rollout, risks, success criteria. |
| Launch Plan | A built or near-built change needs rollout, readiness, communication, risk, and measurement coordination. | Rollout, owners, readiness, communications, guardrails, launch decisions, post-launch review. |
Product Brief owns one selected or plausible initiative. It does not own full strategy, portfolio prioritization, detailed requirements, delivery tasking, or launch coordination. Terminology varies by organization, there is no single universal product brief schema.
A proportional product workflow
One possible artifact journey
A larger initiative may move from strategy → prioritization → roadmap → product brief → PRD → user stories and acceptance criteria → launch plan. That sequence is a decision aid, not process law, and a small reversible change may skip it entirely.
Discovery depth
Need better evidence before the brief?
Use discovery work to understand the problem, user behavior, alternatives, and assumptions before a brief turns weak evidence into polished certainty. The brief stores selected evidence; it does not synthesize an entire research corpus.
Build the judgment
Templates structure thinking; CraftUp teaches the decisions behind them
Strengthen problem framing, prioritization, metrics, execution, and cross-functional judgment rather than relying on documents to make the decision for you.
Product brief FAQ
What is a product brief?
A product brief is a lightweight alignment artifact for one opportunity or initiative. It captures the user and context, the problem claim, the evidence behind that claim (and the evidence against it), the desired outcome, a candidate direction and alternatives, scope boundaries, constraints, assumptions, risks, open questions, and the next decision, before the team writes detailed requirements.
What is the difference between a product brief and a PRD?
A product brief helps decide whether and how an opportunity should proceed. A PRD goes deeper once the initiative is justified, adding detailed requirements, behavior, dependencies, rollout decisions, success criteria, and delivery context. Small changes may skip either artifact when the overhead would exceed the decision value.
Should a product brief include detailed requirements?
Usually no. Capture enough direction and scope to make the next decision, then move detailed functional behavior, edge cases, acceptance criteria, and rollout mechanics into the PRD or delivery artifacts if the initiative proceeds. The brief should not lock product behavior prematurely.
Does evidence in a brief prove the problem is real?
No. Evidence is not proof. A source can be partial, indirect, second-hand, contradictory, or poorly scoped. This template records the source type and status so you can tell a direct observation from a proxy report, and it keeps counter-evidence visible instead of deleting it. Evidence supports a claim; it does not validate it automatically.
Is a product brief a one-page document?
A brief is intentionally lightweight, but length is not the quality test. The right test is whether the problem, evidence, outcome, direction, boundaries, uncertainty, and next decision are explicit enough to make a bounded call. Detailed requirements and edge cases are a signal to move that content into a PRD, not to count words.
How is a product brief different from a product strategy or a roadmap?
Product Strategy owns broader where-to-play and how-to-win choices. Prioritization owns choosing between competing investment candidates. The Roadmap owns communicating selected bets and sequencing. A product brief owns lightweight alignment on one selected or plausible initiative. It can reference strategy, OKRs, or a roadmap bet without recreating them.