Foreword: Why I can’t give you the catch-all template for PRDs…

I will give you a rough guide on how I’ve approached PRDs as a Product Manager who has worked on developer tools (technical PM), consumer products, and enterprise software. However, I’ve found my templates shifting slightly depending on the industry or type of product management so ensure that you’re willing to think critically about how you approach it.

—

0 PRD Kick Off

This section is for absolutely everything you know about the feature or product. It could be random snippets from competitors, research or something else entirely. Here are some questions to help you brain dump.

• What do I already know about the product or feature?
• What don’t I know?
• What is the goal or intention behind the product or feature?
• What can I read or look at?
• Who can I talk to? Customers who have the problem, mentors who know about this space, or other relevant stakeholders.

1 User Stories / Problem / Associated Tickets

<aside> 🗑️

Insert everything you know from the user side. This could be user stories, support tickets, active requests from your users. Also anything else to back up the problem (if there is one)

</aside>

2 Solution Requirements

<aside> 🗑️

Input your solution requirements which could include wireframes a breakdown of how it works etc.

</aside>

3 Edge Cases

<aside> 🗑️

What are some potential edge cases you may need to handle

</aside>