Skip to content
1️⃣ Change author and title
2️⃣ Complete the first draft and notify reviewers
Overview
📕 Key Resources
👀 Reviewers
Add/remove reviewers as needed, they will get a notification. Reviewers change their status themselves once they sign-off the PRD.
Team/Role
Reviewer
Status
Owner
Signed off
PM
Needs revisions
Architect
Not read
FE Engineer #1
Not read
BE Engineer #1
Not read
Product Designer
Not read
Product Marketing
Not read
Research
Not read
Business
Not read
There are no rows in this table
🗓 Key Milestones
Identify relevant milestones, including finishing tech specs and PRDs. Feel free to add/remove rows.
✅
Dates
Milestone
Exit criteria
Nov 8, 2021
PRD - Research & Discovery
Nov 15, 2021
Tech Spec
Nov 15, 2021
Low-fi designs / Prototype
Dec 2, 2021
Milestone 1 - alpha
Dec 13, 2021
Milestone 2 - alpha
Dec 17, 2021
Beta
Jan 19, 2022
General Availability
There are no rows in this table
Problem Alignment
📐The Problem
Describe the problem or opportunity. Why is it important to our users and our business? What insights are you operating on? And if relevant, what problems are you not intending to solve?
TODO text / video
🛤 Goals & Success
What does success look like? What metrics are you intending to move? Be specific, and share the OKR that you touch if any.
TODO
🌎 Competitive & Customer Research
Describe briefly how our competitors are solving this problem. This should also include links or excerpts from Customer interviews.
TODO
Solution Alignment
💡 High-level Approach
Describe briefly (1-2 paragraphs max) the approach you’re taking to solve this problem. This should be enough for the reader to imagine possible solution directions and get a very rough sense of the scope of this project.
TODO text / video
🖼️ Solution Definition and User Stories
Go deep in the solution and milestones and an organized list of user stories, ordered by priority.
TODO
Milestone
User Story
JIRA Issue
Milestone 1 - alpha
As a [user persona] I want to be able to do [X] so that I may understand/accomplish [Y]
There are no rows in this table
👩🎨 Key Design Flows
Show/Link some mocks/embeds of the experience. Link to any other documentation as necessary. In general, it’s helpful to organize these around certain user journeys / use cases.
TODO
Launch Readiness
🚀 Launch Checklist
Make sure you answer all of the questions below and involve necessary stakeholders.
Area
Question
Answer
Instructions if "Yes” (or unsure)
Support
1
Will new learning material be needed (or updates to existing documentation)? Help Center articles? Images/GIFs? YouTube videos? Plugin documentation?
Yes
Growth & Data
2
Have you implemented sufficient tracking in order to measure success, risks and impact on user behavior for the new feature?
No
Are we turning this feature on for everyone immediately (versus a gradual rollout)
No
Marketing
3
Are we running a Beta for this?
Yes
Do we need an onboarding experience?
Yes
Are we adding a new SKU
No
Security
1
Are we collecting any data that we did not already, or are we using any data in a manner that we did not already use it in?
No
Sales
1
Will this feature require new sales processes or training the sales team on new products/changes?
Yes
❓Open Questions & Key Decisions
Keep track of open issues / key decisions. Sometimes, certain decisions are made that might feel controversial; document these in text or video so people know that the discussions happened and there’s awareness of the tradeoffs.
Addressed
Open Question / Decision
Answer
Ping collaborators here
[Question]
[Answer]
[Key Decision]
[Answer]
There are no rows in this table
🧑🦯 Pre-Mortem
List the things that could go wrong (elephant in the room), and any questions that need to be answered from GTM, Eng, Data, Design or Legal before getting deep in the solution.
Addressed
Pre-mortem
Answer
Ping collaborators here
[Concern]
[Answer]
There are no rows in this table
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.