What is a PRD?
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.
PRD for [product name]
Problem
Target Audience
Who is experiencing this problem? Be as specific as possible.
Problem overview
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.
Non-goals
- List explicit areas we do not plan to address
- Explain why they are not goals
- These are as important and clarifying as the goals
Risks
What are the potential threats to achieving success? Are there external or legal risks to consider?
Solution
Key features
Give an overview of what you’re building. This could include an organized list of features or a discussion of what you’re not building.
Key flows
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.
Decision Log
Often decisions are made that might feel controversial. Log them here to everyone informed on key decisions and tradeoffs.
Key Milestones
Identify any relevant milestones that people should know about. Make sure to show when you’re expecting to publicly launch, too.
Stakeholders
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.
