Product Roadmap
Template validated by Amin Bashi, VP of Product, and Senior Director of Product at Product School
[Insert Title Here]
Start Here!
βοΈ Get all our Product Management Templates!
In this template: 4 Product Roadmaps
Agile
Feature
Outcome-Based
Visual
THE TECHNICAL: Agile Roadmap |
Good for: Highly technical projects |
To communicate with: Engineers + Product Dev |
Sprint-based |
Details small chunks of work linked to the epics and features that will be released with sprints. |
THE GO-TO: Feature Roadmap |
Good for: Detailed solutions and the steps to get there |
To communicate with: Product Team |
Time or progress-based |
List of features to be developed and released for a product. Shows the solution, not the problem space. |
THE MODERN: Outcome-Based Roadmap |
Good for: Aligning Product Vision + Action |
To communicate with: Product Team, influential stakeholders |
Now-next-later framework |
Uses Product Vision and business goals as a starting point and solves user problems that will lead to those desired outcomes. |
THE NO-FRILLS: Visual Roadmap |
Good for: An easily digestible overview |
To communicate with: Influential stakeholders; non-Product team members |
A high-level view of the roadmap that is simple and easy to understand. |
To explore later: The different types of roadmaps
Timeline
Technology
Agile
Feature based
Short and long term
Outcome based
Visual
Business
OKR
Experiment based
Product launch
Ready to double click into these roadmaps right now? Then you need The Ultimate Guide to Roadmapping
Feature Roadmap
The baseline Product Roadmap that every PM has in their toolbelt. Youβve identified your solution and need detailed steps on how to get there. What to include: οΏ½
Example: Feature roadmap
Q1
Q2
Q3
Q4
Q1
Profile
Notifications
Community
Gamification
New Preference Settings
Login with LinkedIn
Omni Channel Notifications
Vendor Update
Integrate Reputation
Translations
New Badging System
New Graphics
Today
Create your own feature roadmap
Create an agile roadmap in Google Sheets or download as an Excel.
Feature Product Roadmap
Outcome-Based Roadmap
Reverse engineer the Product Roadmap process by starting with Product and Business vision, then work your way down to user behavior.
What is an Outcome?
outcome [owt-kuhm]
noun
A measurable change in customer behavior.
Define outcomes by the customer behaviors you need to change in order to achieve your goal. The goal of any feature you ship to a customer should be to change the customerβs behavior in a measurable and positive way.
Strategy β Discovery
Business Impacts
Product Vision
Principles / Values
Goal/Objective
Goal/Objective
Outcome/
Key result
Outcome/
Key result
Outcome/
Key result
Outcome/
Key result
Opportunity
Opportunity
Opportunity
Opportunity
Opportunity
Opportunity
Opportunity
Opportunity
Discovery β Delivery
Opportunity
Opportunity
Opportunity
Opportunity
Idea
Idea
Idea
Idea
Solution
Solution
Solution
Solution
Feature or Experiment
Feature or Experiment
Feature or Experiment
Feature or Experiment
Idea
Idea
Idea
Idea
Step 1: Define Product Vision
Project name
| ||
Roadmaps are only as good as your prioritization strategy. Starting with Product Vision will help you ruthlessly prioritize and make decisions on what to build and what not to build. | ||
| ||
What will this product be like in 5 years? |
|
What are our business values and needs? |
|
What would the world look like if we solved our customer problem? |
|
Product Vision Statement | In the next 5 years, this product will ____ and address ___ business needs. |
Watch this video for more guidance on Product Vision
Step 2: Define long-term Goals/Objectives
Project name
| ||
2 to 3 goals for your company for the next 1β2 years that, if achieved, would result in you getting closer to your Product Vision. In the Objectives and Key Results (OKR) framework, these are also known as Objectives. | ||
| ||
Objective #1 | |
Objective #2 | |
Objective #3 | |
Step 3: Define Outcomes/Key Results
Project name
| ||
Now, map 1 to 3 short-term Outcomes to each Goal youβve laid out. What are concrete actions you can take in the next few months to move towards that goal? In the Objectives and Key Results (OKR) framework, these are also known as Key Results. | ||
| ||
Key Result A Maps to Objective #1 | |
Key Result B Maps to Objective #1 | |
Key Result C Maps to Objective #2 | |
Key Result D Maps to Objective #2 | |
Key Result E Maps to Objective #3 | |
Step 4: Identify Opportunities
Project name
| ||
Opportunities for changing customer behavior. Customer Problems, Customer Gains, or Customer Pains, which, if solved, would lead to the desired Outcomes/Key Results. | ||
| ||
Opportunity | |
Opportunity | |
Opportunity | |
Opportunity | |
Opportunity | |
Step 5: Features OR experiments
Project name
| ||
Modern Product Teams are increasingly Experiment- based. At this point in the process, decide whether to take the route of building features or running experiments. If building features Identify features that take advantage of Opportunities and move you towards Outcomes/Key Results, and decide which ones to build. This way you know all the features you work on help solve the customer problem AND achieve business objective. If running experiments Define what solutions you want to test tied to Outcomes/Key Results. Explore different ideas and test their performance. | ||
| ||
Feature/ Experiment | |
Feature/ Experiment | |
Feature/ Experiment | |
Feature/ Experiment | |
Feature/ Experiment | |
Outcome-based Product Roadmap
Goal/Objective |
Goal/Objective #1 |
Goal/Objective #2 |
Goal/Objective #3 |
Later (6+ months) |
|
|
|
|
|
|
Now (1-2 months) |
Outcome/Key Result Customer behavior A changes from X% to Y% by date Z |
|
|
|
|
Next (3 - 6 months) |
|
|
|
|
|
|
Workforce management app
Example: Outcome-based Product Roadmap
Product Vision Statement | In the next 3 years, this product will be the #1 mobile workforce management application for hotel maintenance across the Americas and Europe |
2023 Goal | Utilized daily by 25% of hotel maintenance crews in European target markets by July 30 2023 |
Example: Outcome-based Product Roadmap
Goal |
Double DAU within the next 6 months |
Go big in Europe with 35% usage |
Later (6+ months) |
Daily use At least 80% of all app users manage at least 5 work orders weekly |
Increase native language use 35% of all application usage is in Portuguese, French, or Spanish by end of 2023 |
Now (1-2 months) |
EU Daily Usage = 34% of users |
Total downloads = 120k |
|
Work in your language Customers create a work order in their language within 5 min of app download by Dec 31 2022 |
Next (3 - 6 months) |
EU Usage Mobile worker DAU increased 30% in EU by Feb 28, 2023 |
Total downloads Daily app downloads up by 80% by end of 1H2023 |
Expand deeper in EU Enter Easter European EU Market by 1Q2023 |
Compliance needs Full GDPR compliance by 1Q2020 |
Agile Roadmap
Letβs get technical. A roadmap for details, execution, and communication with engineers.
Example: Agile Roadmap
Sprint 1.1
1.2
1.3
2.1
2.2
Development
Product
QA
UX
Front-end prototype
Repository deployment
Environment setup
Back-end engine
Feature A scope
Store review
Demo staging
Feature B scope
Environment setup
Integrated prototype
Analytics engine
Unit testing
Back-end analytics
Engineering review
MVP Requirements
Roadmap brief
Feature requirements
Pilot
Feedback
Launch
Customer Testing
Backlog sweep
Feature release A-B
Wireframe
UX Design Templates
Feature-level design
UX Audit
High level design
Metrics
QA
Variance testing
UAT
PM Testing
Create your own agile roadmap
Create an agile roadmap in Google Sheets or download as an Excel.
Agile Roadmap
Visual Roadmap
When you need to get stakeholder buy-in, condense your plan into a visual roadmap.
Create your own visual roadmap
Short description goes here
Title 01
Short description goes here
Title 02
Short description goes here
Title 03
Short description goes here
Title 04
Example: Visual Roadmap
Q1 - transfer main web architecture to new CMS
Website launch
Q2-Q3 - identify and debug high priority issues with transfer
Debugging
Q4 - create workflows and architecture for adding new content types
New content flow
Q1-Q2 2023 - Finalize old, low priority content transfer
Transfer old content
More resources!
Learn about OKR-Driven Product Roadmaps by Microsoft Principal PM
Or, dive deeper into Product Management with our free resource collection.
Any feedback on this template? Share it here!