PRD Template
A PRD isn't a contract—it's a communication tool. It captures the problem, the bet, and enough detail for the team to build the right thing.
What makes a good PRD?
A good PRD is clear on the problem, explicit about what's out of scope, and flexible enough for engineers to find the best solution. It answers "why" before "what".
The 7 Sections
Inspired by Shape Up's Pitch format. Every section earns its place.
Problem
A single specific story showing why the status quo doesn't work. Include: who it's for, the hypothesis, and evidence (interviews, data, requests).
Appetite
How much time this is worth and how that constrains the solution. The appetite shapes what we build—not the other way around.
Solution
Core elements at the right abstraction. Include key flows and the main customer benefit.
Risks
Rabbit holes, technical uncertainties, and dependencies worth calling out. What could derail us if we don't address it upfront?
Out of Scope
What we're explicitly NOT building to fit the appetite. Be specific—this prevents scope creep better than any process.
Rollout & Go-to-Market
How we'll release (pilot, A/B, phases) and how we'll sell it. Involve GTM teams early—they shape the product too.
Objectives & Key Results
How this fits strategic goals and the metrics that will tell us if the bet paid off.
PRD Tips
- →Write for the team that will build it, not for stakeholders to sign off.
- →Include mockups early—visuals reveal gaps that words hide.
- →The "Out of Scope" section prevents scope creep better than any process.
- →Update the PRD as you learn—it's a living document, not a contract.