Roadmap planning - Top down, bottom up or both?
•Download as PPTX, PDF•
1 like•410 views
Overview of how to plan a lean roadmap based on vision, objectives, themes, ideas and customer feedback.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Roadmap planning - Top down, bottom up or both?
Similar to Roadmap planning - Top down, bottom up or both? (20)
Recently uploaded
Recently uploaded (20)
Roadmap planning - Top down, bottom up or both?
- 1. Roadmap Planning: Top down? Bottom up? Both!
- 2. Liz Love • Ten years’ experience • Large corporate product management team • First product manager (twice) • Director of Sales & Professional Services @ ProdPad
- 4. Top Down
- 5. Vision, Objectives and Strategy ● Vision = What you want to achieve with your product - the long term goal ● Objectives = What you will measure to prove your strategy is working ● Strategy = What you will build/make/do/change to achieve your vision
- 6. Vision
- 7. Vision, Objectives and Strategy • Vision = What you want to achieve with your product - the long term goal • Objectives = What you will measure to prove your strategy is working • Strategy = What you will build/make/do/change to achieve your vision
- 8. Why are Objectives important? • Guide-rails • Measure progress • Justify and explain your decisions
- 9. Vision, Objectives and Strategy • Vision = What you want to achieve with your product - the long term goal • Objectives = What you will measure to prove your strategy is working • Strategy = What you will build/make/do/change to achieve your vision
- 10. Vision, Objectives and Strategy Roadmap • Vision = What you want to achieve with your product - the long term goal • Objectives = What you will measure to prove your strategy is working • Strategy Roadmap = What you will build/make/do/change to achieve your vision
- 11. “Your Roadmap is a Prototype for your Strategy” Janna Bastow Co-founder, Mind the Product
- 12. Roadmaps
- 13. With themes……...
- 14. Bottom Up
- 15. Where do Ideas come from? • Internal stakeholders • Product, Sales, Marketing, Execs, Development, Support - everyone! • Customers/end-users Courtesy of the GDS Blog
- 16. Collecting Feedback - why? • Feedback helps your ideas to grow • Lots of feedback? Could be high impact! • Requesters are testers
- 17. Review, validate and move ideas through the product management workflow. New Prioritised Idea Backlog
- 18. Prioritize - Impact & Effort
- 19. Scoring for Impact? Impact Gain Creation Pain Relief Metrics/Reach XXS This is a small polish This is weird No impact XS This is a nice touch This is a bit inconvenient Barely noticeable S This is nice to have This is irritating Marginal gain M This should be there This is really poor Modest gain L This is really good This is really bad Significant gain XL This is hugely better This is a deal breaker Huge gain XXL This is revolutionary This is a total disaster World changer Example courtesy of Matt Stratford, PM at Elsevier
- 20. Scoring for Effort? Effort Technical Effort Design Effort Business Effort XXS No sooner said than done Eyeball it Do it XS Quick change Take a quick look Do it S A day or two Have you thought about….. Do it M Decent story Need some design spec Check with someone L A bit of an epic That’ll need design review Talk to a few people XL Big epic Needs an investigation Check with execs XXL It’s a Death Star Massive piece of work Needs a full business case Example courtesy of Matt Stratford, PM at Elsevier
- 21. Bringing it all together
- 22. Why?
- 25. Aligned with Company Direction