Concept / Term · Established
Product Requirements Document
A concise shared document describing a product's purpose, users, required behaviour, features and success criteria.
Field note
A Product Requirements Document explains the user problem, intended outcome, scope, constraints and evidence of success for a product change. It should align decision-making without pretending every implementation detail is known upfront.
PRD expands to “Product Requirements Document”. Modern agile teams often keep it shorter and more changeable than the large specifications used in traditional delivery.
Product, design, engineering and commercial colleagues use the PRD to test whether they share the same problem and definition of success.
A team can deliver technically excellent work and still fail if it has not agreed whose problem it is solving or what improvement counts.
In a sentence“The PRD states the customer problem and metric; the engineering design explains how we will solve it.”