Become Product Manager
12 weeks · 4 milestones
Milestone map
Milestone map
3 milestones
Write a product requirements document (PRD) or feature specification for a real feature — one that will actually be built, or has already been built based on your spec — at your job, a side project with a real team, or an open-source project where you are contributing as a product contributor. The spec must include: the problem being solved (with evidence from real users, analytics, or stakeholder input), success metrics (how you will know it worked, with measurable thresholds), out-of-scope constraints, and at least 3 user stories in the 'As a [user], I want [action] so that [outcome]' format.
Proof required
Submit the PRD or feature spec (with a git commit timestamp or document creation date predating the build), the evidence that informed the problem statement (user feedback, analytics screenshot, or stakeholder email — redacted if sensitive), and a one-paragraph description of what actually shipped vs what was in the spec (any changes and why).
What gets checked
- Problem statement is backed by evidence — a quote from a user, an analytics metric, or a documented stakeholder pain; 'I think users need this' is not evidence
- Success metrics have measurable thresholds ('increase checkout completion rate from 67% to 72% within 60 days') not vague aspirations ('improve checkout')
- The spec predates the build — a post-hoc spec is documentation, not a product requirement