I’ve worked at multiple orgs:
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.
My tech team is blaming prds for delayed delivery of projects. But i am not sure if this is even a correct expectation. The design file had complete flows and written guidelines. Tech team said they wanted that level of clarity in the pr...
Can someone share any real Prd because i am writing prd for a website and it is crossing 30 pages is that okay?
I recently transitioned from an intern to a FTE in a startup. I'm working on a SaaS product as an APM.
I have been taking up a lot of work, interacting with devs, QA, designers but neither do I feel that my manager notices what all I'm ...
Last week, I got a list of 10 features to be implemented. I have no research on the features. But I have to write the PRDs for all of them. How do I communicate to my manager, the ETA to write the PRD. Since every feature could require d...