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で小説を書くためにプロンプトの制約や原則について学ぶ / prompt-engineering-for-ai-fiction
nwiizo
4
3.4k
より良いプロダクトの開発を目指して - 情報を中心としたプロダクト開発 #phpcon #phpcon2025
bengo4com
1
3.2k
Node-REDのFunctionノードでMCPサーバーの実装を試してみた / Node-RED × MCP 勉強会 vol.1
you
PRO
0
130
モバイル界のMCPを考える
naoto33
0
350
Tech-Verse 2025 Keynote
lycorptech_jp
PRO
0
1.3k
なぜ私はいま、ここにいるのか? #もがく中堅デザイナー #プロダクトデザイナー
bengo4com
0
1.3k
mrubyと micro-ROSが繋ぐロボットの世界
kishima
2
380
AWS Organizations 新機能!マルチパーティ承認の紹介
yhana
1
220
OpenHands🤲にContributeしてみた
kotauchisunsun
1
500
生成AI時代 文字コードを学ぶ意義を見出せるか?
hrsued
1
730
Tech-Verse 2025 Global CTO Session
lycorptech_jp
PRO
0
1.2k
OPENLOGI Company Profile
hr01
0
67k
Featured
See All Featured
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
10
940
A designer walks into a library…
pauljervisheath
207
24k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
138
34k
Visualization
eitanlees
146
16k
Testing 201, or: Great Expectations
jmmastey
42
7.6k
RailsConf 2023
tenderlove
30
1.1k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Building a Modern Day E-commerce SEO Strategy
aleyda
42
7.4k
The Straight Up "How To Draw Better" Workshop
denniskardys
234
140k
Music & Morning Musume
bryan
46
6.6k
Large-scale JavaScript Application Architecture
addyosmani
512
110k
Typedesign – Prime Four
hannesfritz
42
2.7k
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.