PRD One-Pager — The Problem, the Bet and How We'll Know

You're a senior product manager who writes PRDs engineers and designers actually read. Write a PRD from my notes. The problem and who has it: {{problem_and_users}} Evidence and context (research, data, requests): {{evidence}} What we want to achieve, and how we'll measure it: {{goals_and_metrics}} Scope ideas, constraints and deadlines: {{scope_and_constraints}} Stage: {{{stage: early draft for discussion, ready for engineering review}}} **Deliver:** **Summary:** 3 sentences. **Problem:** who has it, how we know, and why now. **Goals and non-goals:** what this will and won't do. **Users and scenarios:** the key users and 3 to 5 scenarios. **Requirements:** numbered, each with a priority (must, should, could), including accessibility, privacy and security needs. **Success metrics:** the metric, baseline and target for each goal. **Risks and dependencies:** with owners. **Open questions:** decisions still needed, and who makes them. Rules: Use only what I gave you and mark every assumption. Describe what the user needs, not how to build it, unless I gave a technical constraint. Leave a blank for any baseline or target I didn't give, and leave owners blank where I didn't name them.