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
Leading cross-functional teams and the product ...
Search
Ken Norton
April 11, 2013
Technology
25
80k
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
620
Communicating for Product Managers
kennethn
4
23k
How to work with engineers
kennethn
31
260k
Other Decks in Technology
See All in Technology
Zero Data Loss Autonomous Recovery Service サービス概要
oracle4engineer
PRO
1
7.1k
それでもぼくらは貢献をつづけるのだ(たぶん) @FOSS4GLT会#002
furukawayasuto
1
250
研究開発部メンバーの働き⽅ / Sansan R&D Profile
sansan33
PRO
3
17k
“⾞が通れるほど⼤きな”セキュリティーホールを抑えながらログインしたい
taiseiue
0
130
GigaViewerにおけるMackerel APM導入の裏側
7474
0
200
Cloud Run を解剖して コンテナ監視を考える / Breaking Down Cloud Run to Rethink Container Monitoring
aoto
PRO
0
110
Oracle Database オプティマイザ・ヒントの活用
oracle4engineer
PRO
1
130
mnt_data_とは?ChatGPTコード実行環境を深堀りしてみた
icck
0
150
Houtou.pm #1
papix
0
240
AIエージェントデザインパターンの選び方
almondo_event
0
110
SmartHRの複数のチームにおけるMCPサーバーの活用事例と課題
yukisnow1823
2
990
Redmineの意外と知らない便利機能 (Redmine 6.0対応版)
vividtone
0
830
Featured
See All Featured
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.6k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
137
34k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
10
830
Automating Front-end Workflow
addyosmani
1370
200k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
6
650
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.3k
Building Applications with DynamoDB
mza
95
6.4k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
12k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
8
740
Mobile First: as difficult as doing things right
swwweet
223
9.6k
Building an army of robots
kneath
306
45k
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.