<aside> 💡 A Product Requirements Document (PRD) outlines the product that you intend to create. It provides a roadmap for your product's journey from raw concept to the final product, and it's an essential communication tool for the team. The PRD typically includes information about the target audience, user needs, features, functionalities, and timelines. It serves as a strategic document that aligns the team around the why, what, and how of the product before development begins.
</aside>
| Product Manager | |
|---|---|
| Product Designer | |
| Team Lead/Engineers | |
| Status |
| Stakeholder Name | Status |
|---|---|
| CEO | Signed off |
<aside> 💡 A use case is a description of a specific situation in which a product or service could potentially be used by an end user. Use the user story format: As a [user], I want to [action], so that I can [reason]
</aside>
<aside> 🖼️ Determine how you measure success
</aside>
| Measure | Current | Expected | Result | Notes: |
|---|---|---|---|---|
<aside> 💡 What elements do we want to track? Do any performance dashboards need to be created?
</aside>
<aside> 🖍️ Link UX files here: UX Flows, UI, etc
</aside>
<aside> ⭐ What are you going to build and what do you not want to build? The second part is as important as the first part because the scope is determined.
</aside>
<aside> 📖 What are the must-dos in order to churn out a usable Minimum Lovable Product (MLP)? You’ll see P0, P1, and P2 below. That’s just short hand for ordering priorities.
note: I use these requirements as part of my Acceptance Criteria
</aside>
P0 = Critical | P1 = Important | P2 = Nice to have
<aside> 🚫 List any items that will be out of scope for this product feature
</aside>