Main takeaways: - Gathering requirements from various teams and assessing their impact. - Create the product vision, Prioritize all the collected requirements based on product vision, and create a roadmap. - Communicate the roadmap to the respective teams and revise based on their feedback.

1. www.productschool.com
Coordinate Roadmaps & Work with
Multiple Teams by Amazon PM

2. CERTIFICATES
Your Product Management Certificate Path
Product Leadership
Certificate™
Full Stack Product
Management Certificate™
Product Management
Certificate™
20 HOURS40 HOURS40 HOURS

3. Corporate
Training
Level up your team’s Product
Management skills

4. Free Product Management Resources
BOOKS
EVENTS
JOB PORTAL
COMMUNITIES
bit.ly/product_resources
COURSES

6. Product Roadmaps
Best way to create a roadmap when working with multiple teams and stakeholders

7. Introduction
I am Moumita Paul. Product Manager – Technical
at Amazon, India. MBA from Indian School of
Business. Undergraduate in Engineering.
Overall 12 years of experience. 6 years of
experience in Product Management.
Avid video gamer. Adventure sports enthusiast.
Couch potato.

8. Understanding your customers
Be patient with your stakeholders.
Your company stakeholders are also your
customers – sales team, legal team, finance
team, marketing team, customer support team,
other tech teams, etc.
Ask them their pain points, benefits of doing a
feature for them, etc. Ask them to also mention
the cost of not doing it.
Add it to your backlog and categorize them
under different labels.

9. Start with the Product Vision
Don’t start with the product backlog because -
You and your team will not know where you are heading.
Priorities will keep changing with time.
A product, without a vision, will be changed many times on few people’s
whims and fancies.
It’s demotivating to keep changing the product over and over again.
Leads to too much tech debt and doesn’t meet company bottom lines.
If you understand your organizations business and customers very well,
start with the desired product’s final state. Don’t restrict your
imagination. That is your product vision.
Or if you work in a continuous improvement model, then set a “guiding
principle” that will stand the test of time.

10. Building your Product Vision
Ask ‘WH’ questions about your product. I suggest doing this as a
writing exercise. A good start will be - why you want to build this
product? Who will use it? What are their key problems? How will it
be solved by your product, etc. The answer to these questions will
serve as the building block of your roadmap.
Next step will be – Ask more questions!
What does the final end state of your product look like?
How many years will it take to achieve your product vision?
How much of that do you want to achieve in this year?
Can the customers use your product from year 1 or month 1?
How are you solving the problems better than your competitors?
How will you measure the success of your product?
How are each feature in the product solving those problems
effectively?

11. Building your Roadmap
Now add the current state of the product, just below the
product vision. How many things from the product vision
are already built into the product? Break down the ‘X
year’ product vision into yearly goals.
Now you have a complete product vision, broken down
into yearly goals or OKRs. Next we will figure out how to
map the needs of your stakeholders and multiple teams
into a roadmap. This is when the product backlog comes
into the picture.
If you go through your backlog, you will notice some key
themes emerging from them. Prioritize them and see
where they fit into the product vision (1st
year, 2nd
year,
etc).
Your first draft of roadmap is ready to present to
leadership and stakeholders.

12. Finalizing the Roadmap
When you present this roadmap to leadership and
stakeholders, they might want you to change the priorities
based on a ‘hot potato’ in their minds. Remember that
this roadmap is your mental model. Don’t be afraid of
explaining it to others, even if they don’t agree with you.
This is where the PM skills of pushing back comes into play
– where you refuse to reprioritize unless you are given a
data oriented, reasonable explanation for why you should
do it.
Once the priorities have been agreed on from multiple
stakeholders, then you can discuss with tech team on
effort estimations and then breaking it down into which
quarter they should be delivered.

13. Conclusion
Thank you The Product School for this opportunity. I would personally like to thank Katya E
and Saskia Pencock for the invitation, organizing this live webinar and allowing me to
interact with the students.

14. www.productschool.com
Part-time Product Management Training Courses
and
Corporate Training