Create a lightweight PRD

Why it matters

PRDs are alignment tools. Good PRDs cut back-and-forth questions during sprints.

Steps

• Write the problem, affected users, and evidence of the problem
• Set a goal plus 1 primary and 2 supporting metrics
• Write explicit in-scope and out-of-scope
• Sketch a 5-step user flow
• List 5 edge cases and open questions for engineers

Expected output

1-2-page PRD document

Checklist

• Metrics measurable with target numbers
• Out-of-scope written
• Realistic edge cases
• Readable in 10 minutes

Evidence

PRD document link

Self review

Could an engineer estimate the work from this document alone?