This document summarizes a product summit discussing frameworks for capturing feedback and incorporating it into a roadmap. It discusses that a roadmap should represent the next priorities to get a product closer to its vision and address users' needs. An effective roadmap communicates priorities to the team. The summit also discusses treating a product like a living organism and generating data from across an organization to understand users and inform the roadmap. It emphasizes focusing on outcomes rather than features, identifying pain points, and creating roadmaps at 6 week, 6 month, and 6 year horizons. The document stresses the importance of acting ethically and avoiding harm when developing products.

1. USV Product Summit
Kevin Hsu
1

2. 2

3. Frameworks for capturing and incorporating
feedback into a roadmap
3

4. 4
Rodrigo Davies, Product Manager
4
Jordan Agnew, Product Manager
Your roadmap should represent two things;
1) What are the next things you want to
tackle that get your product closer to its end
vision 2) Which jobs to be done for your
users are you trying to help solve in the near
future
A roadmap is a device to communicate to
(and remind) the team what we're doing, in
what order and what success looks like at
each stage. It should be legible by people
who are familiar with the product, but not
necessarily working on it.

5. The roadmap is just an output.
5

6. 6
Sales
Engineering
Customer Support
Product
Living organisms

7. 7
Sales
Engineering
Customer Support
Product
Living organisms
Us

8. 8
Sales
Engineering
Customer Support
Product
Nervous System

9. Data generated
9

10. Understanding the data
10

11. What does your companies
nervous system look like?
11

12. We don’t believe in
roadmaps.
12

13. Product market fit
13

14. Finding product market fit
14

15. 1. How would you feel if you couldn't use the
product anymore?
15
2. What type of people would benefit from the
product?
3. What do you benefit from most from the
product?
4. How can we improve the product for you?

16. 16

17. Having product market fit
17

18. Things we believe in
Iterating existing product
Scale
Quality
Customer feedback

19. 19

20. 20

21. 21
Outcomes not features
Pain, frequency, density
6 weeks, 6 months, 6 years

22. Name one area of your work
that has been frustrating
22
Rate the pain (1-10)
Rate the frequency (1-10)

23. 23

24. 6 week plan - every week
24
6 month plan - every month
6 year plan - every quarter

25. 25

26. Business, Product,
Engineering
26

27. Demos
27
Measure/learn
Product forum

28. 28
Too many meetings?

29. The Blind Spot
29

30. https://arstechnica.com/cars/2017/08/vw-engineer-sentenced-
to-40-months-in-prison-for-role-in-emissions-cheating/
This happened
30
I'd like append something to what I said earlier about the job of a product person. I think the job of a product person is to solve problems efficiently, quickly, and ethically.

31. Do no harm.
31

32. 🌎
32

33. Thank you
33