Write a PRD / Product Spec
Create a comprehensive product requirements document from problem definition to launch criteria.
Overview
A complete guide to writing effective PRDs that align teams, reduce ambiguity, and set features up for success. Covers problem framing, requirements, user stories, success metrics, and stakeholder alignment.
Prerequisites
- Clear problem or opportunity identified
- Access to user research or customer feedback
- Engineering and design partners available for review
- Stakeholder buy-in on priority
Steps
Define the Problem
2-3 hoursArticulate the problem clearly with context, user impact, and business rationale.
Prompts to use:
Deliverables:
- •Problem statement (1-2 sentences)
- •User pain points
- •Business impact
- •Why now?
Tips:
- •Start with the user problem, not the solution
- •Quantify the impact if possible
- •Explain why this is the right time to solve it
- •Get stakeholder alignment on the problem before moving on
Document User Context
2-4 hoursCapture who the users are, their goals, and current workarounds.
Prompts to use:
Deliverables:
- •Target user segments
- •User goals and motivations
- •Current workarounds
- •Jobs-to-be-done
Tips:
- •Reference existing research if available
- •Include primary and secondary users
- •Document what users do today without this feature
- •Identify edge cases early
Define Solution Requirements
3-4 hoursSpecify what the solution must do, organized by priority.
Prompts to use:
Deliverables:
- •User stories (as a... I want... so that...)
- •Functional requirements
- •Non-functional requirements (performance, security)
- •Must-have vs nice-to-have
Tips:
- •Write requirements from the user perspective
- •Be specific enough to be testable
- •Separate MVP from future phases
- •Include acceptance criteria for each requirement
Define Scope & Constraints
1-2 hoursClarify what's in scope, out of scope, and key constraints.
Prompts to use:
Deliverables:
- •In-scope features
- •Out-of-scope (explicitly)
- •Technical constraints
- •Timeline constraints
- •Dependencies
Tips:
- •Be explicit about what you're NOT building
- •Document assumptions that could change scope
- •Identify external dependencies early
- •Get engineering input on technical constraints
Define Success Metrics
1-2 hoursSpecify how you'll measure success and what targets you're aiming for.
Prompts to use:
Deliverables:
- •Primary success metric
- •Secondary metrics
- •Targets and thresholds
- •How metrics will be tracked
Tips:
- •Pick 1-2 primary metrics, not 10
- •Include leading and lagging indicators
- •Set realistic targets with baseline data
- •Define how you'll know if it's working
Document Design & UX Requirements
2-4 hoursInclude wireframes, user flows, and design considerations.
Prompts to use:
Deliverables:
- •User flow diagrams
- •Wireframes or mockups
- •Key interaction patterns
- •Edge cases and error states
Tips:
- •Work with design early, not after PRD is done
- •Include happy path and error states
- •Reference design system components
- •Note accessibility requirements
Stakeholder Review & Alignment
1-2 daysReview PRD with engineering, design, and leadership for alignment.
Prompts to use:
Deliverables:
- •Reviewed PRD with feedback incorporated
- •Engineering feasibility confirmed
- •Design alignment confirmed
- •Leadership sign-off
Tips:
- •Share PRD early for async review
- •Have a live review meeting for questions
- •Address concerns before moving to build
- •Document decisions and trade-offs
Define Launch Criteria
1-2 hoursSpecify what must be true to launch and how you'll roll out.
Prompts to use:
Deliverables:
- •Launch criteria checklist
- •Rollout plan (beta, GA)
- •Go/no-go decision criteria
- •Rollback plan
Tips:
- •Define minimum bar for launch
- •Plan for phased rollout if risky
- •Include quality gates
- •Have a rollback plan ready