Download this template free
No sign-up needed. Word and Excel files also open in Google Docs, Google Sheets and Apple Pages/Numbers. Letter size (8.5 × 11 in).
PRD: [Feature or Product Name]
1. Problem
[What problem are we solving, for whom, and how do we know it's a problem? Include data or user quotes.]
2. Goals and non-goals
Goals
- [Measurable outcome]
- [Measurable outcome]
Non-goals
- [Explicitly out of scope]
- [Explicitly out of scope]
3. Users and use cases
| User type | User story (As a … I want … so that …) |
|---|---|
4. Requirements
| # | Requirement | Priority (Must / Should / Could) | Acceptance criteria |
|---|---|---|---|
| R1 | |||
| R2 | |||
| R3 | |||
| R4 | |||
| R5 |
5. User experience
[Key flows, wireframes or design links, edge cases and empty, error and loading states.]
6. Success metrics
| Metric | Baseline | Target | By when |
|---|---|---|---|
7. Dependencies, risks and open questions
- [Dependency on another team or system]
- [Risk and mitigation]
- [Open question, with owner]
8. Launch plan
[Rollout approach (beta, percentage rollout, feature flag), support and documentation, announcement.]
Preview of the template. Highlighted [brackets] show text to replace.
How to write a PRD
- Start with the problem, not the solution. Back it up with data, research or customer feedback.
- Set goals and non-goals. Non-goals prevent scope creep and endless debates.
- Describe users and use cases with simple user stories.
- List requirements with priorities. MoSCoW (Must, Should, Could, Won’t) is a common method. Add acceptance criteria so everyone knows when a requirement is met.
- Link to design rather than describing every screen in words.
- Define success metrics with a baseline and target.
- Call out risks, dependencies and open questions, each with an owner.
- Plan the launch.
Example user story and acceptance criteria
User story: As a returning customer, I want to reorder a previous purchase in one click, so that I can restock quickly.
Acceptance criteria:
- A “Reorder” button appears on each past order.
- Clicking it adds all in-stock items to the cart at current prices.
- Out-of-stock items are listed with a message.
Tips
- Keep it a living document and update it as decisions are made.
- Write for skimmers, with headings, tables and bullets.
- Get sign-off from engineering and design leads before development starts.
- Use the Markdown version in GitHub, GitLab, Notion or Confluence.
Frequently asked questions
What is a product requirements document?
A PRD describes what a product or feature should do and why. It defines the problem, goals, target users, requirements and success metrics, so product, design and engineering share the same understanding before building.
How long should a PRD be?
As short as possible. Many teams use one- to three-page PRDs for features, and link to designs and tickets for detail. Large products may need longer documents.
Who writes the PRD?
Usually the product manager, with input from design, engineering, data and stakeholders. It should be reviewed and agreed before significant development begins.
Related templates and guides
README Template
A clear README.md for any software project, with the sections developers look for first, ready to download as Markdown and drop into your repository.
TemplateWebsite Brief Template
Give your web designer or agency a clear picture of what you need, including goals, audience, pages, features, content, style, budget and deadlines.
TemplateProject Plan Template
Define goals, scope, milestones, tasks and owners for any project in one clear document, from a website launch to an office move.
TemplateBug Report Template
A clear bug report format that gives developers everything they need to reproduce and fix a problem the first time.