0% found this document useful (0 votes)
21 views27 pages

Pm Template_ Product Roadmap (1)

This document provides a comprehensive guide on creating various types of Product Roadmaps, including Feature, Outcome-Based, Agile, and Visual Roadmaps. It outlines the steps to develop each roadmap, emphasizing the importance of aligning product vision with user outcomes and stakeholder communication. Additionally, it includes templates and examples to assist product managers in effectively planning and executing their product strategies.

Uploaded by

Shwetambari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views27 pages

Pm Template_ Product Roadmap (1)

This document provides a comprehensive guide on creating various types of Product Roadmaps, including Feature, Outcome-Based, Agile, and Visual Roadmaps. It outlines the steps to develop each roadmap, emphasizing the importance of aligning product vision with user outcomes and stakeholder communication. Additionally, it includes templates and examples to assist product managers in effectively planning and executing their product strategies.

Uploaded by

Shwetambari
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 27

Product Roadmap

[Insert Title Here]

Template validated by Amin Bashi, VP of Product, and Senior Director of Product at Product School
Start Here!
1. Read through to understand what a Product Roadmap is
2. Prefer video content? Check out How to Build Strategic Roadmaps
3. Select the best roadmap model for your needs
4. Share with your team!
5. Get stakeholder buy-in

☝️Get all our Product Management Templates!


In this template: 4 Product Roadmaps

Feature Outcome- Agile Visual


Based
THE GO-TO: THE MODERN: Outcome- THE TECHNICAL: THE NO-FRILLS:
Feature Roadmap Based Roadmap Agile Roadmap Visual Roadmap

Good for: Good for: Good for:


Good for:
Aligning Product Vision + An easily digestible
Detailed solutions and Highly technical projects
Action overview
the steps to get there

To communicate with: To communicate with: To communicate with: To communicate with:


Product Team Product Team, influential Engineers + Product Dev Influential stakeholders;
stakeholders non-Product team
members
Time or progress-based Sprint-based
Now-next-later framework

List of features to be
Uses Product Vision and Details small chunks of A high-level view of the
developed and released
business goals as a starting work linked to the epics roadmap that is simple
for a product. Shows the
point and solves user problems and features that will be and easy to understand.
solution, not the
that will lead to those desired released with sprints.
problem space.
outcomes.
To explore later: The different types of roadmaps

Outcome based Business Experiment Timeline Agile Short and


based long term

Visual OKR Product Technology Feature based


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:

1. Features, by category or theme


2. Simple titles
3. An indication of progress or time
Example: Feature
roadmap Today

Q Q Q Q Q
1 2 3 4 1

New Preference Settings


Profile
Login with LinkedIn

Omni Channel Notifications


Notifications
Vendor Update

Integrate
Reputation
Community
Translation
s

New Badging System


Gamification
New Graphics
Create your own feature roadmap

Create an agile roadmap in Google


Sheets or download as an Excel.

MAKE A COPY DOWNLOAD

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.

1. Define Product Vision


2. Define long-term goals
3. Identify opportunities
4. Define desired short-term outcomes
5. Build features aligned with outcomes
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 Product Vision Principles /


Impacts Values

Goal/Objective Goal/Objective

Outcome/ Outcome/ Outcome/ Outcome/


Key result Key result Key result Key result

Opportunity Opportunity Opportunity Opportunity Opportunity Opportunity Opportunity Opportunity


Discovery → Delivery

Opportunity Opportunity Opportunity Opportunity

Idea Idea Idea Idea Idea Idea Idea Idea

Solution Solution Solution Solution

Feature or Feature or Feature or Feature or


Experiment Experiment Experiment Experiment
Project name
Step 1: Define Product Vision
Roadmaps are only as
good as your prioritization What would the world
strategy. What are our business What will this product
look like if we solved
values and needs? be like in 5 years?
Starting with Product our customer
Vision will help you problem?
ruthlessly prioritize and
make decisions on what
to build and what not to
build.

Product Vision In the next 5 years, this product will ____ and address ___ business
Statement needs.

Watch this video for more guidance on Product Vision


Project name
Step 2: Define long-term Goals/Objectives
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.
Objective #1
In the Objectives and Key
Results (OKR) framework,
these are also known as
Objectives.
Objective #2

Objective #3
Project name
Step 3: Define Outcomes/Key Results
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 Key Result A
towards that goal? Maps to Objective #1

