My PRD Documentation

Akinrodolu seun
2 min readSep 2, 2021

--

Over the year's product managers are becoming one of the leading roles in the tech world. Every company either in HRTech, Edtech, Fintech requires a product manager.
On the other hand as a product manager, they are a handful of things you need to understand and do on a day to day activities which can be very handful.

One of them is Writing a Product Requirement document this is one of the few things document you need to get yourself acquainted with and able to earn.
Now, building a PRD document Your PRD should follow a top-down approach that starts with the overall vision of what you want to accomplish. It should then tie product goals and initiatives with the features required to achieve that vision. A well-defined PRD also includes details about how the end-user will interact with the functionality and what it will look like.
I have added a few links for more clarifications on the vision and initiatives.

As a product manager your own the PRD document and can use it as a reference to the product roadmap and FRD feature requirement documentation. There’s a difference between a “BRD” business requirement document, an “FRD” functional requirement document, MRD market requirement documentation, “PRD” product requirement document.

I will come up with simple clarifications in my next post, back to where we are.
What’s a PRD document? A {PRD)defines the value and purpose of a product or feature. It is written by the product manager to communicate what you are building, who it is for, and how it benefits the end-user.

It is often confused with a market requirements document (MRD), but they are different. An MRD should be created before a PRD so you can document what the customer needs and wants from your product or service before you define the requirements.

So let dive in on how to write a PRD document, There are many templates you can use to write a simple and fancy PRD document. But instead of using that, we can simply use google documents.

Google snippet
  1. Key things to note:
  • Objectives
  • Release
  • Features
  • User flow and design
  • Analytics
  • Future works

I have already highlight some few items you should work on in the google document below.
Click here to get a sample

--

--

Akinrodolu seun

Mission driven teacher, mentor and Product leader growing in Product, Data, Agile and Education.