PRD Template

Product Requirements Document (PRD)

Date: [Date] • Owner: [Team/Name] • Status: Draft for build


1. Purpose & Vision

Why

[Product Name] is an AI-powered [product category] that [core value proposition] by [key mechanism/approach], enabling [target users] to [primary benefit].

Goals:

  • [Primary goal 1]

  • [Primary goal 2]

  • [Primary goal 3]

MVP Focus

  • [Core feature/functionality that defines MVP scope]

  • [System of record or primary data structure]

  • [What is in-scope vs out-of-scope for MVP]

Target Outcomes:

  • [Measurable outcome 1 with metric]

  • [Measurable outcome 2 with metric]

  • [Measurable outcome 3 with metric]

Mockups: (p1) [Screen 1], (p2) [Screen 2], (p3) [Screen 3], [etc.]


2. Scope (Release 1)

In-Scope

Out-of-Scope

  • [Feature explicitly not in MVP]

  • [Feature explicitly not in MVP]

  • [Feature explicitly not in MVP]


3. Key Personas

  • [Primary User Persona]: [role, primary use case, key actions]

  • [Secondary User Persona]: [role, primary use case, key actions]


4. User Journeys (High-Level)

A. [Primary User Journey Name]

  1. [Step 1: Entry point]

  2. [Step 2: Core action]

  3. [Step 3: Key interaction]

  4. [Step 4: Outcome/Value]


5. Functional Requirements

5.1 [Feature Area 1]

  • [Requirement 1]

  • [Requirement 2]

  • [Requirement 3]

Acceptance: [Clear acceptance criteria]


5.2 [Feature Area 2]

  • [Requirement 1]

  • [Requirement 2]

  • [Requirement 3]

Acceptance: [Clear acceptance criteria]


5.3 [Feature Area 3]

  • [Requirement 1]

  • [Requirement 2]

  • [Requirement 3]

Acceptance: [Clear acceptance criteria]


6. Non-Functional Requirements

  • Performance: [Key performance metrics, e.g., TTI ≤ 2s, response time ≤ X ms]

  • Reliability: [Uptime target, e.g., 99.5% uptime]

  • Security: [Security requirements, e.g., SSO, encryption, access control]

  • Accessibility: [Accessibility standards, e.g., WCAG 2.1 AA]

  • Privacy: [Privacy requirements, e.g., data handling, GDPR compliance]


7. Information Architecture & Data Model

System of Record: [Primary system/data structure]

Entities:

  • [EntityName]: [key fields], [relationships]

  • [EntityName]: [key fields], [relationships]

  • [EntityName]: [key fields], [relationships]

Relationships:

  • [Entity] 1--N [Related Entity]

  • [Entity] 1--1 [Related Entity]

  • [Entity] N--N [Related Entity]


8. UX References

  • [Screen/Flow reference] (p1)

  • [Screen/Flow reference] (p2)

  • [Screen/Flow reference] (p3)


9. Acceptance Criteria (Per Epic)

Epic 1 Name: [Acceptance criteria] Epic 2 Name: [Acceptance criteria] Epic 3 Name: [Acceptance criteria]


10. Analytics & Success Metrics

  • Core KPIs:

    • [KPI 1 with target metric]

    • [KPI 2 with target metric]

    • [KPI 3 with target metric]

  • Release Goals:

    • [Goal 1 with measurement]

    • [Goal 2 with measurement]

    • [Goal 3 with measurement]


11. Content & States

Empty States:

  • [Context] → "[Message/CTA]"

  • [Context] → "[Message/CTA]"

Error States:

  • [Error scenario] → "[Error message/action]"

  • [Error scenario] → "[Error message/action]"


12. Accessibility & Design System

  • [Accessibility requirement 1]

  • [Accessibility requirement 2]

  • [Design system guidance]


13. Security, Privacy, Compliance

  • [Security requirement 1]

  • [Privacy requirement 1]

  • [Compliance requirement 1]


20. Glossary

  • [Term]: [Definition]

  • [Term]: [Definition]

  • [Term]: [Definition]


Instructions: Fill out each section with your specific product details. Use this as a starting point and customize as needed for your MVP.

Last updated