PRD: [Feature name]
Owner | Status | ||
Reviewers | Target release | ||
Last updated | Links |
Problem:
Solution:
Success:
Problem
Who has it, when, and what it costs them. No solution yet.
Evidence
Users
User | What they are trying to do | Where it fails today |
Goals and non-goals
Goals
Outcomes you can measure, not features.
Non-goals
What people may expect that this release leaves out, and why.
Success metrics
Add one guardrail: a number that must not get worse.
Metric | Today | Target | How we measure it |
User stories
As a [user], I want to [action] so that [benefit].
Requirements
Must: the release can't ship without it. Should: important, with a workaround if it slips. Could: only if time allows.
ID | Requirement | Priority | Notes |
R1 | |||
R2 | |||
R3 |
See an example
Vague: Exports should be fast.
Testable: R3. Exporting a 50-page document to PDF finishes in under 5 seconds on the oldest laptop we support.
Vague: Sharing should be easy.
Testable: R4. From the Share menu, a signed-in user can copy a view-only link to any document they own in two clicks.
User story: As a team admin, I want to invite people by pasting a list of emails so that I can set up a new team in one go. (R1, R2)
Design and edge cases
Designs:
Empty state:
Errors:
Permissions:
Accessibility:
Risks and dependencies
Risk or dependency | Impact | Mitigation | Owner |
Launch plan
Milestone | Date | Owner |
Requirements approved | ||
Design review | ||
Build complete | ||
Beta | ||
General availability |
Rollout and rollback:
Teams to brief before launch:
Open questions
Each with an owner and the date it's needed by.