Professional Documents
Culture Documents
Product Management
Learning
w/ Shreyas Doshi
Shreyas Doshi
get the job
=
→
1.
Being suitable 2. Current company is the best place
↳eat
2.
Becoming 3 .
side projects .
3 '
Picking
the
Right circle of
places circle
'
trails required of
PM are
to break into influence
sacred
High Agency prerequisites to concern
Pml!
as a
Agency
↓
✓ \
to
Finding a
way influential
find to get something Trails
skills -
communication
done despite I /
the challenges ownership
hesitance creative
exertion
self
confidence
?⃝
1Eureat
i::÷
-
/
product sense
Analytical sense
Lime
Exertion sense
Base case
f-
1. Eliminate liabilities sugar
F-
-
-
-
2. median
-
TIE
up to the median .
iiaeiib
-
into
strength
-
3. turn
superpower .
✗
→ 660 hows Carter
168 hours
else
108 everything
↳ 60 hows Cartier iron
It science
result
Business case
creakily perioniivdior
✓ emotional data
80%
roy.
appeal utility
focused intuition
ongoing delight
project study
want to
"
Tt you
should
1) be great you
be able to operate
"
on all points .
3. picking places
www.Arstcompanyaytomerlirst
-
→ Amazon
product greatest 1. is the
tech first →
google
leverage
first →
arm obsessed
design z . are functions are
first →
Yahoo of product
competition z .
Expansive view
13ᵗʰ Sept 2022
where do 9 start to be a
Great Product
Marty Corgan
Manager
Éems
i) product teams → the good
the bad
ii) Feature teams →
I
?⃝
"" "
"
means →
→s¥ustomµ
identify problems and build
not the business .
solutions accordingly compared
to feature and
and delivery teams
\
→ Given customer
to tho are
given sonny
business problems .
solve
[M
.
and
discover , design
kmeaswudontwme-f.IN
→
solutions ↳ tummy ,,
clear ownership
Risks
←
lor it ? → prod -
build ?
feasibility → can we →
Engg .
valuable KANR.AT
problem walk
to
SCRUM
some teas are
viable
earns
Senior leadership
→prerequisite :
support
Ensure Necessary Product
→
leadership .
→
Raise bar for product teams
→
Reintroduce teams to Business
GMestimation
Thought Experiments
ME pm at Youtube :
Avg -
watch Duration ↓ 40% Rot ?
P-r-eovest.ms
1. aerography
2- Platform
Core t Reels + stories
Videos →
'
3 .
Kind of
4.
Bugs → App releases
that crashed
User journey
user per day ? ↑ increased
→# of sessions per
not
? ↑ 35
of videos starts per
.
user
-
→ #
of button
design changes ?
☒ Guesstimate orders receives in a week
of sviggy
:
#
.
1-
aeoghaepwy →
Bengaluru
20M
Population
:
12M
Smartphone → boy
y
.
+
frequency odd
%spl
#
PIP
Internet quay
0.9m
Households 604 7m71 -8m o 5
-
/
.
a
IM I 1m
students lot
segmentation
→
.
user
16M
30% 4m 4
working Prof
.
_
Total : 18m
food subscriptions :
v04
before moving
drop
of the
.
2) Time
point
3) user segmentation .
I 6M Sept 2022
Careerladder
& Skills
w/ Diego Granados
whati-p-Egmentlpayinwoeq-PM-stalkl.ro
|
etc
customers → I :| s with Eng , Ds ,
Pms , Design
→ Be the best storytellers → Broader team presentations
calls
and influence others .
→ customer / partner
→ different →
meetings to check progress
communicate in Team
,µµ, p_ÉYENER
→
ummmm ,
visions
? influence
careeiraddcr :
UP 't cpo
APM Jr PM → PM → Sr PM → director of →
→
product
→
.
.
Product
Flavours of product
Management
:
↳earth : customers _ competitors ,
market trends ,
Business Model
"
product Manager Responsible :
ATM ,
MVP , wsecase scenarios
solutions
localisation ,
globalisation ,
performance
Responsible :
Bug triaging . sprint tracking
Eng firing
Growth PM → Focus
3. Metric optimization Expansion
:
,
bikes poutine :
A/B experimentation Questioning ,
storage sharing ,
Effective PRDS
w/ Bhandari
Apoorva
gPRDs
The
Part 2 ?
Parl
¥w
✗
why ?
✗ Go to Toots
✗ who ?
÷."
-µµag;gI→_ ☒
Business
user
strategy
experience
-
Analytics
pm
#"
QA
M
0ps &
Business
lhyPRDs?_ low
Conversion is
Eg
:
:
1- Conviction
the
How many people
are
affected by
2- Quantification :
problem
Collaboration : clients
3.
engineers
users
by designers
-
,
, ,
engineers and
QA
document primarily toe
business impact
Business do e →
PRD ?
|
3) Product
|
2) objective scope
1) provemement _
• went stabs
• "
ˢᵗM
current
•
solution •
outs cope
• limitations of
a.
g. www..gg ,
feature
and
key challenges
◦
their impart
a) Metric Tracking
)
" ʳʰʳʰᵗʳʰʳʰᵈʰʳʰ -
Event creation
•
51 Functional
Requirements • Dash boarding
b) Scenario Handling
7) wireframing
8) Version and Release Plan
Mistakes
① Jump to solutions
before understanding
the problem .
② Create navigation
both happy
using
and sad flows .