Main takeaways:
A PM's day to day job is utter chaos -- writing docs, communicating with users, navigating the organization, dealing with fires -- constantly!
In the middle of flying a plane when it is still under construction, how does a PM even find time to think about the long-term plans and vision?
There are several practices that PMs can do, amidst the noise, to play the long game with your product, and your career.
5. How to think long-term
(When everything is on ļ¬re)
Glenn Wilson
May 2021
6. Who am I?
Group Product Manager at Google for 13 years
MBA, Massachusetts Institute of Technology ā08
Software engineer, various startups
BS, Computer Science, University of Michigan
9. Write PRDs
Design UX
Executive
presentations
Talking with
customers
Bug triage
Tech support
Build
roadmaps
Navigating the
organization
Website is
down!
Eng is blocked
on you!
Angry
customer!!
Emergency
executive
review!
Biz partners
backing out!
New
dependencies!
10.
11. Whatās our 5 year
vision?
Who are we and
where are we
going?
12.
13. What are my tips and tricks for getting out of this?
ā Recognize what āemergenciesā and ācritical issuesā do to you
ā Objectively assess the cost & beneļ¬t of the work you have to do
ā Ruthlessly prioritize, constantly
ā Set aside bandwidth for unstructured thinking and keep it sacred
16. Super critical - do it now!
Meh, do it whenever Important - do it soon
17. Late PRD that eng
is blocked on
Feature the CEO
is demanding
Bugfix for angry
customer
Slides for
publicly-visible
product talk
Super critical - do it now!
Meh, do it whenever Important - do it soon
Think about the
future - 1, 5, 10
years from now
19. Project Expected Outcome If I donāt do it right now... Workload
Critical bug Stop losing 3% revenue We lose 3% of revenue/day High
Write Foobar
PRD
Advance project to
product review stage
Product review gets pushed
out. Engineers do other stuff
Medium
Talk to angry
customer
Customer isnāt angry
anymore
Customer will be angry.
Maybe -1% revenue
Low
CEO demanding
feature
CEO is happy, +3% more
revenue
CEO will be unhappy High
20. Priority Project Expected Outcome If I donāt do it right now... Workload
P0 Critical bug Stop losing 3%
revenue
We lose 3% of revenue/day High
P1 Write Foobar PRD Advance project to
product review stage
Product review gets
pushed out. Engineers do
other stuff
Medium
P2 Talk to angry
customer
Customer isnāt angry
anymore
Customer will be angry.
Maybe -1% revenue
Low
P2 CEO demanding
feature
CEO is happy, +3%
more revenue
CEO will be unhappy High
Not going
to do.
Everyone
should
know it!
21. Priority Project Expected Outcome If I donāt do it right now... Workload
P0 Critical bug Stop losing 3%
revenue
We lose 3% of revenue/day High
P0 Critical exec
review
Execs questions are
answered
Backlash from boss &
others
Medium
P1 Write Foobar PRD Advance project to
product review stage
Product review gets
pushed out. Engineers do
other stuff
Medium
P2 Talk to angry
customer
Customer isnāt angry
anymore
Customer will be angry.
Maybe -1% revenue
Low
P2 CEO demanding
feature
CEO is happy, +3%
more revenue
CEO will be unhappy High
Line
does
not
move
down!
New
interrupts
push the
list down
22. Ugh, doing this constantly will eat up a ton of time
ā Snippets, quarterly goals
ā Communicate what youāre doing with teammates & manager
ā Everyone can see your prioritized list
ā Donāt cut into unallocated time
23.
24. Priority Project Expected Outcome If I donāt do it right now... Workload
P0 Major bug Stop losing 3% revenue We lose 3% of revenue/day High
P1 Feature foo +10% active users Partner team will back out
of the project
Medium
P2 Feature bar +5% early funnel
retention
We do it next quarter Low
P2 Minor bug Better user experience,
better satisfaction
Users have to keep using
workaround, less
satisfaction
High
25. If you take anything away...
ā Very little is actually critical -- your brain plays tricks on you
ā Ruthlessly prioritize, constantly
ā Build in intentional slack into your time planning
ā Make sure everyone knows what youāre doing -- and NOT doing
ā Keep unstructured time precious