Lenny’s Podcast148 min
Bob Baxley · Jun 12, 2025
Key learnings- Before joining a new company, check whether founders genuinely believe in design; design-led cultures are born that way, not…
- When changing cultures, keep your core values but re-express them in the new company's behaviors rather than carrying over old…
- Keep teams small when inventing something new; add people once the vision is clear, since more people slows creative convergence.
Lenny’s Podcast87 min
Christine Itwaru · Feb 16, 2023
Key learnings- Product ops can be understood two ways: as a set of systems that help a product team thrive, and as a dedicated person or group…
- Common product ops responsibilities include voice-of-customer synthesis, tooling and data integrations, content and education…
- Frame the role to PMs as protecting their time for customer conversations, which Christine says PMs should never give up, rather…
Lenny’s Podcast113 min
Katie Dill · Oct 15, 2023
Key learnings- Beauty and functionality are not opposites; beauty enhances usability, approachability and trust, and users read attention to…
- When joining a team, come in listening and build trust first; Katie's early team intervention taught her that people won't follow…
- Quality is a group effort: align engineering, product and design on shared standards, and use an editor or architect to ensure…
Lenny’s Podcast98 min
Melissa Tan · Jun 18, 2023
Key learnings- Hire first-principles thinkers who are humble and collaborative, since that combination drove much of Dropbox's innovation…
- Start go-to-market and monetization planning early rather than treating growth as a layer added on top of the product later.
- Introduce a PLG motion when the product is intuitive to onboard onto and has a viral component; move toward enterprise sales once…
Lenny’s Podcast92 min
Jeremy Henrickson · Jun 4, 2023
Key learnings- Keep small teams with clear, narrow missions, and break large problems into pieces that small groups can own end to end to…
- Build a shared platform with a single system of record so product teams spend less energy on decisions and integrations, letting…
- Dive into the trenches yourself: leaders learn where the real challenges are only by working through the hardest details with the…
Lenny’s Podcast108 min
Kim Scott · Dec 10, 2023
Key learnings- Radical candor means caring personally while challenging directly; missing the first yields obnoxious aggression, missing the…
- Don't ask 'Do you have any feedback for me?'; instead ask a specific question like 'What could I do or stop doing that would make…
- Give feedback immediately, in person or by phone rather than text or Slack, and use context, observation, result, next step…
Lenny’s Podcast87 min
Ray Cao · Mar 7, 2024
Key learnings- Succeeding in global markets requires sending people in, hiring local talent, and understanding local culture, since the…
- Adopt a 'context, not control' mindset: give teams full information and ownership, then let them proactively think and reactively…
- Hire for curiosity, discipline, and prioritization skill; Cao notes that hiring quality over speed is a mistake he made early on.
Lenny’s Podcast100 min
Dhanji R. Prasanna · Oct 26, 2025
Key learnings- Track AI impact with self-reported time savings plus validation metrics such as PR throughput and feature delivery, which Block…
- Expect the current AI value baseline to keep rising; adopt tools continuously and re-evaluate where they add value as…
- Non-technical staff building their own small internal tools with agents can compress weeks of waiting on engineering queues into…
Lenny’s Podcast104 min
Lane Shackleton · Oct 1, 2023
Key learnings- Treat the core job of product work as turning ambiguity into clarity, and build repeatable systems rather than chasing one-off…
- Build default-on customer contact systems, such as a standing weekly slot with customers, instead of quarterly OKRs to talk to…
- Ask career questions about how many 'oh shit' moments someone has had recently, a sharper signal of growth than asking whether…
Lenny’s Podcast83 min
Ivan Zhao · Mar 6, 2025
Key learnings- Hide a grand vision inside a product people already want: Notion's 'sugar-coated broccoli' approach meant shipping familiar…
- Test whether your early adoption comes from real users, not just from your own taste: Ivan warns that building too much for…
- Don't be afraid to reset the codebase when the foundation is wrong, and favor better abstractions, since a small core can…
Lenny’s Podcast84 min
Adam Mosseri · Jul 9, 2026
Key learnings- Small pods of four to six generalist engineers plus a generalist 'product staff' role can move faster than large specialist…
- As building gets cheaper, spend more time deciding what to build; taste and judgment about strategy become the scarce skills, per…
- Keep investing in tomorrow's senior talent in each function, not just today's, or the organization will regret it in a few years.
Lenny’s Podcast101 min
Camille Fournier · Sep 15, 2024
Key learnings- Share credit generously with engineers and give them room to present their own technical contributions rather than taking the…
- Show genuine interest in engineering details, even if you don't need to master them, since dismissing them signals a lack of…
- Avoid acting as a go-between for engineers and stakeholders; if you keep relaying questions back and forth, connect the people…
Lenny’s Podcast103 min
Gustav Söderström · May 21, 2023
Key learnings- Expect the internet's next shift from recommendation to generation to require rethinking products and business models, much as…
- Design UIs to match your model's real accuracy: if predictions are right only one in four or five times, show several options at…
- Treat generative AI as a distinct paradigm rather than more of the same machine learning, and ask what experience couldn't exist…
Lenny’s Podcast106 min
Daniel Lereya · Apr 27, 2025
Key learnings- Treat a competitor's rapid shipping as a gift that proves a goal is possible, then set an ambitious target that forces you to…
- Measure product managers by the impact they validate for customers, not by features shipped; define the problem, the opportunity…
- Ask each quarter what your product will do differently for customers a quarter from now, and check whether you can name your…
Lenny’s Podcast95 min
Nilan Peiris · Sep 24, 2023
Key learnings- Measure word of mouth by simply asking new customers how they heard about you and overlaying that on attribution and…
- Use NPS as a proxy for viral potential: moving promoters up the scale roughly doubles how many people each customer refers, so…
- Read the verbatim NPS comments company-wide; Wise found customers repeatedly asked for lower prices, faster transfers, and easier…
Lenny’s Podcast160 min
Evan LaPointe · Aug 11, 2024
Key learnings- Send questions to the right mental mode: most people over-rely on fast, recall-based thinking, so deliberately route problems to…
- Start meetings with priming, stating the context, shared goal, and guiding principles before jumping into decisions; mismatched…
- Know your own personality and openness level, then be vulnerable with your team about how you naturally react to abstract vision…
Lenny’s Podcast78 min
Keith Yandell · Feb 9, 2023
Key learnings- Hire people better than yourself, then get out of the way; the most valuable managers slowly step back as their team members…
- Write a 'How to work with me' document that states your expectations, known growth areas, and commitments to your team; it helps…
- Help people find their next job, even outside the company; it surfaces retention risks early, lets you plan backfills, and builds…
Lenny’s Podcast73 min
Asha Sharma · Aug 28, 2025
Key learnings- Treat AI products as living systems: build the loop of collecting usage signals, defining rewards, A/B testing, and fine-tuning…
- Invest in post-training and fine-tuning on your own data, not just off-the-shelf models; once models are large, adapting them to…
- Watch for a shift from GUIs toward composable, code-native interfaces, since text streams and composability connect better with…
Lenny’s Podcast126 min
Alex Komoroske · Oct 3, 2024
Key learnings- Favor gardening over pure building: look for things that can grow on their own with ecosystem or network-effect dynamics, invest…
- Treat LLMs as squishy, imperfect 'magical duct tape' and design products that tolerate occasional failures rather than assuming…
- Build taste by finding a distinctive perspective that resonates with people, since cheap content generation makes differentiation…
Lenny’s Podcast68 min
Brandon Chu · Jun 27, 2022
Key learnings- Treat domain expertise as table stakes; to reach the highest levels, lean into founder skills like storytelling, motivating…
- Think of the PM role as helping teams ship the right thing at the right time in the right way, acting as a servant leader rather…
- Set annual directional plans but expect them to change; avoid sunk-cost fallacy and be willing to throw away work when the world…
Lenny’s Podcast133 min
Keith Coleman & Jay Baxter · Feb 27, 2025
Key learnings- Surface notes only when raters who normally disagree both find them helpful; seeking cross-polarized agreement is what keeps…
- Open participation to everyone with basic verification and random selection, rather than curating contributors, so the system…
- Set the quality bar conservatively: showing a bad note damages trust far more than withholding a good one, so the team accepts…
Lenny’s Podcast107 min
Luc Levesque · Jun 15, 2023
Key learnings- Focus relentlessly on impact over activity: measure outcomes against the north-star metric rather than hours worked or work…
- Hire the top 1% by looking for repeated 'signs of excellence' in a candidate's history, such as multiple standout achievements…
- Recruit with the whole executive team and involve the candidate's spouse or family, since changing companies is a family…
Lenny’s Podcast87 min
Brian Tolkin · Aug 4, 2024
Key learnings- Treat operations and product as complementary engines rather than rivals; a company runs best when both feed each other with…
- Start with manual, human-in-the-loop processes to learn, then automate with technology once volume makes manual work break…
- Be explicit about where scarce engineering effort goes, focusing on the core leverage point (like dispatch and pricing early on)…
Lenny’s Podcast129 min
Caitlin Kalinowski · May 17, 2026
Key learnings- Hardware can only be 'compiled' a handful of times, so teams must be more conservative, run reliability checks early, and solve…
- Define clear, written goals (cost, weight, resolution) before starting and resist changing them, since hardware is far less…
- Design the riskiest or hardest-to-physically-build parts first rather than starting with the components you already know how to…