> ## Documentation Index > Fetch the complete documentation index at: https://docs.figr.design/llms.txt > Use this file to discover all available pages before exploring further. # Draft PRDs > Generate comprehensive product requirement documents from user insights and competitive analysis. # Draft PRDs Transform research insights into structured product requirements. Figr helps you create comprehensive PRDs that bridge user needs, business goals, and technical constraints. **From insights to action:** Convert scattered research findings into clear, actionable product requirements that guide development and design decisions. ## PRD Generation Process **Consolidate research findings:** Dashboard showing user research, competitive analysis, and business goals being consolidated **Input sources:** ```yaml theme={null} User Research: - Interview findings and pain points - Usability testing results - Survey data and feedback - Analytics and behavior data Market Analysis: - Competitive feature gaps - Industry trends and patterns - Market opportunity assessment - User expectation benchmarks Business Context: - Strategic objectives - Revenue targets - Resource constraints - Timeline requirements ``` **Generate specific requirements:** ```yaml theme={null} Feature specifications: - Core functionality definition - User interaction patterns - Data processing needs - Integration requirements - Performance criteria ``` ```yaml theme={null} UX specifications: - User journey definitions - Accessibility requirements - Mobile responsiveness needs - Error handling approaches - Success state definitions ``` ```yaml theme={null} Implementation specs: - Platform compatibility - Performance benchmarks - Security requirements - Scalability considerations - Integration constraints ``` **Create organized PRD framework:** ```yaml theme={null} High-level overview: - Problem statement - Solution approach - Success metrics - Resource requirements - Timeline overview ``` ```yaml theme={null} Detailed specifications: - As a [user type], I want [capability] so that [benefit] - Given [context], when [action], then [expected result] - Success criteria and edge cases - Priority levels and dependencies ``` ```yaml theme={null} Implementation details: - API requirements - Database schema changes - Third-party integrations - Performance requirements - Security considerations ``` ## PRD Templates & Frameworks **Comprehensive feature documentation:** ```markdown theme={null} # Feature Name: [Descriptive Title] ## Problem Statement - User pain point description - Business impact assessment - Current solution limitations ## Solution Overview - Proposed feature description - Key benefits and outcomes - Success metrics definition ## User Stories ### Primary User Journey - Core workflow description - Step-by-step user actions - Expected outcomes ### Edge Cases - Alternative scenarios - Error handling - Edge case management ## Technical Requirements - Platform specifications - Performance criteria - Integration needs - Security requirements ## Design Requirements - UI/UX specifications - Accessibility standards - Responsive design needs - Brand compliance ## Success Metrics - KPI definitions - Measurement methods - Target benchmarks - Timeline for assessment ``` **Large initiative documentation:** ```markdown theme={null} # Epic: [Initiative Name] ## Strategic Context - Business objectives alignment - Market opportunity size - Competitive positioning - Resource allocation rationale ## Feature Breakdown ### Phase 1: Foundation - Core functionality requirements - MVP feature set - Technical infrastructure ### Phase 2: Enhancement - Advanced features - User experience improvements - Integration expansions ### Phase 3: Optimization - Performance improvements - Advanced analytics - Ecosystem integration ## Cross-Functional Requirements - Marketing requirements - Sales enablement needs - Customer support preparation - Legal and compliance review ``` **Evidence-based requirement generation:** ```markdown theme={null} # Research Insights → Requirements ## User Research Findings Finding: "Users abandon checkout at shipping cost reveal" Requirement: Display shipping estimates on product pages Priority: High (affects 40% of conversions) ## Competitive Analysis Insights Finding: "Competitors lack bulk editing capabilities" Requirement: Implement batch operations for admin users Priority: Medium (differentiation opportunity) ## Analytics Insights Finding: "Mobile users prefer single-column layouts" Requirement: Redesign mobile interface with vertical flow Priority: High (68% mobile traffic) ``` ## AI-Assisted PRD Creation **AI extracts requirements from research:** * Analyze user interview transcripts * Identify patterns in feedback data * Generate user stories from pain points * Suggest acceptance criteria * Prioritize based on user impact **Intelligent document organization:** * Auto-categorize requirements by type * Generate logical section structure * Create cross-references and dependencies * Suggest missing requirement areas * Maintain consistency across sections ## Collaborative PRD Development **Gather requirements from all perspectives:** ```yaml theme={null} PM contributions: - Business case and market opportunity - User journey mapping - Feature prioritization - Success metrics definition - Competitive positioning ``` ```yaml theme={null} Engineering input: - Technical feasibility assessment - Implementation complexity estimates - Performance requirement validation - Security and compliance needs - Integration constraint identification ``` ```yaml theme={null} Design requirements: - User experience specifications - Accessibility requirements - Visual design constraints - Interaction pattern definitions - Mobile responsiveness needs ``` ```yaml theme={null} Business input: - Strategic alignment verification - Resource allocation approval - Timeline constraint setting - Success criteria validation - Risk assessment and mitigation ``` **Collaborative improvement process:** ```yaml theme={null} Review cycles: 1. Initial draft creation from research 2. Stakeholder review and feedback 3. Technical feasibility validation 4. Business alignment confirmation 5. Final approval and sign-off Feedback integration: - Comment-based suggestion system - Version control for changes - Decision rationale documentation - Conflict resolution processes ``` **Keep PRDs current and actionable:** ```yaml theme={null} Maintenance practices: - Regular review and updates - Progress tracking integration - Scope change documentation - Lessons learned capture - Post-launch evaluation ``` ## PRD Quality Assurance **Ensure comprehensive coverage:** ```yaml theme={null} Essential elements: ✅ Clear problem statement ✅ Specific solution description ✅ User story completeness ✅ Acceptance criteria definition ✅ Success metrics specification ✅ Technical requirement clarity ✅ Timeline and milestone definition ``` ```yaml theme={null} Validation checklist: ✅ Business objective alignment ✅ User need validation ✅ Technical feasibility confirmation ✅ Resource requirement realism ✅ Timeline achievability ✅ Success metric measurability ``` **Ensure implementation readiness:** ```yaml theme={null} Quality criteria: Clarity: - Unambiguous requirement statements - Clear success criteria - Specific user story formatting - Detailed acceptance criteria Actionability: - Implementation-ready specifications - Clear priority levels - Dependency identification - Resource requirement clarity Testability: - Measurable success criteria - Clear validation methods - Specific performance benchmarks - User acceptance test scenarios ``` ## Integration with Development Process **PRDs that support agile development:** * Epic and story breakdown * Sprint planning readiness * Acceptance criteria clarity * Definition of done alignment * Continuous refinement support **Seamless PRD to design transition:** * Design requirement extraction * User journey documentation * Constraint specification * Success metric definition * Validation criteria establishment ## PRD Best Practices **Keep user needs central:** ``` ✅ Start with user problems, not solutions ✅ Include real user quotes and feedback ✅ Validate assumptions with research ✅ Consider diverse user scenarios ✅ Plan for accessibility from the start ``` **Ground requirements in data:** ``` ✅ Reference specific research findings ✅ Include quantitative supporting data ✅ Cite competitive analysis insights ✅ Document assumption validation plans ✅ Plan success measurement methods ``` **Ensure feasible requirements:** ``` ✅ Validate technical feasibility early ✅ Consider resource constraints ✅ Plan for realistic timelines ✅ Account for dependencies ✅ Include risk mitigation strategies ``` *** Move from requirements to design exploration and concept development. [Pre-Design Exploration →](/designing/ideation/pre-design-exploration)