How to write a Product Requirement Documentation (PRD Draft) as a Product Manager?

Writing PRD is an art and it is excelled only with practise.

📄 Product Requirements Document (PRD)

🎯 Release Target

• Start Date:

• Expected End Date:

• Point of Contact:

🧑‍🤝‍🧑 Stakeholders

• Team A:

• Team B:

• Team C:

Document Status:

📝 Define the Objective (Why?)

📖 Product Story

• What are you trying to solve?

  • Identify the needs and jobs to be done for the user.

• Why are you trying to solve this?

  • Identify key problems and pain points.

• Whom are you trying to solve it for?

  • Define the User Persona.

🔍 Supporting Data (If any)

• Provide research data or facts to substantiate your problem statement.

📊 Impact (Measurable)

• Explain how this will impact users and the business if the product or its features are built.

🥅 Define Success Metrics (What you want to achieve?)

Goal and Metrics:

• Define your goal, its metrics, and any constraints to consider.

Example:

• Goal: Increase order value and frequency through discounts.

• Metric: Increase overall revenue.

• Constraint: Users can apply discount codes only once per week.

📈 Additional Success Metrics

• List additional metrics related to the problem you aim to solve.

💡 List Assumptions or Key Information

• Note any assumptions about your users, technical constraints, or business goals.

Example: Most users will access this feature from a specific geography.

📅 Milestones and Timelines (When are you going to achieve?)

• Task Started On: Record the actual start date, including brainstorming and drafting ideas.

• All Stakeholder Approvals Stage 1: Obtain approvals from all relevant stakeholders before proceeding.

• Wireframes & Design Stage 2: As a PM, you might create wireframes and pass them to the design team, who will then provide the final design (e.g., in Figma) to the developers.

• Development Stage 3: List features and their respective timelines.

  • Feature 1: X Date

  • Feature 2: Y Date

  • Feature 3: Z Date

• QA and Testing Stage 4: Include QA time alongside development to account for edge cases and potential delays.

• Release (Alpha, Beta, Gamma) Stage 5: Plan the release phases based on your MVP and story mapping, detailing the target release dates for each phase.

🛠 Solution (How are you going to achieve it?)

📄 Solution Brief

• Provide a brief overview of the solution.

• List all the features as per the scope of work and problem stated at the first. These features will be a part of a User Story and User Story will be a part of an Epic.

  • Feature 1 - User Story A - Epic A

  • Feature 2 - User Story A - Epic A

  • Feature 3 - User Story A - Epic A

🔀 Alternative Solutions Considered

• Discuss other alternatives considered and their prioritization metrics.

🛤 Product Flow (Details of the Feature/Product)

• Customer Journey: Start to End of a Product

• Wireframes and Flow Diagrams of the Product Features

• User Stories of Features

• User Acceptance Criteria of every feature or user story

• Edge Cases for every feature and their negative implications, if any.

---

📊 Event Tracking Sheet

• Track all the events at every stage - ensure that tracking is available for every page and click events to track better.

⚙ Dependencies

• Mention any team dependencies or feature dependencies before getting started with the development.

❓ Open Questions

• Add any pending questions to which you do not have answers.

🏗 Infrastructure Requirements

• Any major infrastructural prerequisites.

💸 Budget Approvals

• Get confirmations on the financial aspects of the product - like cost to make, resources required, etc.

🤝 Partner Support

• APIs, partnerships, etc.: Do we need any third-party integrations here?

🔗 Internal Dependencies

• Tech, design, and other teams:

📂 Related Documents

• Include any relevant documentation related to tech, marketing, support, or other areas.