$30 off During Our Annual Pro Sale. View Details »
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
1
99
An Introduction to Product Management
Graham Siener
May 23, 2013
Tweet
Share
More Decks by Graham Siener
See All by Graham Siener
How technical should a PM be?
gsiener
0
190
Interviewing Exercise
gsiener
0
110
Data-driven Product Management
gsiener
4
210
Featured
See All Featured
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
17k
Stop Working from a Prison Cell
hatefulcrawdad
273
21k
Building Applications with DynamoDB
mza
96
6.8k
Git: the NoSQL Database
bkeepers
PRO
432
66k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.3k
4 Signs Your Business is Dying
shpigford
186
22k
Testing 201, or: Great Expectations
jmmastey
46
7.8k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
12
970
A better future with KSS
kneath
240
18k
Rebuilding a faster, lazier Slack
samanthasiow
84
9.3k
Leading Effective Engineering Teams in the AI Era
addyosmani
8
1.3k
Designing Experiences People Love
moore
143
24k
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