Every PM/Aspiring PM knows the value of PRD!
But how do we make one that facilitates product vision & fuels easy collaboration b/w teams? 👀
Watch (VP Products ) delve deep into product specs and documenting a great PRD🙌
Join here bit.ly/khilaninsurjo
Conversation
Replying to
Some of the points would be speaking about in today's session. Super elated for this one and pretty sure this would be very useful y'all.
Join here: bit.ly/khilaninsurjo
1
3
On company's roadmap:
- The first step is to arrive at your company's roadmap by prioritizing what's important for your company's goals
- Once you know your roadmap then you focus on problem identification, prioritization, solution, delivery and product launch.
1
3
On what docs do PM write as a starting point
All the docs that PM script or write basically serve a similar purpose:
- PRDs
- Concept Note
- Prod Spec
- 6-pager
- Prod FAQ
1
3
On what docs do PM write as a starting point:
All of these docs tell you broadly:
- What problem are you solving
- What is the answer to the problem
- What would it take to get to the answer
1
1
4
👉 PRDs is the voice of the PMs and not the voice of the customer
👉 User story will help you understand the detailed requirements
👉 PRDs eventually builds a clear view of the solution and bridges the gap b/w expectation and reality
1
3
On problem identification:
▶️ Quantifying the problem and understanding the data around it is one of the signs of a great PM
▶️ Identify the customer segment for which you are solving the problem
▶️ Always narrow down or drill down to a specific user persona
6
I've been writing PRD's as a good PM all these years, now I know how to transition ahead from good. Wonderful session and absolutely bang on! 🙌🚀
4