Steps
Problem and user sit together. Requirements and scope sit together. Metrics, UX notes, and review close it.
Problem and user
One problem, why now, who feels it, what they do today. Align on that before requirements.
- Product
Problem Statement Framework
Create clear, actionable problem statements that align teams and drive focused solutions.
problem-statementframingstrategy - Product
Amazon PR/FAQ (Working Backwards)
Create an Amazon-style PR/FAQ document using the Working Backwards framework for product innovation.
prfaqworking-backwardsamazon - Research
User Journey Mapping
Create detailed user journey maps with touchpoints, emotions, and opportunities.
user-journeymappingux - Research
Mixed-Source Research Synthesis
Combine already-coded interviews, surveys, and analytics into one report. For a single session use Session Debrief From Transcript. To cluster interview notes, use Affinity Mapping Assistant, then Research Insight Statement Writer.
researchsynthesisinsights
Requirements and scope
Stories, must vs nice, and an explicit out-of-scope list. Get engineering on constraints before you decorate.
- Product
Project Scope Definition
Define clear project scope with explicit in/out boundaries and assumptions.
scopeproject-managementrequirements - Product
User Story Writing
Write effective user stories with clear acceptance criteria, personas, and value statements.
user-storiesrequirementsagile - Product
Feature Prioritization Matrix
Prioritize product features using structured frameworks like RICE, Value vs. Effort, or Kano Model.
prioritizationroadmapproduct-management
Metrics and UX
How you will know it worked, plus the UX requirements that are not “make it nice.” Empty, error, and success states belong here.
- Product
SMART Goal Creator
Turn a vague objective into clear goals using the SMART framework: Specific (clear outcome and scope), Measurable (metrics or observable signals), Achievable (realistic given constraints), Relevant (aligned to user or business value), and Time-bound (deadline or milestones). Includes success criteria and checkpoints.
goalsOKRsplanning - Product
Acceptance Criteria Generator
Generate comprehensive, testable acceptance criteria for user stories and features.
acceptance-criteriarequirementstesting
Review
Walk the spec. Capture launch criteria that are actually gates. Then hand off; do not keep rewriting in Slack.
- Product
Stakeholder Alignment Document
Create documents to align stakeholders on decisions, trade-offs, and product direction.
stakeholderalignmentdecision-making - Product
Product Launch Checklist
Create comprehensive product launch checklists covering design, development, marketing, and operations.
launchchecklistproject-management
Frequently asked questions
Do I need this after a design sprint?
If you are building, yes. The sprint shareout is evidence. The PRD is the contract.
We are still discovering the problem. Write a PRD anyway?
No. Run a research study or a sprint. A spec written to look busy will be rewritten after the first customer conversation.
How short can it be?
Short enough that engineering can build without Slack archaeology. Problem, who, in/out, success metric. If that fits in two pages, stop.