📝 PRD Writing Guide
A Product Requirements Document (PRD) is the bridge between strategy and execution. It communicates what to build, why, for whom, and how success will be measured. A good PRD is not a 50-page specification — it is a living document clear enough that any team member can understand the product direction. Modern PRDs are concise, outcome-focused, and collaboratively authored.
PRD Structure
Problem Statement
What user problem are we solving? What evidence do we have?
Goals & Success Metrics
What does success look like? How will we measure it?
User Stories & Requirements
Who are the users? What are their workflows?
Design & Technical Considerations
Constraints, dependencies, trade-offs, open questions
Real-World Example
Amazon's internal PRD equivalent — the 6-page narrative memo — forces clarity of thought by requiring full sentences and logical argumentation instead of bullet points. Jeff Bezos banned PowerPoint presentations in meetings because they allow presenters to hide behind bullet points without demonstrating clear thinking.