Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
An Introduction to Product Management
Search
Graham Siener
May 23, 2013
110
1
Share
An Introduction to Product Management
Graham Siener
May 23, 2013
More Decks by Graham Siener
See All by Graham Siener
How technical should a PM be?
gsiener
0
210
Interviewing Exercise
gsiener
0
120
Data-driven Product Management
gsiener
4
220
Featured
See All Featured
エンジニアに許された特別な時間の終わり
watany
107
240k
Building Experiences: Design Systems, User Experience, and Full Site Editing
marktimemedia
0
520
My Coaching Mixtape
mlcsv
0
130
Getting science done with accelerated Python computing platforms
jacobtomlinson
2
210
Testing 201, or: Great Expectations
jmmastey
46
8.2k
Amusing Abliteration
ianozsvald
1
180
Leo the Paperboy
mayatellez
7
1.8k
GraphQLとの向き合い方2022年版
quramy
50
15k
Collaborative Software Design: How to facilitate domain modelling decisions
baasie
1
230
The Illustrated Children's Guide to Kubernetes
chrisshort
51
52k
Darren the Foodie - Storyboard
khoart
PRO
3
3.4k
Everyday Curiosity
cassininazir
0
210
Transcript
Agile + Lean Product Management Graham Siener Product Manager @
Pivotal Labs @gsiener #pmga
About Me (aka why should I listen?) Software Consulting Sustainability
in The Bahamas (?!) Cust Dev and PM at Startups PM coach at Pivotal Labs
What does PM mean? Discovering a product that is valuable
by listening to customers and collaborating with designers/developers.
What does PM mean? People Problems Priorities
People Know WHO you are building for
People Know WHAT they need
Problem A Product exists to SOLVE someone’s problem
Problem Focus FIRST on problem definition
Problem I need a faster site. Why? It’s too slow.
When do you notice? When I’m entering data. Where is the data coming from? Excel. I copy it. *Credit: Jess Martin
Problem Manually copying data into the website from Excel
Problem Don’t jump to SOLUTIONS too early
Priority You can’t build it all.
Priority WHEN to build is as important as WHAT.
Priority Sometimes that means saying NO to features.
Priority User behavior (usable) Business value (viable) Tech constraints (feasible)
Priority Create a shared metric for picking the most important
features.
Discovering a product that is valuable by listening to customers
and collaborating with designers/developers.
But How? Build Measure Learn (Repeat)
Customer Development Figure out what to build
Exercise: Inception
Lean Metrics Prove that you made your product better
Example: Planning Wizard
Example: Auto-Login Emails
Exercise: Interviews
Interview #1 A: Speaker B: Interviewer C: Observer
Interview #1 You’re trying to build an app that helps
you plan a vacation. Ask your speaker about a recent vacation.
Interview #1 A: Speaker B: Interviewer C: Observer
Interview #2 B: Speaker C: Interviewer A: Observer
Interview #2 You’re trying to build an app that helps
you decorate your house. Ask your speaker about a recent home improvement.
Interview #2 Interviewers: You can only ask clarifying questions after
the first statement. E.g., “Tell me more about X”
Interview #2 B: Speaker C: Interviewer A: Observer
Interview #3 C: Speaker A: Interviewer B: Observer
Interview #3 You’re trying to build an app that organizes
your todos. Ask your speaker about how they manage their task list.
Interview #3 Interviewers: You can’t say anything after the first
question. E.g., silence!
Interview #3 C: Speaker A: Interviewer B: Observer
Exercise: Interviews Wrap up
Thanks! @gsiener #pmga pivotallabs.com/author/gsiener