Cyrus Stoller home about consulting

Guide to writing a PRD

Author: Cyrus
Status: Complete

Motivation for writing a PRD

As teams grow, it’s no longer efficient for everyone involved in a project to meet and share updates as they happen in real-time. And as organizational structure forms, teams need help to stay on task, to avoid the temptations of scope creep, and to curb conflict arising from uncertainty about who is in charge.

The main purpose of a PRD is to explain why a particular project is important and to define what needs to be built (not how). By explaining the motivation behind a project, team members can better reason about how to make decisions when they are presented with new information. More than anything a PRD should be a document that can be referred to whenever there’s disagreement on the best way to move forward.

Requirements for an upcoming PRD

Defining success for a PRD

Assumptions

Current plan for execution

Dependencies

Acronym Definition

PRD = Product Requirements Document


I realize this is a little meta, but I thought it’d be interesting to write a PRD for writing a PRD.

Category Meta