Fareed Mosavat on Becoming a Great PM
Fareed Mosavat — Lenny’s Podcast — ~2022
Key ideas
- PM mastery is earned through reps, not training. There is no pre-training that substitutes for working on real products with real customers. Courses and mentorship are a layer on top; the core acceleration comes from executing, iterating, and generalising lessons across projects.
- The PM learning loop has four stages. Execute → generalise (build transferable mental models) → communicate (share learnings to build organisational trust) → scale opportunities (move from known-problem/known-solution toward unknown-problem/unknown-solution work). Most PMs under-invest in the generalise and communicate steps.
- Sponsorship, not mentorship, unlocks career inflections. The step-change moments in Fareed’s career came when a senior leader gave him a materially larger problem to own — not from coaching. Creating the conditions for sponsorship requires doing visible work on high-priority problems and demonstrating curiosity two stack levels up and two stack levels down.
- The IC-to-manager canyon is crossed by shifting from doer to editor, and from constrained executor to resource marshaller. The manager death spiral — keeping the best work, blocking the team — is broken by trusting people, thinking in ROI of your own input, and treating resourcing as a leadership responsibility, not a given constraint.
- Four types of product work (feature, growth, product-market-fit expansion, scaling) require different thinking. Senior leaders must build a portfolio across all four rather than over-indexing on the one they know best.
Notes
- Fareed spent ~7 years at Pixar (credited on Finding Nemo, Cars, Wall-E, Up). Core lesson: what matters is the end experience and emotion, not technical fidelity.
- Framework for four types of product work developed jointly with Casey Winters, delivered through the Reforge product strategy programme.
- “Two stack levels up, two stack levels down” curiosity heuristic: understand your boss’s boss’s priorities, and understand the technical substrate below your immediate problem.