Free product template
PRD for a new feature
Problem with numbers, users, goals and non-goals, measurable metrics with a guardrail, user stories with acceptance criteria, scope, risks and launch.
It opens with this template loaded and runs in your browser. You don't need an account to use it; a free account saves your work and exports it.
The job it does
Before a team starts building: one document everyone reads, that says what done means and how you will know it worked. It comes with its own checks, so after you change it you can see at a glance that it still does the job.
What's inside
This is the template exactly as the Product & BA Lab opens it, read-only. Open it to run it, change it and export it.
- 1 document
- Exports as Markdown and CSV
A product requirements document the team can build from: the problem with numbers, who it is for, measurable goals with a guardrail, user stories with acceptance criteria, and how it launches. Replace the reorder example with your feature, keep the structure.
- The PRD has every section written
- The PRD has at least 3 measurable success metrics (every metric has a number in its target)
- Every user story has at least 2 acceptance criteria
- A measurable guardrail metric is about “cancel” or “refund” or “error” or “complaint” or “late”
Problem
Partner shop owners restock every week, mostly the same items. Today they rebuild the basket item by item: a median of six minutes on a phone, and 1 in 12 baskets misses an item they meant to order.
Users
The 1,800 partner corner shops that order stock through the Partner app, mostly owners ordering between customers on a phone. Not store staff or app customers.
Goals
Restocking takes about a minute, partners order what they meant to order, and more of them order every week.
Non-goals
No automatic ordering, no price negotiation and no change to delivery slots in this release.
Success metrics
| Metric | Kind | Baseline | Target | By |
|---|---|---|---|---|
| Share of partner orders placed with Reorder | success | 0% | 40% | end of Q3 |
| Median time to place a restock order | success | 6 min | 1 min | end of Q3 |
| Reorders cancelled within 10 minutes | guardrail | 2% | ≤ 3% | every week |
Requirements
1. As partner shop owner, I want to reorder a past order in one tap, so that restocking takes a minute (must)
Acceptance criteria:
- Given a past order, when I tap Reorder, then the cart holds the same items and quantities
- Given an item was removed from the range, when I reorder, then it is left out and I am told which
2. As partner shop owner, I want to change quantities before I pay, so that I order what I need this week (must)
Acceptance criteria:
- Given a reordered cart, when I change a quantity, then the total updates at once
- Given a quantity of zero, when I confirm, then the item is removed
3. As partner shop owner, I want to see which items are out of stock before I pay, so that I can swap them (should)
Acceptance criteria:
- Given an out-of-stock item, when the cart opens, then it is marked with a reason
- Given a marked item, when I tap Swap, then I see in-stock alternatives
Scope
In: Reorder on the order history, quantity changes before paying, out-of-stock warnings. Later: a weekly reminder and saved baskets.
Risks
Partners may reorder by mistake: we watch cancellations within ten minutes. Stock may be short for popular items: we flag them before checkout.
Open questions
Should Reorder copy promotions from the old order? Owner: the pricing team, answer by the end of the month.
Launch plan
Pilot with 100 partner shops for two weeks, then everyone. We watch reorder share, time to order and cancellations daily, and roll back if cancellations pass 3%.
Completeness check: every part is written.
The lesson behind it
Learn why it works, with a podcast and a quiz for each lesson.
More product templates
Sprint plan
People, days off and focus factor, a sprint goal, the stories that carry it, a burndown preview and a board.
Process map: as-is and to-be
A swimlane map with lanes per team, decisions with labelled outcomes and a validator; the today and the proposed process side by side.
Backlog prioritisation (RICE and MoSCoW)
Reach, impact, confidence and effort for every item, a MoSCoW board, and why for every number.