This document provides guidance on developing an effective product vision, strategy, and roadmap. It emphasizes the importance of having a shared vision that motivates the team. The product strategy describes who the product is for and why, while the roadmap aligns goals and sets expectations. Both the strategy and roadmap should support and evolve with the vision. Collaboration, testing assumptions, and reviewing plans regularly can help ensure success.

1. July 12 2016

2. RESOURCES
Most of the information being delivered has been
pulled from Roman Pichler
(http://www.romanpichler.com/)

3.  Setting EXPECTATIONS
 Aligning stakeholders
 Team(s)
 Clear Goals
 True understanding of Product and Deliverables

4.  British Government Agency let people suggest name for new
$287M Polar Research Vessel
 Lessons Learned:
 Be Honest about asking for advice.
 If you ask for advice, be prepared to take it.
 If you ask for advice, be prepared to say NO.
 If you don’t take advice, be clear about why.
 Be clear about your expectations and why you are asking for
advice!

5. Vision
Product
Strategy
Product
Roadmap

6.  Guide for everyone involved in making the product a success.
 The ultimate reason for creating/maintaining product.
 Helps to attract the right team and the right customers.

7.  Should not be a plan, but the motivation for developing the
product.
 Everyone must have the same vision – Shared Vision
 Keep it short and sweet!
Example of Vision Board
(http://www.romanpichler.com/tools/
vision-board/)

8. Vision
Product
Strategy
Product
Roadmap

9.  The high-level plan to the vision
 Describes who the product is for and why people would want it
 What the business goals are and why the company would
invest
 Changes as your product changes
 Provides input for the Product Roadmap

10.  Start with what you KNOW now
 Focus on what matters MOST
 Use the Vision Board previously listed. Moving from Left to Right
 Collaborate
 Change and update your vision board

11.  Put it to the TEST
 You can do further interviews with specific target groups
 May turn out to be WRONG…Changing the Strategy is called
a PIVOT
 Other tools to help with Product Strategy:
 Business Model
 Lean Canvas

12. Vision
Product
Strategy
Product
Roadmap

13.  Describes how the product is likely to grow
 Facilitates learning and change
 Helps communication around product development
 Aligns the product and company strategy
 Helps set expectations for stakeholders, development,
marketing, etc.
 Strategic vs Tactical (Product Backlog)
 Owned by the PO
 Supports the Product Strategy and ultimately the Vision!

14.  Based on shared goals rather than features
 Mitigates conflict for Agile teams who only commit a few
weeks at a time

15.  Focus on goals and benefits – Product Strategy
 Tells the story of your product
 Keep it simple – Epics, User Stories, Designs belong in the
Backlog not Roadmap
 Collaborate – creates shared ownership and buy-in
 Say NO!
 Dates or NO Dates – Look at your audience
 Measurable – Goal level KPI’s
 $$$ - Look at skills possibly needed and how many people
 Review and Adjust

16.  Roadmap is a GUARANTEE
 High level plan based on what you know TODAY
 Epics and User Stories
 Wishful Thinking

17.  Do you have a VISION?
 Do you have a PRODUCT STRATEGY?
 Do you have a ROADMAP?
 Are you revisiting these things? If so, how often?