Templates / Product requirements (PRD)
Product requirements (PRD)
Half of a PRD defines what to build. The other half defines what not to build. Explicit non-goals keep the discussion from sprawling.
Write requirements as verifiable sentences. A requirement without a success metric cannot be evaluated after launch.
What is inside
Feature PRD
Problem
Who hurts, in what situation, and why.
Goals and metrics
- Define success as a number.
Requirements
- Each one verifiable.
Non-goals
- What this version will not do.
Open questions
- Questions that need a decision.