Product Requirement Document (PRD)
The Product Requirements Document (PRD) defines the product’s core goal, target users, user roles, and devices. It organizes the foundational requirements that serve as the starting point of planning, forming the basis for the subsequent Functional Specification (FS) and Information Architecture (IA).
1. Required Details
On the Product Requirements page, you can fill in the following details:
Overview: The name or topic of the project.
Goal: The problem you aim to solve or the value you want to create.
Target User: Your primary users and their context.
User Roles: The types of users defined within the project (e.g., planner, manager, viewer, etc.).
Devices: The environment where the service will be used (e.g., web, mobile app, etc.).
After setting “User Roles,” they will be linked directly to corresponding features in the Functional Specification (FS).
2. Review & Edit
When the AI suggests content, it appears as a preview. Review the draft — if it looks accurate, click Approve; if revisions are needed, click Reject.
You can also click the Edit button at the bottom of the PRD tab to make manual changes at any time.
Last updated