What do you do once you’ve written the prd?
I’ve worked at multiple orgs: 1. Sometimes prd are written for the sake of it. Contains no details. Usually engineers closely work with pm and implement stuff 2. In other scenario active discussion happen on prd and then stakeholders meet and take final call 3. In some orgs prds are just less of prds and more of timeline docs. What do you guys prefer?
In my experience, a lot depends on what is getting built.
For super complex system level stuff, PRDs are more of solutioning docs. Lots of people collaborate, edge cases are captured, sign-offs from biz folks are captured.
For simple yet critical (policy level) stuff -- like pricing changes etc, PRDs are proxy for proof of opt-in/ sign off
For simpler, not so critical stuff, PRDs (or 1-pagers) are just anchors in the product roadmap
Again, this is from my experience working with large Indian startups/ unicorns
That makes lot of sense.
In the first case do you usually have discussion on the doc, ie lots comments and deliberations or do you usually get on a call with stakeholders and give them a walkthrough?
I think alot of time PRDs for my own reference. The way devs clear their execution thoughts in code, I can clear my thoughts in a well written document aka PRD.
It helps me imagine and formulate a better flow for users.
It also helps me find edge cases of a situation.
And most importantly, it's a good reference document for me.
Discover More
Curated from across
