Today is my last day as a PM at Facebook/Meta! ππ½
While bittersweet, Iβm grateful that I learned a ton from from some of the best PMs in the world.
Here are the most consequential ideas I learned about leading product teams:
1/ Ask more from your team, not less πͺ
Giving low-skill tasks to high-skilled teammates is a waste of their talents.
Use their full skillset by giving them bigger challenges.
This lets your team have more impact and increases the your own leverage.
Example:
2/ Let fires burn π₯
Great PMs are comfortable with persistent fires. They can't solve everything.
Instead, they find higher-leverage ways of tackling more than one problem at a time.
Here's how Brian Chesky does it:
Brain Cheskyβs High Leverage To-Do List
1. Make an exhaustive list of tasks
2. Group them by their root cause
3. Ask what one action can take care of these 3? These 5?
4. Do it again and again.
This brings 20 to-dos to 3-5 high leverage actions. Think calling the fire dept:
3/ Create the truth π
When you first join a team, write a "State of the Union".
This lets you:
1/ create context for their team
2/ show that they understand the team's problems
3/ build credibility
Here's a template modeled after a SOTU I wrote:
4/ Execute perfectly π―
Imagine starting a diet and cheating mid-way.
At the end of the diet, do you know if the diet/strategy worked? No.
Key idea: you can only debug or evaluate strategies if they are executed well.
Here's how to do that:
5/ Always make decisions with objective criteria β
This lets you show their thought process and remain objective.
Here are three examples of varying fidelity (note: fidelity varies with complexity of the decision):
6/ Create scope π
PM seniority is tied to the size, ambiguity and impact of your scope.
Great PMs create meaningful scope for their teams. You do this by:
1/ building capacity
2/ finding new areas
3/ capturing with a plan
Here's how to do this:
7/ Meta-Execute π
Often, itβs in the best interest of teams for the PM to step back from execution to:
- define long-term plans
- make sure youβre working on the right things
To do this, you need to meta-execute.
This is a big idea, I unpack it here:
8/ Your team should decide what they build π£
If you're worried they'll chose the wrong things, the PM hasn't given them
1/ the right context
2/ the right prioritization framework
3/ an ownership culture
Here's how to create "bottoms-up" roadmaps:
My new team at Facebook has a great process for creating roadmaps.
Here is our six-week timeline:
Wk 1: Socialize Your Charter
Wk 2: Understand Share-outs
Wk 3: Ideation
Wk 4: Longlist to Shortlist
Wk 5: Prioritization and Goals
Wk 6: Consolidate
Let's break it down
To recap:
πͺ Ask more of yout team
π₯ Let fires burn
π Create the truth
π― Execute perfectly
β Decide with criteria
π Create scope
π Meta-Execute
π£ Team decides what to build
I documented more lessons I observed building products here, check em out:
For all the flak that FB gets, I'm proud & lucky to have worked with some really smart people.
This job changed my trajectory and taught me so much.
I'm going to enjoy the holidays with my family and jump into a new role in the new year. Stay tuned. π