7. A B O U T M E
● 14 years of product management, currently at Facebook
● Worked at corporates
● Worked at startups
● Founded and helped start-ups
● Lived in 4 countries and 4 states
● Industry - several industries aka - customer focus, ecom, mobile, Finance
8. 2.
1.
AGENDA
Pre-req for roadmapping
What is a Product Roadmap
Four steps - Identify the Problem
Four steps - Business and Impact analysis
6.
3.
4.
5. Four steps - How to measure the success
Four Steps - feasibility & risk analysis
10. Roadmap is a PROCESS owned by PMs.
It facilitate product teams to balance innovation, stakeholders
requests, market trends, business needs, user feedback and a lot more
depending on the business. ..
11. Roadmap ensures:
● Right Priorities - what matters to the customers
● Aligned with business objectives
● Issues/problems are bubbled up and addressed
● Stakeholders and partners requests
● Innovative
● Top down + Bottom up
12. Pre-req - Know your customers..
● Behavior based Persona
● Lifestyle of your customer
● Live & experience
● Customer’s customer are your customers
● User groups - mixed
● ROI is not limited to numbers
14. 1. Identify the problem
One effective way to identify customer problems is to have a
parallel discovery track in place, it continuously generates validated
product backlog items in collaboration, keeping the organization
customer focused & innovative
15. Problem ---> Objectives
● Vague moon shot - How to deal with it
● Focusing on key big players
● Going into weeds
● Too much focus on competitors
16. 2. Impact & Business Analysis: It’s important to
align the Priorities as per the high level company
initiatives for that period of time
17. Primary Teams (⅔)
Researchers
Engg team
UX team
Sales
CS - User feedback
Leadership (⅓)
Marketing
Finance
Relationship Managers
Regional managers
Policy makers
Legal
Top down & Bottom up Product Roadmap Approach
Bottom
up + top
down
roadmap
18. 2. Business & Impact Analysis
● Business objectives depends on the growth stage
● Leadership curiosity is not a direction
● Do not leave priorities totally on the team
● Art of saying No - empathy builds understanding
19. Impact Analysis
● How much is the reach of the problem
● How important the problem is for the customer
● Primary/secondary/corner user case
● Quantify wherever possible
● Go beyond numbers
20. 3. How to measure the success : Identifying how to measure the success
ensures outcome based roadmap
● Key results → OKRs
● Northstar - one north star
● Connect all functions: Align all function’s efforts in the required direction
● Achievable in reasonable time
● Do not overcomplicate - few are good
● Avoid data paralysis
21. 4. Feasibility and risk analysis -Solution discovery - committed roadmap
● The engineering feasibility with engineering team
● Capacity planning : with high-level estimates
● Resolve any technical or functional dependencies
● Financial feasibility : allocating the budget
● Usability feasibility with the user group and UX feasibility with the
designers etc.
● Check the involved risk in developing or nor developing the proposed item/s
22. 2.
1.
S U M M A R Y
Value of having a roadmap & Pre-req
What is a Product Roadmap
Identify the Problem
Business and Impact analysis - > Objectives
6.
3.
4.
5.
How to measure the success -> OKRs and Prioritized list
Feasibility & risk analysis