| Date | Name | Role | Version | Comments |
|---|---|---|---|---|
| @January 23, 2023 | John Doe | Founder | 0.1 | Initial draft |
| Name | Project Role | Contact for |
|---|---|---|
| John Doe | Project lead | Clarifications on user flow, product design & strategy. |
| Isaac Hobb | Tech | Anything front end, back end or data engineering |
| Emma Crosby | Marketing & Admissions | Anything around email drips for admissions |
| Justice Hill | Onboarding & Experience | Anything around email drips for activation |
The objective section in a PRD will state your product’s purpose, detailing who your product is for and why you're building it.
Why is this needed with Business / Product / Tech rationale and impact metrics. What are the pain-points being addressed with this launch/product?
Assumptions in your PRD are the aspects of your product that you plan to validate or invalidate.
This might be an assumption about how a user will interact with the product, or a user’s beliefs about what this category of products can or can’t do.
Constraints are the potential hurdles your product team may face, such as budget limits, or even lack of talent, technical skill, or bandwidth on the team itself.
Dependencies include anything the product team or product itself needs in order to meet an objective. A dependency can include: