write-prd

Overview

Based on Shape Up by Ryan Singer (Basecamp). A PRD defines the problem, the appetite, and the solution boundaries - not a detailed spec. The key insight from Shape Up: fix the time, flex the scope. Define how much the team is willing to spend before deciding what to build.

Workflow

Step 1: Set the Appetite

Before writing requirements, define the appetite - how much time is this worth?

• Small batch: 1-2 weeks
• Big batch: 4-6 weeks

If the solution requires more time than the appetite allows, cut the scope - don't extend the time.

Step 2: Write the Problem Statement

One paragraph. Answer: what is broken or missing today, who is affected, and what is the cost of not solving it. Avoid mentioning solutions here.