Product requirements

The purpose of a Product Requirements Document is to have a documentation of what features should the product or service contain in order to meet your users' needs.

How does it help

Having a Product Requirements Document ensures a certain level of mutual, shared understanding inside your team. Ideally, this document will serve as a cornerstone for your product development.

What will you get

The name of this tool is pretty self-explanatory: you will get a detailed Product Requirements Document, which lists what problems should be solved, what features should be supported by your product or service.

The Product Requirements Document synthesizes the data we gain from organizing and analyzing the findings of the UX Research. This document bridges the gap in the UX design process between the data analysis and the interface and interaction design phase. Use Cases, User Stories and Scenarios are great inputs for creating a Product Requirements Document. There are different approaches in creating a Product Requirements Document, we include the followings:

  • Target audience (Who will use it)
  • Business goals
  • Features needed to meet the users' needs (in a prioritized way)
  • Content types
  • Ideas to consider for future development (optional)
  • Inspirations (optional)

In other words, it contains business, functional and user requirements. To get the most out of this tool, a Product Requirements Document should evolve over time, through many iterations.

What is the process

This is how we create a Product Requirement Document:

  • Listing out the key features
  • Creating the Product Requirements Document
  • Iterating as often as possible in order to maintain its alignment with your actual product or service