PRD vs Design Doc
People think a product requirements document and a design doc are the same plan. The first says what to build and why: the problem, the users and how to tell it worked. A design doc says how to build it: the parts, the data and the options turned down. Product managers most often write the first. Engineers write the second, after they read it.
Product Requirements Document (PRD)
A written plan of what a new feature must do, and why.
A product requirements document (PRD) says what a new feature or product must do. It names the problem, who has it and why it matters now. It lists what the thing must do, and what is left out. It also says how the team will know it worked. Engineers and designers read it before they plan how to build. A good PRD is short and changes as the team learns.
Technical Design Document
A written plan for a new part of an app. The team reads it before coding.
A technical design document is a written plan for building a feature or system before the coding starts. It says what problem it solves and what is left out. It shows the design, often with diagrams, and the other options that were turned down. Teammates read it and leave comments. Many teams write one for any large change.
In one line
- Product Requirements Document (PRD)
- A written plan of what a new feature must do, and why.
- Technical Design Document
- A written plan for a new part of an app. The team reads it before coding.
These live in different corners of the glossary (Business and Development), which is exactly why they get confused.