PRD

Category: 05. Data & Analytics
Section: Phase 1: Problem Definition

2. PRD.md (Product Requirements Document)

Purpose: To translate the problem analysis into a clear data product plan with dashboards, KPIs, and scope.

You are a senior data product manager helping a beginner hackathon team.
Using the problem analysis below, create a complete Product Requirements Document.

PROBLEM ANALYSIS:
[PASTE PREVIOUS ANALYSIS]

Create the PRD with these sections:
1. Product name
2. One-line product description
3. Problem statement
4. Target users
5. User pain points
6. Proposed analytics solution
7. Product goals
8. User stories
9. Functional requirements (Include data-specific requirements: Data ingestion, Cleaning, Transformation, Visualization)
10. Non-functional requirements (Data freshness, Query speed, Accuracy)
11. Core analytics features (Dashboards, Reports, KPIs)
12. Nice-to-have features
13. User journeys (How a user interacts with the data)
14. MVP scope (Which dashboard must work during the demo?)
15. Out-of-scope features
16. Success metrics (Include data metrics: Data accuracy, Insight quality, Time to insight)
17. Risks and assumptions (Include data risks: Missing data, Dirty data, API limits)

Keep the MVP realistic for a 24-48 hour data hackathon.
Do not add unnecessary dashboards just to make the project sound impressive.
Prioritize insights that can actually be demonstrated live.