Simple Product Requirements Document

This PRD is our playbook. It's here to make sure we're all shooting for the same goal.

mock-logo

Overview

Briefly explain why we're doing this. How does this fit into our big picture?

The Problem We're Tackling

  • What's the Issue?: Define the problem in a sentence or two.
  • Validation: Any customer feedback or data that supports this?

Who's This For?

  • Target Audience: Who are we building this for?
  • Why It Matters: Why do they need it?

Objectives

  • What's the Win?
  • What are we hoping to achieve?

Success Metrics

  • KPI 1
  • KPI 2
  • KPI 

Features

What are the essential features? Any additional features if time allows?

Feature 2

 

User Story: As a [user type], I want [an action] so that [benefit/value].

 

Feature Details: What are the essential features? What is out of scope?

 

Acceptance Criteria: Define what must be true for the feature to be considered complete.

Feature 1

 

User Story: As a [user type], I want [an action] so that [benefit/value].

 

Feature Details: What are the essential features? What is out of scope?

 

Acceptance Criteria: Define what must be true for the feature to be considered complete.

Feature 3

 

User Story: As a [user type], I want [an action] so that [benefit/value].

 

Feature Details: What are the essential features? What is out of scope?

 

Acceptance Criteria: Define what must be true for the feature to be considered complete.

Risks and Roadblocks

  • What Could Stall Us?: Any potential issues?
  • Plan B: Quick contingency plan.

Timeline Key Dates

List major milestones.

Communication

  • Team Updates: How will we keep the team in the loop?
  • Customer Updates: How will we tell our users?

Open Questions

  • What's Unclear?: Any unresolved issues or questions.

Details

What are the things we need to do (and be careful about) to get it done.

Exit