The PRD explained for designers: what it is, what it contains, and how to contribute

A PRD (product requirements document) defines what a feature must achieve and for whom. Learn its sections and what the designer should contribute.

info Quick Definition
A PRD (product requirements document) defines what a product or feature must achieve, for whom, within what scope, and under which criteria it is considered done. Its job is to align product, design, engineering, and business before anyone builds.

What is a PRD?

It is the document where the “what” and the “why” are fixed. Wikipedia describes it as a record of product requirements that says what the product must do, avoiding as far as possible how it will be implemented. That lets designers and engineers choose the solution within a shared frame.

Atlassian describes it in a similar way: a PRD defines the requirements of a product or feature, meaning its purpose, features, and functionality, and it is completed with the development team and product designers.

What sections does it have?

There is no single format, but Wikipedia, Atlassian, and Plannotator share a core:

SectionWhat it answers
Problem and purposeWhat pain it solves and why now
Goals and metricsWhat success looks like, with numbers
Non-goalsWhat is deliberately left out
Users and use casesWho uses it and in what situation
RequirementsWhat it must do, including non-functional requirements
Acceptance criteriaWhen a feature is considered ready
Assumptions and dependenciesWhat is taken for granted and what depends on others
Timelines and open questionsMilestones, dates, and what is still unknown

Plannotator proposes a very similar list and adds counter-metrics: indicators that watch whether the change harms something important. Wikipedia also includes stakeholders, market assessment, constraints, and requirements for interaction with other systems.

Atlassian’s template is shorter: basic document details (target release date, status, team), objective, success metrics, assumptions, requirement options with user stories and their importance, supporting documentation (mockups and diagrams), open questions, and what is out of scope. If your company already has a template, use it; what matters is that it answers the same questions.

What does the designer contribute?

The designer brings the part a PRD often leaves vague: the experience. Atlassian suggests writing the document together with engineering and product designers, and attaching mockups and diagrams. Your most useful contributions are:

  • Evidence of the problem. What you observed in research, with links to the findings.
  • Use cases and flows. How the feature will be used step by step, including errors.
  • Acceptance criteria written in experience terms. Not only “the user can pay”, but “the user understands the total before confirming”.
  • Open questions. What you do not know and need to validate.

Writing acceptance criteria in experience terms avoids a common problem: the feature meets its technical requirement and still confuses the user.

What should a PRD NOT be?

Plannotator warns against writing a PRD only to satisfy a process. A long document nobody reads aligns nobody. And for small, reversible changes, a short issue is usually enough.

Plannotator also separates the PRD from the technical specification and the implementation plan. The PRD should stop before technical design: it decides the problem and the outcome, not the architecture.

Wikipedia adds that the information in a PRD should be updated regularly as new information or changes arrive, and that unrealistic timelines can lead to delays or even cancellation of the project. A PRD that is never updated becomes fiction.

How do you use it well?

Some practices that help:

  1. Start with the problem, not the solution. If the PRD opens with a screen, you probably skipped a step.
  2. Write non-goals, so the scope does not grow without a decision.
  3. Link each requirement to a finding or a metric.
  4. Keep the document short and link to details instead of copying them.
  5. Version important changes and say in the document what changed and why.

If you want to know which decisions should be recorded, the design decision log complements the PRD because it keeps the reasoning behind each change.

Example

Illustrative example: a team wants to add installment payments to an online store. The PRD opens with the problem: a share of shoppers who reach checkout with a high total abandon it, according to the last quarter’s analytics (illustrative data). It sets the goal of reducing that abandonment without raising defaults, and a non-goal of not offering long-term credit in this version. The designer adds the flows for choosing a plan, the error states if a card is declined, and an acceptance criterion: the shopper must see the final total, the number of installments, and the date of the first charge before confirming. Open questions are listed with an owner.

Common mistakes

  • Writing the solution instead of the problem.
  • Skipping non-goals, which inflates the scope.
  • Acceptance criteria that are only technical, with no user experience in them.
  • Leaving the PRD unupdated after important changes.
  • Making a document so long that nobody reads it.
  • Writing a PRD for changes that do not need one.

To decide what enters the scope, the Kano model helps separate basics from differentiators, and designing an MVP explains how to cut down to the core that tests the hypothesis. If the PRD serves as the basis for validating an idea, concept testing lets you check the proposal with people before committing to development.

Sources

Frequently asked questions

What is a PRD?
It is a document that defines the purpose, scope, requirements, and expected behavior of a product or feature, so the team can align. Wikipedia describes it as a document that says what the product must do, avoiding as far as possible how it will be implemented.
What sections does a PRD usually have?
Problem and purpose, goals, success metrics, users and use cases, functional and non-functional requirements, acceptance criteria, non-goals, assumptions, dependencies, timelines, and open questions.
What should a designer contribute to a PRD?
Evidence of the user problem, flows and sketches that show how the feature will be used, and acceptance criteria that describe the experience, not only the functionality.
Does every change need a PRD?
No. Plannotator warns against writing a PRD only to satisfy a process. For small, reversible changes, a concise issue is usually enough.