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 prd as well. What should i do? Btw We are a startup.
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
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.
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...
Met a PM from IIT / IIM with 4 years of experience. He is working at a well know soonicorn at a salary of 17 lakhs per year . He used to draw 30 lakhs per year in his last role before we was laid off . Interesting Times ahead
A minute of silence to all the grapevine polls where salary expectations are so high 😁
Finally. This was long due. PM's are just overpaid.
Not just PM. I'm in Business roles for the past decade; People are offering me 50% less now. Fortunately not laid off...
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 ...
feeling like I am literally in the worst phase of my life. Our company is taking ownership of an abroad project and those abroad folks are not supportive or even if they support us then they give little information so that we can't take ...
