A Product Requirement Document or PRD is the bible of the Product Designer when it comes to designing a specific product. It contains the mission and vision of the product. It contains key information of the people involved in creating the product. It contains the scope of the product. When you are lost, revert back to the PRD and update it with a product manager as often as necessary.

1. Intro
   • Product Name
   • Author
   • Purpose
     Technical and business perspective
2. People
   • Background (names and contact information)
     • Stakeholders
     • Teams
   • Foreground
     • Target Market (Market research, demographics)
     • Customer, Users
       • Audience
       • Tasks
       • Use Cases
       • User Journey
       • Needs
       • Information-seeking Behavior
       • Experience
     • Design Personas (User goals, pain points)
3. Content
   • Content Objectives
   • Root Definitions
   • Document and Data Types
   • Volume
   • Existing Structure
   • Governance and Ownership
4. Context
   • Business goals
   • Funding
   • Politics
   • Culture
   • Technology
   • Resources
   • Constraints
5.  Product
   • Product Overview
   • Similar Products, Competitors
   • Functional Requirements
   • Platforms, Benchmarks

References

• Product Requirements Document – Wikipedia
• Creating Personas – UX Booth
• Information Ecology – UXD
• Soft Systems Methodology

Version History

1.0.1 - 23 March 2020

Added Root Definitions in Content based on Soft Sytems Methodology