In the Objectives and Key


Results (OKR) framework, Key Result B
these are also known as Maps to Objective #1
Key Results.
Key Result C
Maps to Objective #2

Key Result D
Maps to Objective #2

Key Result E
Maps to Objective #3
Project name
Step 4: Identify Opportunities
Opportunities for
changing customer
behavior. Customer
Problems, Customer
Gains, or Customer Pains,
which, if solved, would Opportunity
lead to the desired
Outcomes/Key Results.

Opportunity

Opportunity

Opportunity

Opportunity
Project name
Modern Product Teams are Step 5: Features OR experiments
increasingly Experiment-
based. At this point in
the process, decide
whether to take the route
of building features or
running experiments. Feature/
If building features
Experiment

Identify features that take Feature/


advantage of
Opportunities and move
Experiment
you towards
Outcomes/Key Results, Feature/
and decide which ones to Experiment
build.

This way you know all the Feature/


features you work on help Experiment
solve the customer
problem AND achieve
business objective.
Feature/
If running experiments Experiment

Define what solutions you


want to test tied to
Outcomes/Key Results.
Explore different ideas
and test their
performance.
Outcome-based Product Roadmap

Goal/Objective Now (1-2 months) Next (3 - 6 months) Later (6+ months)

Outcome/Key Result
Customer behavior A
Goal/Objective #1
changes from X% to Y% by
date Z

Goal/Objective #2

Goal/Objective #3
Workforce management app

Example: Outcome-based Product Roadmap

In the next 3 years, this product will be the #1 mobile workforce


Product Vision
management application for hotel maintenance across the
Statement
Americas and Europe

Utilized daily by 25% of hotel maintenance crews in European


2023 Goal
target markets by July 30 2023
Example: Outcome-based Product Roadmap

Goal Now (1-2 months) Next (3 - 6 months) Later (6+ months)

EU Daily Usage = 34% of EU Usage


users Mobile worker DAU
increased 30% in EU by Daily use
Double DAU within the Feb 28, 2023 At least 80% of all app
next 6 months Total downloads = 120k users manage at least 5
Total downloads work orders weekly
Daily app downloads up by
80% by end of 1H2023

Expand deeper in EU
Enter Easter European EU Increase native
Work in your language language use
Market by 1Q2023
Go big in Europe with 35% Customers create a work 35% of all application
usage order in their language usage is in Portuguese,
within 5 min of app Compliance needs
French, or Spanish by end
download by Dec 31 2022 Full GDPR compliance by
of 2023
1Q2020
Agile Roadmap
Let’s get technical. A roadmap for details, execution, and
communication with engineers.

1. Development Team ONLY


2. Small chunks of work
3. Detailed
4. Changes frequently
5. Sprint-based
Example: Agile Roadmap
1. 1. 2. 2.
Sprint 1.1
2 3 1 2
Front-end prototype Environment setup Store review Environment setup Unit testing
Developme

Repository
nt

Back-end engine Demo staging Integrated prototype Back-end analytics


deployment

Feature A scope Feature B scope Analytics engine Engineering review

MVP Requirements Roadmap brief Pilot Launch Backlog sweep


Produc

Feature
Feedback Customer Testing Feature release A-B
t

requirements

Wireframe UX Design Templates Feature-level design UX Audit High level design


U
X

Metrics QA Variance testing UAT PM Testing


Q
A
Create your own agile roadmap

Create an agile roadmap in Google


Sheets or download as an Excel.

MAKE A COPY DOWNLOAD

Agile Roadmap
Visual Roadmap
When you need to get stakeholder buy-in, condense your
plan into a visual roadmap.

1. Removes knowledge barriers


2. Effective communication
3. High level, key info
4. Streamlined, simple
5. Visually appealing
Create your own visual
roadmap

Title 01 Title 02 Title 03 Title 04


Short description Short description Short description Short description
goes here goes here goes here goes here
Example: Visual Roadmap

Transfer old
Website launch Debugging New content flow content
Q1 - transfer main Q2-Q3 - identify Q4 - create workflows Q1-Q2 2023 - Finalize
web architecture to and debug high and architecture for old, low priority content
new CMS priority issues with adding new content transfer
transfer types
More resources!

Learn about
OKR-Driven Product Roadmap
s by Microsoft Principal PM
Or, dive deeper into Product
Management with our
free resource collection.

Any feedback on this template? Share it


here!

You might also like