Product Requirements Document (PRD)



Explain the information that your team needs to know, such as the industry, why this need arises.



State the problem. Describe the opportunities available, as well as the value that is created for the user. Tell the key points of the researchs. Explain why this is a problem and why it's important for your business.

Objectives / Goals


What will success look like in terms of solving this problem? Explain why are you building this and what do you hope to accomplish.

Success Metrics


Determine how you measure success

Key Features & Scope

What are you going to build and what do you not want to build? The second part is as important as the first part because the scope is determined.

Feature 1




Additional details:

Feature 2

Core UX Flow (optional)


Most organizations complete the UX design of features after the PRD has been reviewed and accepted. However, there may be some general guidance required at this stage to ensure the release objectives are met. This is not the place for pixel-perfect mockups or wireframes that map out every possible scenario; instead, it can be used to describe the overall user workflow.

Risks (optional)


What problems might arise and what should we do if those problems occur?

Support Plans (optional)


What are the biggest problems users will face and how do we want to help them?