Section 1: Executive Summary

<aside> 📌 This section is intended to be filled out by the end of the planning process. Executive Summary should include: Priorities of the area + main levers to achieve them. Half of a page max (suggested).

</aside>

Section 2: Product Plan

2.1 Mission of the Q

2.2 State of the Product

<aside> 📌 Section requirements

• Need to inform the reader of the current state of the product, which sets up the background and context for the next sections.
• Data/metrics-driven and focused on the current state of the product, not focused on historical context.
• 1-3 paragraphs max (suggested). </aside>

2.3 Key Objectives and Results

<aside> 📌 Section requirements

• List right up front what the metrics for success are so we can use them as a lens to see the remaining document through.
• 3-5 objectives maximum, each with <= 3 key results.
• Historical figure (“from X”) and forecasted figure (“to Y”) for each key result. </aside>

Section 3: Product Roadmap

<aside> 📌 Section requirements

This is the meat of the document and lays out the plan, how to execute it, and should match up to achieving the goals stated at the top of the document.

• Add a summary of the epics, sizing, sprint(s) (SP) planned in and the team availability at the beggining of this section
• Write an Executive Summary for each epic describing the approach in detail and why it will hit the plan — keep it brief and to the point
• Include what OKRs you will be hitting per initiative
• This same table should be added to your Jira Epic to avoid double working </aside>

Roadmap summary

Team Availability

3.1. Epic 1 — [Name of the epic]

<aside> 📌 Section requirements

Use this section to duplicate epic tables and deep dive into the details of product planning — make sure stakeholders can understand what is planned, why and when.

</aside>