Product Requirements

Document
A Visual Journey For Your Product
Product Requirements Document

Scope
MVP
Features and functionalities
User experience
KPI’s

1. Scope

This is a short overview of what your product will do. Make sure you write everything from end-user
point of view, starting with the problem you’re solving and going from general functianalities to specific
features. You could try to cover general design aspects here too, but you’d be better off leaving that for
latter.
REMEMBER: Always filter everything through your end user’s perspective.

2. MVP

An MVP (Minimum Viable Product) it’s “a version of a product with just enough features to satisfy early
customers and provide feedback for future product development”. It will includefeatures available when
launching the MVP
Don’t forget to include the reasoning behind what’s developed
first. Define potential user testing and maybe include examples of similar
products.

3. Feaures and Functionalities

Once you have an overview of your MVP, describe your product in detail. Let’s focus on this website
analyzer example. The features and functionalities section should outline each dashboard and option
your end-user can have. Don’t be shy about the details. You should include as much information as
possible for the development team to properly implement your vision. If you’re developing using an
agile methodology, you could leave some room for other features to be added along the way. And you
should always state if a feature is not mandatory. That way, if there’s a compatibility issue, developers
can just scrap the optional features.
Don’t be shy about the details.

4. User Experience

When you read User Experience, don’t just think about design. Yup, this section should cover the basics
of your product in terms of user interface, branding, design and all the other artsy stuff. But user
experience goes a bit further. You should also outline the ideal user flow when using your product. So
developers can better adapt the features and interface to fit the story you’re preparing for your end-user.
This is where visual support can help a lot. You can use a tool to design mockups, like balsamiq, you
can whip out Illustrator, or you can even paste screenshots and photos of similar products. Whatever
you do,
make sure there’s some visual support, with explanations.
It’ll save you a lot of time.

5. KPI

We live in an age when knowledge is power. Make good use of it. One way to do that is to define clear
KPIs (Key Performance Indicators) from the get-go. You don’t want to be stuck 6 months into the
development process not knowing if you’re going to achieve what you set out. So define a way to
measure performance, both for the development team, and the product after launch.

techmatch
1 Scope
Make sure you explain what the product will generally do in clear terms, but also take this opportunity to establish who you’re helpi

Vision Where you want your product to be 5 years from now

Goals What your product should achieve in the medium to long term

Actions What you do everyday to achieve your goals

Persona(s) Describe your end-user

What your vision is and how the product is in line with that

Make SMART and make sure they’re in line with the KPI’s you’ll
define later

Break down processes that will help you reach aformentioned goals

Take some time to define who you’re helping, and why they’ll want
to use your product
 2 MVP
ct) it’s “a version of a product with just enough features to satisfy early customers and provide feedback for future product development”. It will incl

Name Release name

Date Release date

Actions Actions on release

Objectives What you need to achieve before release date

Features Features included in the release

It doesn't have to be catchy, but your team and focus groups will
appreciate some creativity!

Make sure it's realistic! You don't want your team to be

disappointed if they don't reach a deadline

Detail critical actions on release date, and who takes them too

This is where you'll start breaking your MVP down in bite-sized

chunks

Doesn't have to be anything fancy. Just detail what's included in the

MVP
 3
ld include as much information as possible for the development team to properly implement your vision. If you’re developing using an agile method

Feature Feature name

Description Don't get extremely technical, just outline the basics of the feature.
Purpose Tie back into vision and goals
Problem What user problem are you solving?
Added Value How will this help users?
Out of Scope What this feature doesn't do
Bare Necessities The minimum required to accept the feature

Feature Feature name

Description Don't get extremely technical, just outline the basics of the feature.
Purpose Tie back into vision and goals
Problem What user problem are you solving?
Added Value How will this help users?
Out of Scope What this feature doesn't do
Bare Necessities The minimum required to accept the feature

Feature Feature name

Description Don't get extremely technical, just outline the basics of the feature.
Purpose Tie back into vision and goals
Problem What user problem are you solving?
Added Value How will this help users?
Out of Scope What this feature doesn't do
Bare Necessities The minimum required to accept the feature

Feature Feature name

Description Don't get extremely technical, just outline the basics of the feature.
Purpose Tie back into vision and goals
Problem What user problem are you solving?
Added Value How will this help users?
Out of Scope What this feature doesn't do
Bare Necessities The minimum required to accept the feature
 4
ideal user flow when using your product. So developers can better adapt the features and interface to fit the story you’re preparing for your end-use

Insert wireframes and mock-ups

Describe your mock-up

Describe your mock-up

 5
rformance Indicators) from the get-go. You don’t want to be stuck 6 months into the development process not knowing if you’re going to achieve wh

A KPI is a measurable value that indicates how well your product and business are reaching their goals

What is your desired outcome?

Why does this outcome matter?
How are you going to measure
progress? How can you influence the
outcome?
Who is responsible for the business outcome?
How will you know you’ve achieved your outcome?
How often will you review progress towards the outcome?

Answers to these questions could include:

To increase our user base to 10.000 users

This will provide a positive ROI for the
product By calculating the ROI for the
product
Daily meet with the development team, weekly skype with the design team
The CTO is responsible for this outcome
Revenue will increase by 10% this year
Weekly progress check-up