A PRD is an explanation of the specific product we're building. It should explain why (both internal goals and for customers) and the exact scope (features and functionality) in the product. It should also say what you're not building.

Use it to get stakeholders on the same page, then it can be used to help the team understand the project. It's a continuously iterated, living document that's updated periodically.

Outline for PRD

1. Title
2. Change History
3. 1. Each important changes by who, why and when
3. Overview
4. 1. What is the project about
   2. Why are you doing
4. Objectives
5. 1. What it will let customers do
   2. What are the company goals
5. Success Metrics
6. 1. What metrics indicate goal achievement
6. Messaging
7. 1. What is the product messaging marketing to describe this product to customers
7. Timeline
8. 1. What is the overall schedule that everyone is working towards
8. Personas
9. 1. Who are the target personas - customer user personas defined
   2. Which is the key persona
9. User Scenarios
10. 1. Full stories about how various personas will use the product in context
10. Requirements
11. 1. Distinct, prioritized features with explanations as to why each is important
11. Features Out
12. 1. What are you not doing and why
12. Designs
13. 1. Early sketches
    2. Actual designs
13. Open Issues
14. 1. What factors need to be resolved
14. Q&A

Roadmapping

is a fundamental product management activity. While product managers are known for being adaptable, mapping your path provides an avenue for stakeholder negotiation and data-led planning to support effective decision-making.