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
610
Communicating for Product Managers
kennethn
4
23k
How to work with engineers
kennethn
31
260k
Other Decks in Technology
See All in Technology
デジタルアイデンティティ人材育成推進ワーキンググループ 翻訳サブワーキンググループ 活動報告 / 20250114-OIDF-J-EduWG-TranslationSWG
oidfj
0
540
データ基盤におけるIaCの重要性とその運用
mtpooh
4
540
深層学習と3Dキャプチャ・3Dモデル生成(土木学会応用力学委員会 応用数理・AIセミナー)
pfn
PRO
0
460
[IBM TechXchange Dojo]Watson Discoveryとwatsonx.aiでRAGを実現!座学①
siyuanzh09
0
110
AWSサービスアップデート 2024/12 Part3
nrinetcom
PRO
0
140
re:Invent2024 KeynoteのAmazon Q Developer考察
yusukeshimizu
1
150
完全自律型AIエージェントとAgentic Workflow〜ワークフロー構築という現実解
pharma_x_tech
0
350
テストを書かないためのテスト/ Tests for not writing tests
sinsoku
1
170
「人物ごとのアルバム」の精度改善の軌跡/Improving accuracy of albums by person
mixi_engineers
PRO
1
110
Amazon Q Developerで.NET Frameworkプロジェクトをモダナイズしてみた
kenichirokimura
1
200
デジタルアイデンティティ技術 認可・ID連携・認証 応用 / 20250114-OIDF-J-EduWG-TechSWG
oidfj
2
690
.NET 最新アップデート ~ AI とクラウド時代のアプリモダナイゼーション
chack411
0
200
Featured
See All Featured
GraphQLとの向き合い方2022年版
quramy
44
13k
Facilitating Awesome Meetings
lara
51
6.2k
Typedesign – Prime Four
hannesfritz
40
2.5k
Writing Fast Ruby
sferik
628
61k
Mobile First: as difficult as doing things right
swwweet
222
9k
Bash Introduction
62gerente
610
210k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
44
9.4k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
120k
jQuery: Nuts, Bolts and Bling
dougneiner
62
7.6k
Faster Mobile Websites
deanohume
305
30k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
Scaling GitHub
holman
459
140k
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.