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 Podcast77 min
Nikita Miller · Apr 6, 2023
Key learnings- Have product, design, engineering and data leaders each write expectations for their own role and for each other, then review…
- Revisit roles and responsibilities every few months, usually triggered by tension or missed work, with a quick retro when…
- Watch execution velocity and decision-making speed closely; outcomes matter, but shipping output quickly is the indicator that…
Lenny’s Podcast98 min
Annie Duke · May 2, 2024
Key learnings- Make implicit judgments explicit (e.g., a hiring rubric) before using intuition; Duke cites Kahneman's work lifting hiring hit…
- Gather opinions independently and asynchronously before meetings, then use the meeting only for discussion, focusing on where…
- Reserve meetings for discussion; discovery of views should happen beforehand and decisions should be made by an accountable…
Lenny’s Podcast102 min
Claire Hughes Johnson · Mar 5, 2023
Key learnings- Start with self-awareness: seek feedback on your motivators, strengths, and blind spots, and share them with your team, since…
- Introduce job levels and career ladders earlier than feels necessary; waiting until a company is large makes the change far more…
- Treat company-building infrastructure as essential, not optional: product-market fit alone won't scale, and weak structures and…
Lenny’s Podcast69 min
Vijay · Jan 26, 2023
Key learnings- Protect your core product: rather than moving people from the core to new ventures, invest the core's profits into new bets…
- Be cautious adding adjacent products in new categories; bolt-on products that are only mid-tier in crowded categories rarely move…
- When a product is losing customers to competitors, a focused 'speed' phase working directly from ranked churn reasons can close…
Lenny’s Podcast93 min
Mike Krieger · Jun 5, 2025
Key learnings- Use AI as an independent strategy critic: ask it to be brutal or to challenge your thinking, since default prompts tend to…
- As AI writes most code, bottlenecks shift upstream to deciding what to build and aligning people, and downstream to merge queues…
- Give teams a minimum viable strategy so people feel empowered to build and explore at the edge of model capabilities without…
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 Podcast85 min
Roger Martin · Jul 25, 2024
Key learnings- Strategy is an integrated set of choices that compels desired customer action, since customers are the one thing a company cannot…
- Work through the five cascade questions together: winning aspiration, where to play, how to win, required capabilities, and…
- Winning requires being either differentiated or lowest cost; without one of those, competitors can keep pushing you back step by…
Lenny’s Podcast128 min
Dan Shipper · Jul 17, 2025
Key learnings- Non-programmers can use Claude Code-style command-line agents with local files to process large text sets, like meeting notes or…
- Hire or assign someone to an AI operations role who continuously turns repetitive team tasks into prompts and workflows, and make…
- Apply 'compounding engineering': spend a bit of effort turning each recurring task (like writing PRDs) into a reusable prompt or…
Substack podcastJan 3, 2026
Jan 3, 2026
Key learnings- Treat time management as an ongoing experiment rather than a fixed system, testing methods and keeping what actually works for…
- Advanced time management ideas go beyond to-do lists to focus on how you allocate attention across competing priorities.
- Protect blocks of deep, uninterrupted work time, since product work is often fragmented by meetings and reactive requests.
Lenny’s Podcast96 min
Ronny Kohavi · Jul 27, 2023
Key learnings- Test every code change, since even small bug fixes or tiny UI tweaks can have surprising, large impact on key metrics.
- Expect most ideas to fail: roughly two-thirds to over 90% of experiments in his experience did not move the target metric, so…
- Allocate a portion of experiments to high-risk, high-reward bets, accepting that about 80% will fail, while keeping most work…
Lenny’s Podcast94 min
Jiaona Zhang · Jul 2, 2023
Key learnings- New PMs often jump to solutions; start by understanding user problems and whether a real opportunity exists before deciding what…
- A PM has little formal authority and must lead through influence, so editing and synthesizing opportunities matters more than…
- Check unit economics early; magical thinking that a business will work at scale is a common trap, as the Airbnb Plus experience…
Lenny’s Podcast110 min
Gaurav Misra · Mar 27, 2025
Key learnings- Aim for every engineer to ship a marketable product each week, sliced down to an MVP so the team can gather real user feedback…
- When time is tight, cut scope rather than quality: repeatedly remove elements from a feature until removing anything more would…
- Treat technical debt as financial leverage for startups, but track it like interest: once debt consumes most engineering time…
Lenny’s Podcast128 min
Nick Turley · Aug 9, 2025
Key learnings- Ship early to learn what people actually want; with AI, the valuable behaviors are emergent, so you won't know what to polish…
- Treat the model itself as a product: iterate on it using real user use cases, personality/vibe checks, and new capabilities like…
- Set the team's pace deliberately by asking whether work is 'maximally accelerated', separating fast product iteration from…
Lenny’s Podcast99 min
Will Larson · Jan 7, 2024
Key learnings- Treat engineers as capable adults by giving them hard problems and accountability, which lets them grow into senior leadership…
- Build simple stock-and-flow models of processes like hiring pipelines, then compare them against historical data to find where…
- Write your engineering strategy down, even imperfectly; an unwritten strategy cannot be debugged or improved, and every function…
Lenny’s Podcast100 min
Zevi Arnovitz · Jan 18, 2026
Key learnings- Start slowly with a ChatGPT project acting as a skeptical 'CTO' before moving to coding tools, gradually easing into code to…
- Capture ideas quickly as Linear issues using reusable slash commands, so you can pick them up later with context already gathered.
- Separate the workflow into explore, plan, execute, review, and document phases, and have the AI ask clarifying questions before…
Lenny’s Podcast84 min
Sachin Monga · Oct 30, 2022
Key learnings- Early on, act more as a facilitator than a decision maker: keep the CEO and teams aligned on problems and vision through a…
- Organize product teams around timeless customer problems (writers, readers, growth) rather than product surfaces, so structure…
- Expect any process or planning system to become obsolete as the company grows; aim to keep getting better each week, month, and…
Lenny’s Podcast148 min
Amol Avasare · Apr 5, 2026
Key learnings- Expect most growth time to go to 'success disasters' once growth is rapid; firefighting breaking systems matters as much as new…
- In AI-first products, skew the growth portfolio toward larger swings, since future product value could be orders of magnitude…
- Treat activation as a top lever in AI products: identify user traits that predict which feature fits them, then guide them there.
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 Podcast116 min
Noah Weiss · Jul 23, 2023
Key learnings- Distill company-level product taste into a shared set of principles so teams can self-evaluate and founders are not the sole…
- Involve founders early for strategy, goals and anti-goals, then again at the end to taste the product, and keep iterating in…
- Run complaint storms by critiquing adjacent products' customer journeys first, which builds calibration and fresh empathy before…
Lenny’s Podcast100 min
Richard Rumelt · Jan 21, 2024
Key learnings- Treat strategy as a response to one or two real challenges, not a list of ambitions, priorities, or aspirations; Rumelt suggests…
- A solid strategy has three parts: a diagnosis of the situation, a guiding policy for dealing with it, and coherent actions that…
- Test your strategy for bad signs: goals dressed up as strategy, fluffy jargon, missing diagnosis, and actions that contradict one…
Lenny’s Podcast105 min
Nikita Bier · Aug 25, 2024
Key learnings- Look for latent demand: when users go through a distorted workaround to get a value, that signal can reveal a product idea with…
- Target teens for social and communication products, since invitations per user drop roughly 20% per year from age 13 to 18, and…
- Build a reproducible testing process: Bier argues that the number of shots at bat and how reliably you test ideas matters more…
Lenny’s Podcast193 min
Eric Ries · Oct 29, 2023
Key learnings- Treat a startup as an experiment: state the hypothesis, identify the leap-of-faith assumptions, and design the cheapest test that…
- An MVP is defined by the hypothesis being tested, not by a fixed level of stripped-down quality; it can be a brochure, a…
- Quality is defined by the customer, so teams that don't know their customer can't really know what a quality bar means; get early…
Lenny’s Podcast123 min
Matt MacInnis · Dec 28, 2025
Key learnings- Extraordinary outcomes require extraordinary effort; if people feel comfortable at work, something has gone wrong, and leaders…
- Deliberately understaff projects, since overstaffing invites politics and pulls people onto low-priority work before it is clear…
- Withholding feedback is selfish because it optimizes for your own comfort; escalate issues in public and give direct feedback…