20. Every week
Make it a habit to talk to customers every week.
Talk to at least 2 a week. Ideally, more.
Bring your team
Bring the entire team. This includes engineers
and designers and anyone else who wants.
Listen
To what they want but really pay attention to
what their real problems are
Qualitative
Feedback
Imperatives
21. Every week
Make it a habit to talk to customers every week.
Talk to at least 2 a week. Ideally, more.
Bring your team
Bring the entire team. This includes engineers
and designers and anyone else who wants.
Listen
To what they want but really pay attention to
what their real problems are
Qualitative
Feedback
Imperatives
22. Every week
Make it a habit to talk to customers every week.
Talk to at least 2 a week. Ideally, more.
Bring your team
Bring the entire team. This includes engineers
and designers and anyone else who wants.
Listen
To what they want but really pay attention to
what their real problems are
Qualitative
Feedback
Imperatives
24. BRING YOUR TEAM / RESULTS
Few to no
engineers can talk
about the
customer value
they build
A few engineers
can email
colleagues to talk
about their work
Some engineers
start repeating
feedback in
meetings
Engineering teams
start suggesting
roadmap items by
innovating on
feedback
Everyone is
thinking about
product and how
to impact that
WEEK 1 WEEK 2 WEEK 3 WEEK 4 Present
27. Every week
Make everyone use data. Send around data
constantly. Make it a thing that people enjoy
getting.
Bring your team
Get engineers curious about data. Get data on
your roadmap. Set up a day where you all stop
feature development and explore data.
Visualize
Get a great visualization tool. Without this, you
will hate looking into data.
Quantitative
Imperatives
28. Every week
Make everyone use data. Send around data
constantly. Make it a thing that people enjoy
getting.
Bring your team
Get engineers curious about data. Get data on
your roadmap. Set up a day where you all stop
feature development and explore data.
Visualize
Get a great visualization tool. Without this, you
will hate looking into data.
Quantitative
Imperatives
29. Every week
Make everyone use data. Send around data
constantly. Make it a thing that people enjoy
getting.
Bring your team
Get engineers curious about data. Get data on
your roadmap. Set up a day where you all stop
feature development and explore data.
Visualize
Get a great visualization tool. Without this, you
will hate looking into data.
Quantitative
Imperatives
30. BRING YOUR TEAM / RESULTS
No engineers
think about
effectiveness of
features
A few engineers
can think of things
to A/B test
Some engineers
start asking for
access to data
Engineering teams
start suggesting
roadmap items
based on data
Everyone is
thinking about
data and how to
build hypotheses
WEEK 1 WEEK 2 WEEK 3 WEEK 4 Present
32. Customer Wants
Your team know what the
customer wants in detail.
Customer Does
Your team know what the
customer does in detail.
Anyone on your team can answer
33. Team Mission
Your team knows what NOT
to focus on.
Customer Wants
Your team know what the
customer wants in detail.
Customer Does
Your team know what the
customer does in detail.
Anyone on your team can answer
34. Anyone on your team can
answer what you should
build next
AND NOW