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
200
Interviewing Exercise
gsiener
0
120
Data-driven Product Management
gsiener
4
220
Featured
See All Featured
Are puppies a ranking factor?
jonoalderson
1
3.3k
AI: The stuff that nobody shows you
jnunemaker
PRO
5
530
My Coaching Mixtape
mlcsv
0
97
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
17k
What's in a price? How to price your products and services
michaelherold
247
13k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
249
1.3M
Optimizing for Happiness
mojombo
378
71k
The Anti-SEO Checklist Checklist. Pubcon Cyber Week
ryanjones
0
110
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
37
6.3k
Speed Design
sergeychernyshev
33
1.6k
Chasing Engaging Ingredients in Design
codingconduct
0
170
Between Models and Reality
mayunak
3
260
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