what frameowrks to use for PRD
- User
what frameowrks to use for PRD
Assistant
For Product Requirements Documents (PRDs), here are the most effective frameworks and approaches:
Core PRD Frameworks
1. Traditional PRD Structure The classic approach includes: problem statement, objectives, user stories, functional requirements, non-functional requirements, success metrics, timeline, and dependencies. This works well for waterfall or hybrid development approaches.
2. Jobs-to-be-Done (JTBD) Focuses on what users are trying to accomplish rather than features. Structure your PRD around the core jobs users need to complete, the circumstances that trigger these jobs, and the desired outcomes.
3. Amazon's Working Backwards Start with a press release and FAQ for the finished product, then work backwards to define requirements. This ensures you're building something customers actually want.
4. One-Page PRD Popularized by companies like Airbnb and Uber. Forces extreme clarity by limiting to: problem, solution, success metrics, risks, and timeline on a single page.
Supporting Methodologies
User Story Mapping helps visualize the user journey and prioritize features based on user activities and tasks.
RICE Scoring (Reach, Impact, Confidence, Effort) provides a quantitative framework for prioritizing features within your PRD.
Opportunity Solution Tree connects desired outcomes to opportunities to solutions, ensuring alignment between business goals and product features.
Modern Approaches
Lean PRD focuses on hypotheses, experiments, and learning metrics rather than detailed specifications. Better suited for early-stage products or features.
Outcome-Based PRDs define success metrics and desired outcomes rather than prescriptive solutions, giving teams more autonomy in implementation.
The best framework depends on your organization's culture, development methodology, and product stage. Many teams combine elements from multiple frameworks to create their own approach.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.