The document discusses best practices for creating and managing a product roadmap. It recommends taking a step back to focus on high-level goals, problems and themes rather than specific features. An effective roadmap provides strategic direction, aids communication, and facilitates collaboration. It should be treated as a living document that is updated transparently in response to changes. The key aspects are having strategic context, stakeholder communication, and focusing on goals rather than just features and dates.

1. Product Roadmap
How to best create and manage roadmaps?

2. Why this talk?

3. Not just features & dates

4. Take a step back!
http://www.romanpichler.com/blog/agile-product-planning-vision-strategy-tactics/

5. Outline
Product vision & strategy
Creating a product roadmap
Managing a product roadmap
What are product roadmaps?

6. What are product roadmaps?

7. Provide direction

8. Pair objectives & strategy

9. Aid communication
By Martin Eriksson, http://www.mindtheproduct.com/2011/10/what-exactly-is-a-product-manager/

10. What are product roadmaps?
Provide strategic and product direction
Offers rationale for decisions, resource allocation
and prioritisation
Effective communication tool
Facilitate stakeholder collaboration & decision making
Create continuity of purpose

11. Product vision & strategy
http://www.romanpichler.com/blog/agile-product-planning-vision-strategy-tactics/

12. Business vision

13. Business vision

14. Product vision
https://wiki.mozilla.org/Firefox/VisionStatement

15. Strategy - ‘Bit in the middle’
Business goals
Revenue & profit
User Experience
Business model
Value chain
Customer
segmentation
Design principles
Competitors User needs
Technology Compliance
Domain Geography
Strategy
Constraints

16. Product vision & strategy
Think big – A good vision is lofty and aspirational
A shared vision – Create a common sense of purpose
which is shared widely across the company
Motivating – Outlines product benefits for others
Use for decision-making – Use your vision as guide
when making business or product decisions
Distinguish between vision and strategy – A vision
should not be a plan that outlines how to reach a goal

17. Creating a product roadmap

18. Roadmap Wish list

19. Roadmap Customer only

20. ‘Old School’

21. ‘Old School’

22. What’s wrong?
What is the context?
Why are we doing certain things? Why not?
What value are we looking to deliver and why?
What business or user problems are we looking to
solve, for whom and why?
Don’t forget that your roadmap is a communication
and collaboration tool!

23. Pitfalls when creating
Common pitfalls when creating a roadmap:
Why? - Just a collection of features and timings
Dependencies - Not thinking about cross-product or
team dependencies
“Solution sickness” - Fixating on a feature or solution
upfront

24. ‘New School’: Goal oriented

25. Create a roadmap

26. Roadmap themes

27. Creating a product roadmap
Don’t fixate on features; focus on problems, goals,
assumptions or themes instead
Important to not lose sight of measurable results
Consider adding extra layers to allow for risks,
dependencies and product discovery (‘unknowns’)

28. Managing a product roadmap
By Janna Bastow, http://www.mindtheproduct.com/2014/07/product-roadmapping-prioritisation-portfolio/

29. Roadmap a one off

30. Roadmap Set in stone

31. Roadmap updates

32. Things can change

34. As long as you’re transparent

35. As long as you’re transparent

36. Managing a product roadmap
Treat your product roadmap as a living document
Be transparent about roadmap progress
Keep communicating to your stakeholders

37. Product Roadmap - 3 things
3 things to take away:
Take a step back before creating a roadmap
A roadmap needs strategic context and goals
Stakeholder communication is critical

38. Thank you!
@MAA1
https://www.linkedin.com/in/abrahammarc
https://marcabraham.wordpress.com/
https://medium.com/@maa1