# Product Requirements Document

### Why PRD?

* A PRD captures the **vision, goals, target audience, key features, and functionality** of the product.
* By defining the product's features and requirements, a PRD allows you to **estimate the effort, resources, and timeline** required for development.
* A PRD establishes the boundaries of the **product's scope** (again, a good product is a well-defined one!)
* And of course, a PRD serves as the **single source of truth** for anyone involved in product development and execution.

{% hint style="success" %}
A PRD is the "what" and "why" behind a product. Interviewers often want to assess your ability to define and communicate product requirements effectively.&#x20;

Having a solid grasp of what goes into a PRD and how to structure one can showcase your skills in understanding user needs/goals, translating them into clear requirements, and aligning all stakeholders around a shared vision - which is at the heart of product management.
{% endhint %}

### Problem Statement

#### Personal Financial Management for Young Adults

Assume you are a product manager at your favorite bank - we'll call it HOP Financial for now :)

**Context:** Young adults lack financial literacy, facing challenges with student loans, budgeting, saving, and investing. Traditional banking services often don't cater to their unique needs.

**Need:** A fintech solution that simplifies financial management for young adults, providing tailored guidance, tools for budgeting, debt management, saving, investing, and fostering financial literacy.

**Solution:** A mobile app acting as a personal financial assistant, offering customizable budgeting, student loan tracking, savings goals with automated recommendations, simplified investing options, and educational content.

**Objective:** Our primary objective is to empower young adults to effectively manage finances, achieve goals, build long-term financial health through this platform.

The product will aim to reduce financial stress among young adults and encourage a proactive approach to financial planning and investment.

### Guidelines

Make sure to check out this article which explains using a real example:

{% embed url="<https://bootcamp.uxdesign.cc/how-to-write-a-product-requirement-document-c4bd51604d5e>" %}

Done reading? Check out Reforge's Checklist + Template for making PRDs:

{% embed url="<https://www.reforge.com/blog/evolving-product-requirement-documents>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://iam.highonproduct.com/project-ideas/product-requirements-document.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
