One of the most important roles of a product manager is to maintain communication and alignment around the product decisions you are making. Each stakeholder will have varying levels of understanding and context about why you are building a feature, so it’s your job to act as a bridge between stakeholders, your product team, and the customer.
Enter the product requirements document (”PRD”). It’s an essential tool in every great PM’s toolkit. A PRD provides context about an upcoming product feature to all the stakeholders involved, including the problem, proposed solution, launch plan, and progress updates. It’s meant to be a living document, constantly being updated and referenced as progress and circumstances change. It becomes the single link you send to anyone who wants to know more about a feature.
Use this PRD template
How to create PRD
Copy this doc
Write the PRD, including the problem, solution, launch plan, and stakeholders
Share the doc with the relevant stakeholders by clicking Share at the top of the page
Delete this intro text (everything above the line below)
PRD for [product name]
Who is experiencing this problem? Be as specific as possible.
Describe the problem (or opportunity) you’re trying to solve. 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?
Goals & Success
What does success look like? What metrics are you intending to move? Explain why these metrics are important if not obvious.
List explicit areas we do not plan to address
Explain why they are not goals
These are as important and clarifying as the goals
What are the potential threats to achieving success? Are there external or legal risks to consider?
Give an overview of what you’re building. This could include an organized list of features or a discussion of you’re not building.
💡 Pro tip: Add sketches, wireframes, or whiteboards from Mural.
Show 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. Show enough of a clickthrough where people can walk away with a reasonable understanding of how the product works.
💡 Pro tip: Embed a live Figma file to visualize key flows right in your PRD
Often decisions are made that might feel controversial. Log them here to everyone informed on key decisions and tradeoffs.
What color should we make the logo?
Of the options, green is the closest to our branding.
When should we launch?
After reviewing all options, we should launch next Thursday.
Who is our target audience?
There are no rows in this table
Marketing press release
Work backwards by writing the press release before you build the feature. Here’s a good example:
Keep stakeholders informed
Click below to subscribe to updates on this feature. The PM will include you in email updates, etc.
Pulse Check - How do you feel about this feature?
Uncheck the box to hide other teammates’ sentiments. When your team is ready to discuss, check the box to show all sentiments.
Add My Sentiment
Check to show everyone's sentiment (
submitted with average sentiment of
Love the new checkout flow!
I’m confused as to why we’re not tracking metrics yet.
I’d love to see more details on the audience we’re targeting