PRD (Product Requirements Document)
Acronyms and Abbreviations
The document that says what a product must do and why, before anyone builds it.
In practice
A product requirements document captures the problem, the users, the goals, the scope and the success criteria for a product or feature — the shared understanding a team builds from. Good ones are short, evidence-based and clear about what is out of scope; bad ones are feature lists nobody reads. Increasingly it is a living doc rather than a signed-off spec.
Questions
What is PRD (Product Requirements Document)?
A PRD is a document defining a product's purpose, target users, functional requirements, constraints and success metrics to align a team before development.
Why do you use PRD (Product Requirements Document)?
Because building the wrong thing well is the most expensive mistake there is, and a PRD is where the team agrees on what the right thing is.
How do you use/apply PRD (Product Requirements Document)?
State the problem and evidence, define who it is for, list requirements as outcomes not solutions, set measurable success criteria, and mark what is explicitly out.
When do you use PRD (Product Requirements Document)?
Before committing engineering time to anything substantial, and revised as discovery changes the picture.
Who uses PRD (Product Requirements Document)?
Product managers, with designers and engineers as co-authors.
