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
経験がないことを言い訳にしない、 AI時代の他領域への染み出し方
parayama0625
0
280
大規模組織にAIエージェントを迅速に導入するためのセキュリティの勘所 / AI agents for large-scale organizations
i35_267
6
350
P2P ではじめる WebRTC のつまづきどころ
tnoho
1
280
【CEDEC2025】大規模言語モデルを活用したゲーム内会話パートのスクリプト作成支援への取り組み
cygames
PRO
1
510
Gemini in Android Studio - Google I/O Bangkok '25
akexorcist
0
100
経理出身PdMがAIプロダクト開発を_ハンズオンで学んだ話.pdf
shunsukenarita
1
250
メモ整理が苦手な者による頑張らないObsidian活用術
optim
1
160
帳票構造化タスクにおけるLLMファインチューニングの性能評価
yosukeyoshida
1
180
Kiroから考える AIコーディングツールの潮流
s4yuba
2
520
反脆弱性(アンチフラジャイル)とデータ基盤構築
cuebic9bic
2
110
「AI駆動開発」のボトルネック『言語化』を効率化するには
taniiicom
1
230
[TechNight #91] Oracle Database 最新パフォーマンス分析手法
oracle4engineer
PRO
3
290
Featured
See All Featured
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
Art, The Web, and Tiny UX
lynnandtonic
301
21k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
161
15k
How to Ace a Technical Interview
jacobian
278
23k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
234
17k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
29
1.8k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
8
860
Agile that works and the tools we love
rasmusluckow
329
21k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
31
1.3k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
530
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
Build The Right Thing And Hit Your Dates
maggiecrowley
37
2.8k
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.