6 Proven Practices to write & manage PRDs like a Pro — Chapter 5

In the previous blogs of this PRD series, we have already discussed how to write awesome PRDs, make them foolproof, and manage them along the timeline of the product development process. In this chapter, we will discuss how to ensure smooth coordination with all the departments while writing PRDs and getting them approved

Proven Practice №5 — Get PRD Approvers

Writing and managing PRDs in an agile work environment is a very fluid process, where the product development process and PRD writing runs parallel to each other

The PRD will constantly change and update according to the progress made in the development process. Therefore, it is extremely important that all the teams involved are kept constantly informed about the development progress and what changes are happening in the PRD

This will ensure that you avoid any conflict with the teams as you keep moving forward with product development and the teams and stakeholders will be aware of the ongoing development

Who are PRD Approvers?

PRD Approvers are stakeholders from every team that the product manager is working with for the particular product development

PRD Approvers could be a team lead or someone who is well aware of and holds responsibilities on the processes that your PRD is focussing on

This person should be able to understand the product benefits and the changes it would bring for the users and should be in a position to communicate the same to their respective teams, get feedback, and give necessary approval to the PRD

PRD Approvers are not fixed for every project that the product manager would undertake. It would differ based on the feature/product you are building, and which all teams and verticals will be involved in this

Why get PRD Approvers?

1. PRD Approvers can be your single point of contact for communication with the respective internal team. They can help you with information, feedback from their team, communicating the PRD and ongoing updates in the product development process to their team
2. PRD Approvers can help you with UAT (User Acceptance Testing) and product adoption if they are directly interacting/working with the users
3. PRD Approvers will feel as much a part of the product development process as the Product Manager, and this will empower them with a greater sense of responsibility towards the ongoing product development process
4. As a product manager, you can be rest assured that communication is in order with all the involved teams with the help of PRD Approvers

How to get them?

1. Communicate with the required teams including your product development team and business teams for assigning one person from each team who will be reviewing the PRD at every stage and will be approving it
2. You can also take help from your business POCs to understand who could be the PRD Approvers for the particular project from the business teams. PRD Approvers should be someone who is leading the function/process that your PRD is focussing on
3. Ensure that the business POCs and senior management are aligned on who the PRD Approvers are going to be for the particular project so that it doesn’t come as a surprise for them later

Things to keep in mind

1. The PRD Approvers for a particular project could be your business POCs as well. So only if the project requires someone else to be a PRD Approver, because the business POC is not handling that part of the function that your PRD is focussing on, then go for getting them
2. Always keep your business POCs in the loop, include them in the required meetings, PRD walkthroughs, development updates, etc. This will help you to avoid any miscommunication with the business teams
3. Once the first draft of your PRD is ready, share it with your business POCs and PRD Approvers. Mention the names of your PRD Approvers in the top section of your PRD and ask them to review it and approve it. Here is an image of a top section of a PRD with the names of its Approvers