PRDs and tech teams

I kinda know this. See, Firstly, PRD should have that level of clarity. What I do is, paste Figma design screenshots in the PRD to show them the flow. Also arrow head the customer journey when required, in the PRD. Now ofcourse this is not essential in all projects. When I am having 2-3 different docs for one project, I paste the link to those docs in the PRD. So that it feels like a top down story to the reader. Now Secondly, developers are sometimes assholes too. They are lazy and want things to be spoonfed many a times with an attitude of "will do one thing only once no matter what. You come to us with changes, we won't do it" I think this is really annoying and stupid to say. It's very natural that for complex or big projects, one might forget some edge cases or corner cases to consider or sometimes the requirement changes after going live because of some other issues. In those cases one has to redo certain parts. But they create a lot of fuss and throw tantrums like class 5 kids for these. So ideally, try to put everything in the PRD and write it like a story. So that everyone can have great detailed clarity and understanding. With bullets, UI screenshot, flow chart, metrics, doubts, special points, database schema, API related things (if the project is about any third party integration) etc

A startup shouldn’t be depending on PRDs. If you know the true meaning of agile.

Here is the thing. There is no PRD for designs. Once project scope is clear, we must get on with the PRD slowly. Once you as a PM have 100% clarity and understanding and have made your own scratchy notes about everything, get on a call with the designer. Explain him things, features, capabilities, user journey flow etc (these mustbe there already mentioned in the PRD by then). Then give him the freedom to come up with his own designs. You review them. If all good, then go forward. In this case start editing the PRD and patch the screenshots of the designs at the right places. If not satisfied, then explain him your expectations again and reiterate. Basically full complete PRD is for developers only. Designers come at a stage where PM is also getting started on the project, so it's very essential that in the starting, PM and designers become like real husband wife and lovers. Afterwards, keep iterating the PRD and editing whenever required. Final version should be given to the tech team along with commenting access

Start getting a TRD from tech team before signing off on dev start. 😎 In my experience, mostly it ends up being a communication gap or missed edge cases. Get the devs to spend some time on documenting how they will implement. This should help in ensuring that they have understood requirement right, any obvious edge cases are caught early & discussed and lastly gives a better timeline estimates.