What should PRDs look like?
PMs of Reddit! What should PRDs look like?
In recent times, every PRD I come across is just AI slop. While AI largely gets the structure right, what's missing is real context. I am a new PM (3yrs of experience in a startup), so I have tried to experiment a bit with the structure of PRDs since my products are largely technical in nature. But now I'm curious as to what "good" PRDs look like? At this point it seems like a mythical beast that people have only heard stories about. Can you guys give me some pointers? Does anyone have a repo where I can read some real PRDs, maybe for products that are now live?
Skillifyabhishek Three years in at a startup you probably have more instinct than you think. A good PRD answers four things clearly: what's the problem, who has it, how will we know we solved it, and what are we actually building. Everything else is supporting detail. If it's longer than two pages before the specs, it's probably too long. Mar 19 2 likes
thereasonigotbangs Mine are ulta streamlined one pagers: problem, solution, functional requirements, open questions, and appendix. Mar 19 2 likes