Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Leading cross-functional teams and the product manager
Ken Norton
April 11, 2013
Technology
26
78k
Leading cross-functional teams and the product manager
What I wish I'd known before I became a PM.
More of my writing and speaking at
Bring the Donuts
.
Ken Norton
April 11, 2013
Tweet
Share
More Decks by Ken Norton
See All by Ken Norton
Google Tech Hubs: OKRs and Product Management
kennethn
4
550
Communicating for Product Managers
kennethn
4
23k
How to work with engineers
kennethn
31
250k
Other Decks in Technology
See All in Technology
ソフトウェアライセンス 2022 / Software License 2022
cybozuinsideout
PRO
1
1.1k
複数のスクラムチームをサポートするエンジニアリングマネジメントの話
okeicalm
0
1.1k
Power AutomateでのAdaptive Cards-基本編
miyakemito
1
310
誰が正解を知っているのか / Who knows the right answer
takaking22
1
240
紙にまつわる苦しみを機能化してきた カミナシの歴史
kaminashi
0
1.2k
Meet passkeys
satotakeshi
1
120
Data in Google I/O - IO Extended GDG Seoul
kennethanceyer
0
150
Autonomous Database Cloud 技術詳細 / adb-s_technical_detail_jp
oracle4engineer
PRO
10
18k
Citizen 개발기
outsider
0
270
Retca Cloud
bau
0
510
How to start with DDD when you have a Monolith
javujavichi
0
310
Target SDK Versionを上げない Notification runtime permission対応
napplecomputer
0
140
Featured
See All Featured
It's Worth the Effort
3n
172
25k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
315
19k
Building Better People: How to give real-time feedback that sticks.
wjessup
344
17k
Teambox: Starting and Learning
jrom
123
7.7k
StorybookのUI Testing Handbookを読んだ
zakiyama
5
2.2k
Navigating Team Friction
lara
175
11k
Practical Orchestrator
shlominoach
178
8.6k
Large-scale JavaScript Application Architecture
addyosmani
499
110k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
15
940
Clear Off the Table
cherdarchuk
79
280k
4 Signs Your Business is Dying
shpigford
169
20k
Designing for Performance
lara
597
63k
Transcript
Leading Cross-Functional Teams Ken Norton VP, Products JotSpot, Inc.
What am I going to talk about • A disjointed
set of learnings • What I wish I’d known before • (There will only be two formulas)
Here’s the good news.
You have the resources.
You are completely accountable.
You are ready to go.
But…
You have no authority.
And everyone is skeptical.
Why?
Without sales, nobody would sell. Without engineering, nobody would build.
Without support, customers would riot.
Without product managers?
Life would be just fine.
(For a while.)
Organizational structure: What you are working with
What you’ve probably learned:
Functional organization. PM
Weak matrix. PM
Strong matrix. PM
What you actually find.
The real world. PM
The reality. • You will not be closely supervised. •
Little to no authority will be handed to you. • You will not have direct managerial oversight for the people who work on your stuff. • You will be highly accountable for success (or lack thereof).
The team: Who you are working with
7 ± 2 Ideal team size.
7 ± 2 (That’s the first formula).
Always trust your instincts.
If you don’t have the right team, get it.
There is nothing more important to invest “political capital” on.
Communicating: How you are working with who you are working
with
There are only three things you need to remember.
1. “Never tell people how to do things. Tell them
what to do and they will surprise you with their ingenuity.” (General George Patton)
2. Communicate to different people in their own language.
3. Represent the points of view of the people not
in the room.
How to get respect from engineers.
Clear obstacles. Always take the blame. Ask smart questions. Explain
the “why.” Empathize. Bring the donuts.
How to get respect from sales.
Know their number. Get on the phone with customers. Make
promises so they don’t have to. Help them be creative. Bring the donuts.
How to get respect from executives.
Have a vision. Be patient. Know your competition. Make your
commitments. Bring the donuts.
How to get respect from customers.
Understand what they want. Call them out of the blue.
Keep your promises. Take the blame. Bring the donuts.
A. B. S.
Always Be Shipping.
Nothing helps a team become efficient more than a steady
release tempo.
Agile development.
Can be extremely effective.
But requires hard work and experience.
If you do nothing else…
Have a fifteen minute daily meeting.
Ask your team three questions: • What have you completed
since our last meeting? • What will you have done by tomorrow’s meeting? • What’s standing in your way and how can I help?
Estimating work.
Product Manager: “When can you get this done? Today?”
Engineer: “Well, I think it needs more time.”
Product Manager: “We need it ASAP. What about tomorrow by
end of day?”
Engineer: “Uh, OK.”
The right question: “What needs to happen for you to
finish, and what can I do to help?”
Rule of thumb for estimates.
Likely estimate (L): “How long do you think it will
take?”
Pessimistic estimate (P): “OK, but what’s the longest it could
take, accounting for unforeseen roadblocks?”
Optimistic estimate (O): “What’s the least amount of time required
if everything goes well?”
O + (L x 4) + P 6 What you
plan.
Another rule of thumb for estimates.
Never assume more than 5 hours of progress per developer
per day.