How to build trust and grow as a product leader | Fareed Mosavat (Reforge, Slack, Instacart, Pixar)
Executive Summary
Fareed Mosavat discusses how PMs build trust, generalize their learning and move into leadership. Selected coverage from a third-party speaker-labelled transcript focuses on the learning loop, sponsorship, curiosity and team leadership. Company stories are his accounts, not current policies. Advising and independent-career passages are omitted. Untimed editorial topics are not video chapters.
Key Takeaways
Start with execution on real problems
Mosavat puts execution at the start of the learning loop: deliver work for real customers and see what happens. Early PM assignments often have a known problem and known solution. Reading and courses can help, but they do not replace seeing a solution meet the world.
Turn experience into a reusable hypothesis
After shipping, ask which parts of the lesson apply elsewhere. His onboarding example contrasts a fast path with extra setup that may help a customer reach activation. Good friction is context-dependent, not a rule to lengthen every flow.
Communicate what the work taught you
Mosavat says doing the work is not enough: explain what happened, what you learned and what may generalize. That communication helps others assess readiness for bigger problems. It also gives the organization useful understanding beyond a single metric change.
Seek sponsorship through demonstrated trust
He describes leaders at Conduit Labs and Slack giving him larger problems after seeing his work and how he explained it. Sponsorship differs from advice: someone takes a chance on your ability. His career stories are personal accounts, not guaranteed promotion recipes.
Understand the system around your job
His curiosity model looks two levels up, two levels down and sideways. For a growth problem, that can include company priorities, implementation and neighboring teams. This wider view helps connect a local decision to how the business actually works.
Move from doing to improving other people’s work
Mosavat describes the leadership shift as going from doer to editor. The appropriate input depends on a person's experience and understanding: sometimes direction, sometimes coaching, sometimes space. Keeping every important task for yourself prevents the team from scaling.
Ask for the resources the problem needs
He contrasts an individual contributor making the most of available resources with a leader proposing what solving the problem requires. That can mean extra people or another team's work. Treat resource needs as part of the proposal, not only as an explanation after a missed outcome.
The Conversation Breakdown
Start with execution on real problems
⏱ Untimed topicMosavat puts execution at the start of the learning loop: deliver work for real customers and see what happens. Early PM assignments often have a known problem and known solution. Reading and courses can help, but they do not replace seeing a solution meet the world.
Turn experience into a reusable hypothesis
⏱ Untimed topicAfter shipping, ask which parts of the lesson apply elsewhere. His onboarding example contrasts a fast path with extra setup that may help a customer reach activation. Good friction is context-dependent, not a rule to lengthen every flow.
Communicate what the work taught you
⏱ Untimed topicMosavat says doing the work is not enough: explain what happened, what you learned and what may generalize. That communication helps others assess readiness for bigger problems. It also gives the organization useful understanding beyond a single metric change.
Seek sponsorship through demonstrated trust
⏱ Untimed topicHe describes leaders at Conduit Labs and Slack giving him larger problems after seeing his work and how he explained it. Sponsorship differs from advice: someone takes a chance on your ability. His career stories are personal accounts, not guaranteed promotion recipes.
Understand the system around your job
⏱ Untimed topicHis curiosity model looks two levels up, two levels down and sideways. For a growth problem, that can include company priorities, implementation and neighboring teams. This wider view helps connect a local decision to how the business actually works.
Move from doing to improving other people’s work
⏱ Untimed topicMosavat describes the leadership shift as going from doer to editor. The appropriate input depends on a person's experience and understanding: sometimes direction, sometimes coaching, sometimes space. Keeping every important task for yourself prevents the team from scaling.
Ask for the resources the problem needs
⏱ Untimed topicHe contrasts an individual contributor making the most of available resources with a leader proposing what solving the problem requires. That can mean extra people or another team's work. Treat resource needs as part of the proposal, not only as an explanation after a missed outcome.
Core Frameworks & Ideas
Career learning loop
Execute on a real problem, generalize the lesson, communicate it, earn a larger opportunity and execute again.
Two levels up, two levels down
Understand company context above your role, implementation below it and related work beside it.
Doer to editor
Improve the team's work with the right amount of direction, coaching or space instead of keeping all important execution.
Actionable Next Steps
- ✓After shipping, write one result and one hypothesis that may apply elsewhere.
- ✓Explain that lesson to a team that can use it.
- ✓Map the company goal, technical dependencies and neighboring teams around your project.
- ✓Propose the resources the problem needs instead of only accepting today’s allocation.
Notable Quotes
“You have to shift from doer to editor is the way I think about it.”
“You can create your luck by being good at communicating and solving hard problems.”
“So I call this going two stack levels up, two stack levels down in terms of your curiosity and what you understand, and also, knowing what’s to the left and what’s to the right.”
The One Thing to Remember
Ship, generalize, explain what you learned and earn the next larger problem.