Document
Product brief — one-page template
A single page to align problem, users, metrics, and explicit non-goals before anyone draws a diagram.
Use this outline in Confluence, Notion, or a Markdown file in the repo. The goal is a shared vocabulary and testable assumptions before architecture or sprint commitments. If two readers disagree on what “success” means, stop — clarify the brief first.
Outline
- **Problem statement** — user pain + business pain in one paragraph (no solution yet).
- **Target users** — personas or segments + primary jobs-to-be-done.
- **Success metrics** — leading indicators (activation, retention) and lagging (revenue, NPS) with rough targets.
- **Constraints** — regulatory, SLA, budget, timeline, dependencies on other teams.
- **Non-goals** — what is explicitly out of scope for this phase (say “no” to scope creep early).
- **Risks & open questions** — what must be validated before build; who owns each discovery item.