How does a PM handle documentation (PRD, RFC)?

The PM maintains documentation such as PRD (Product Requirements Document) and RFC (Request for Comments) to ensure clarity and consistency of requirements and decisions in the project.

• PRD describes the product goals, target audience, functional and non-functional requirements, success criteria. The document should be understandable to all team members — from developers to marketers.
• RFC is used for discussing and agreeing on technical solutions or changes. The RFC details the problem, proposed solutions, their advantages and disadvantages.

Documentation is maintained in formats convenient for the team — this could be Confluence, Google Docs, Notion, or specialized systems. It is important to regularly update the documents, make them accessible and structured so that any team member can quickly find the necessary information.

Example of a PRD structure:

# Product Name

## Goals and Objectives

## Target Audience

## Functional Requirements

## Non-Functional Requirements

## Success Criteria

## Constraints and Risks

Thus, the PM ensures transparency and communication through proper documentation.