/
Product Requirements Document

Product Requirements Document

Owned by William Skaggs
Last updated: Apr 27, 2023 by Abhinandan Rudramuni
2 min read

Tip: This template is intended to help teams plan, design and develop products with the greatest chance for success. It helps teams think through their work more deeply, improves asynchronous communication with other teams, and creates space for collaboration.

Table of Contents

Problem

Questions to answer:

  • What problem are we solving? (Pain points)

    • The data related to course selection is split across many different sources

  • For whom? (Customers)

  • When do they experience this issue?

  • What data, research, and feedback do we have that explains this problem? (User Surveys, Customer Interviews)

  • Which customers are we working with, or hearing from, to better understand this problem? (User Testing, Focus Groups)

  • Why is solving this problem urgent? Why is it important?

Proposal

Questions to answer:

  • How are we solving this issue?

  • What alternatives did we consider?

  • Why did we land with this?

  • What is the general shape of this solution?

  • Do you have any mocks, prototypes, or relevant comparisons in the market?

  • How will we know that we’ve solved this issue?

  • What will we measure?

  • Have we considered how we’re building this to be fast, performant, scalable, and/or relatively low-cost on our services?

Plan

Questions to answer:

  • What are we building?

  • How does it work?

  • How do we know that it works?

  • What are we measuring?

  • When will it be ready?

 

❌What are not building? (Out of scope)

List the features or things that are out of scope, meaning things that do not define our product or what we offer to customers.

 

Then, answer these questions:

  • Question 1: Does everyone know what we are launching?

  • Question 2: Are we sure this is going to work?

  • Question 3: What are our launch steps?

  • It’s go time!

… and feel free to link to other more detailed documents