# Product brief template

Keep it short. Mark every number as measured, reported by the owner, or assumed for this learning exercise.

## User and problem
- User:
- Situation:
- Current workaround:
- Where time, quality, or requests are lost:
- Evidence and source:
- Hypotheses to verify:

## Version 1 result
- The user can:
- Main journey (5–7 steps):
- How the user knows it worked:

## Scope
- Included:
- Not included yet:
- Data collected and why:
- Data not collected/stored:

## Acceptance criteria
| Condition/action | Observable expected behavior | How to verify | Status |
|---|---|---|---|
| Happy path | | | |
| Required field is empty | | | |
| Network/server error | | | |
| Mobile screen | | | |
| Keyboard navigation | | | |

## Success and constraints
- Baseline (value / source / period):
- Target (a hypothesis until validated):
- Review date:
- Decision owner:
- Risks and open questions:

## Worked example
Consultation request service. Version 1: one service, name and contact, truthful submission confirmation. Payments and CRM are out of scope. Learning criterion: a server error never appears as a successful submission, and the entered data is preserved. No business impact numbers are claimed.