## Definition of Product Docs Product Docs in product management are essential documents that serve as a [[Product Roadmap]] for the development, launch, and maintenance of a product. These documents provide important information about the product's features, functionality, target audience, and competitive landscape. ## Types of Product Docs Here are some of the most common Product Docs used in product management: ### Product Requirements Document (PRD) This document outlines the product's features and functionality, and serves as a blueprint for the development team. It defines what the product should do and how it should work. For example, a PRD for a new mobile app might include a list of features, user flows, and wireframes. ### Product Roadmap [[Product Development/Product Roadmap/Product Roadmap]] provides an overview of the product's development timeline, including milestones, key features, and launch dates. It helps stakeholders understand the product's progress and what to expect in the future. For example, a product roadmap for a new software product might include a timeline for development, beta testing, and launch. ### User stories [[User Stories]] are a way of capturing and communicating the requirements of a product from the perspective of a user. They are short, simple descriptions of a feature or functionality, typically written from the perspective of a user who wants to achieve a specific goal or complete a specific task. User stories are commonly used in Agile software development, but can be used in any product development methodology. ### Market Requirements Document (MRD) An MRD outlines the market needs and trends that the product is designed to address. It includes market research, competitive analysis, and customer feedback. For example, an MRD for a new fitness tracker might include information about the target audience, market trends, and key competitors. ### Product Brief A product brief summarizes the product's key features, benefits, and [[Target Audience]]. It's often used as a marketing tool to help sales teams and other stakeholders understand the product's value proposition. For example, a product brief for a new consumer electronics product might include a description of the product's key features, such as battery life, screen size, and storage capacity. In summary, Product Docs are essential tools for product managers to communicate the vision, goals, and requirements of a product to stakeholders. They help ensure that everyone involved in the product development process is on the same page and working towards the same goals. ## Additional Content [[Carl Vellotti]]: Every PM knows the classic documents: 1-pagers, PRDs, user story maps. Here are 6 of my favorites + when and how to do them. ![[Pasted image 20230325095404.png]]