<aside> ℹ️ As expertly described by Aakash Gupta, "The PRD is not a static document, it's a living, breathing reflection of the team's progress”

As such, this PRD will evolve over time, with each iteration serving the current product lifecycle

</aside>

<aside> ℹ️ I will be making references to Nir Eyal’s Hooked model, and will answer some of his homework questions here, since these are EXCELLENT questions any PM / tool creator should ask themselves.

</aside>

Sections:

1. Problem Statement
2. User personas + pain points
3. Goals
4. Solution Elevator Pitch
5. High Level Product Phases + Success Criteria
6. Jobs to be Done
7. Features list
8. Metrics (for each step of funnel)
   1. acquisition funnel, with supporting behavioral metrics supporting well defined hypotheses
9. Hooked Model Homework
10. Mockups/Wireframes

Background:

Working on complex projects involving lots of people from multiple orgs and multiple timezones requires a lot of the communication and decision making to happen asynchronously.

One of the most efficient ways of doing so is to have a common document-based framework to drive the processes such as: prioritization or tradeoff decisions, PRDs of various complexity, etc.