In the discovery phase of the product development process, your attention should be on understanding the problem you aim to solve. The product brief serves as a tool for gathering input from leadership and key stakeholders that helps you decide whether or not to pursue this opportunity further. [Reforge]

➡️ Principles

• Product brief is a well-structured one-pager that covers opportunity, target audience, why now, success metrics, impact, and a rough plan.
• The goal of the Product brief is to ensure alignment across the teams and prevent any misaligned expectations around the opportunity, scope, and timeline.
• Use Product brief to gather feedback, improve your thinking, and leverage any knowledge floating in the organization on that topic.

🗓️ When to create

• Product brief should be written at the beginning of a new initiative before any external discovery is completed.
• It should reflect and capture your best understanding of the problem you are tackling and what it will take to solve it.
• The Product Manager should review existing content and context and speak to internal parties that may have knowledge about the problem before drafting this document.
• The Product Manager should collaborate with their Design and Engineering counterparts to articulate the rough estimates for discovery and delivery efforts.

📄 Library

Product Brief Library