Main Takeaways:
- Why do some products die off and others take off?
- What are the 4 key disciplines of product management and how do they maximize the chance that your product will deliver value?
- How can you master the 4 key disciplines and become in the top 10% of PMs?
7. 3
About me
I’ve had the privilege of working as a PM for 17 years at a broad range of companies
My early days… My big company days.. My startup days.. My return to big tech…
13. 9
Airborne Laser
Plane
X-32 Jet Engine
Engine
Ford S/C Thunderbird
Car
Amazon Seller Desktop
Software
GoSmart Mobile
Wireless Service
Flywheel Taxi
Mobile App
Clippit App
Mobile App
iZora Drone
Drone
Logitech Pop
Smart Device
Logitech Harmony
Smart Device
Google Instant Quotes
Web Feature
Virtual Mechanic
Software
Shopdora
Software
Mortio
Software
Zyclone Fitness
Fitness Center
Icebeast
Sporting Goods
FAILURE FAILURE FAILURE FAILURE
FAILURE FAILURE FAILURE FAILURE
FAILURE FAILURE FAILURE FAILURE
FAILURE FAILURE FAILURE FAILURE
14. 10
“Failure is so important. We speak
about success all the time. But it is
the ability to use or resist failure
that often leads to great success.”
- J.K. Rawlings
19. 15
What is an irresistible product?
Feasible Desirable Viable
You build it Customers want it You make money o
ff
it
20. 16
If it’s so easy then why do
so many products fail?
Execution Risk Market Risk Financial Risk
You can’t build it Customers don’t want it You don’t make money o
ff
it
21. 17
Your primary job as a PM is
to eliminate these risks
PM
Eliminate
Execution Risk: You can’t build it
Market Risk: Customers don’t want it
Financial Risk: You don’t make money o
ff
it
24. 20
How they prevent failure
Vision Design Execute Learn
Execution Risk
Market Risk
Financial Risk
Provide clarity on what
to build
Build e
ffi
ciently
Pursue only what
customers want
Test that customers
want your product
Learn from customers
and iterate
Project how you will
make money
Measure your results
and iterate
Obtain enough
resources
Know exactly what to
build next
Ensure your product
is high quality
Ensure engineering has
clear direction
Keep engineering
costs down
27. 23
The vision process
Identify customer jobs Paint the vision Share the vision
Your customer is hiring your
product to get a job done (e.g.
get a job as a PM) and has
selection criteria (e.g. fast,
fun, easy).
You want to design a product
that performs the job better
than other alternatives.
Approach:
• Identify Jobs
• Identify Selection Criteria
Clearly describe the problem
you’re solving, your solution,
why it’s better than existing
alternatives, who would use it,
and how you make money.
Elements:
• Problem
• Solution
• Customer
• Market Opportunity
• Financials
• Team
Share your vision with team
members, address their
concerns, explain why it’s
important, and get them to
rally behind it.
Team Members to Rally:
• Executives Sponsor
• Managers
• UX
• Engineering
• QA
• Marketing
• Sales
• Operations
29. 25
Design
Objective
Turn your vision into clear instructions to engineering describing exactly what to build
Team
Product Manager
Researcher
Designer
Engineers
30. 26
The design process
Decide Prototype De
fi
ne
Decide exactly how your
solution will work.
Tools:
• Product Questions - list out
all the decisions you need
to make, all the possible
solutions, and your
recommendation; then walk
through them with the
cross-functional team to
decide on each of them
Test your solution with
customers and continue to
iterate until it is valuable to
them.
Tools:
• Inspiration
• Mockups
• Prototype
• User Studies
• Iteration
De
fi
ne your solution in detail
so that engineering can build
it without any ambiguity.
Tools:
• Mockups
• User Flow
• User Stories
31. 27
“The design step has distinct two
phases: a) iterating on your solution
until your customers love it and then
b) specifying your solution so its
crystal clear what to build.”
- Dave Mohla
33. 29
The execution process
Develop Test Resolve
Build your solution as
e
ffi
ciently as possible.
Tools:
• Backlog
• Sprint Planning
• Sprints
Ensure your solution works
exactly as you speci
fi
ed.
Tools:
• Continuous Releases
• Story Veri
fi
cation
• End-to-End Testing
Resolve any issues your
engineers raise so they have
clear direction and are never
blocked.
Approach
• Issue Identi
fi
cation
• Solution Options
• Solution Decision
34. 30
“In the execution step, your goal is to
ensure your engineers can build your
solution as ef
fi
ciently and at as a
high quality level as possible.”
- Dave Mohla
35. 31
Learn
Objective
Measure whether your solution has delivered on its intended objectives and then course correct
Team
Product Manager
Data Analyst
Researcher
36. 32
The learning process
Measure Analyze Update
Measure all the assumptions
in your vision.
Tools:
• Metrics
• Dashboards
• Reports
• Customer Surveys
• Sales Feedback
Understand exactly how your
solution is working and know
what to do to improve it.
Tools:
• Deep Dive Analyses
• Event Tracking
• SQL Database Querying
• Spreadsheet Analysis
• Database Visualization
Incorporate your learnings into
your roadmap and use those to
launch subsequent releases of
your product that.
Approach
• Updated Vision
• Updated Design
• Roadmap
• Releases
37. 33
“The learn step is where you
determine whether your original
hypothesis is correct and then adjust
based on your learnings.”
- Dave Mohla
38. 34
Iteration is key
Vision Design Execute Learn
The more iterations you can do and the
faster you can do them, the sooner you can
narrow in on a product that customers love
and delivers on your business goals
Iterate
40. 36
Zendesk Insights
• Let’s say you’re the PM for Zendesk Insights
• Zendesk is an online tool for tracking and
resolving customer issues via tickets
• You want to enable Zendesk customers to
get deeper insight into their customer
interactions
41. 37
The steps applied
• Identify the customer
jobs (e.g. understand
how customers are
interacting with us,
know what to change)
and selection criteria
• Research existing
solutions and customer
pain points
• Create vision deck with
the jobs, problem,
solution, customer,
business model, and
revenue opportunity
• Generate inspiration
from other reporting
dashboards
• Create mocks and
prototypes of
experience that deliver
on jobs and selection
criteria
• Test prototypes with
users and iterate and
improve them
• Create
fi
nal mocks and
stories detailing your
solution
• Create backlog of
stories in priority order
• Plan weekly sprints to
tackle stories in chunks
• Continually release
builds as features are
developed
• Test and verify all the
stories have been met
• Resolve any issues or
questions that any
engineers have
Vision Design Execute Learn
• Track key metrics
related to the adoption,
revenue, and usage of
your product
• Perform analyses to
understand exactly how
users use product
• Run surveys with
customers to get
feedback
• Plan subsequent
versions of product
based on feedback
42. 38
How the steps are practiced
Vision Design Execute Learn
Working Backwards
Doc with Press
Release & FAQ
Strategy Deck
Investor Pitch
Mocks
Mocks
Prototype
User Testing
Mocks
Technical Design
Product Requirements
Doc (PRD)
TPgM
User Stories
Sprints
Backlog
Product Requirements
Doc (PRD)
OKRs
Metrics Reports
Weekly Metrics Meetings
In-House Dashboards
In-House Logging
In-House Tools
3rd Party Dashboards
3rd Party Logging
3rd Party Tools
Done especially well