Lenny’s Podcast68 min
Marty Cagan · Aug 21, 2022
Key learnings- Empowered product teams are handed problems to solve with measurable outcomes, not prioritized feature lists to ship; celebrate…
- Product managers are equally responsible for the 'how' - ensuring a solution is valuable, usable, feasible, and viable - not just…
- Limit problem validation time when the founder already understands the problem; spend most effort on solution discovery through…
Lenny’s Podcast108 min
Cat Wu · Apr 23, 2026
Key learnings- Shorten the path from idea to user: AI-era timelines have shrunk from six months to days or a week, so PMs should focus on…
- Ship features as clearly labeled research previews to lower the commitment of launching and get fast user feedback that can be…
- Set a clear, specific goal for who the key user is and what success means, which rules out many approaches and speeds decisions.
Lenny’s Podcast95 min
Shreyas Doshi · Oct 31, 2024
Key learnings- Run a pre-mortem before launches by imagining the project has already failed, then surfacing tigers, paper tigers and elephants…
- Classify tasks as leverage, neutral or overhead; spend extra effort only on leverage tasks, and do less polish on neutral and…
- Beat procrastination on high-leverage work by doing a couple days of low-stakes placebo tasks first, then working from a…
Lenny’s Podcast78 min
Janna Bastow · Oct 16, 2022
Key learnings- Treat a roadmap as a prototype for your strategy: its value lies in the roadmapping process of sharing and testing assumptions…
- Replace timeline-based roadmaps with Now, Next, Later buckets so that not every item implies a due date, since uncertainty grows…
- Reserve firm dates for truly fixed constraints such as regulatory deadlines or seasonal rushes, and plan extra buffer and soft…
Lenny’s Podcast118 min
Karri Saarinen · Oct 8, 2023
Key learnings- Ship features early to a small set of users or internal teammates and polish only at general release, rather than perfecting…
- Co-create early features with one or a few large customers to clarify how complex workflows should actually work.
- Give project teams ownership of their features; craft often emerges when engineers and designers discover better interaction…
Lenny’s Podcast109 min
Bill Carr · Nov 2, 2023
Key learnings- Start product decisions from the customer's real problem and work backwards to the required solution, rather than starting from…
- Avoid compound metrics that blend several numbers into one index; track each important metric individually so you can see which…
- Organize teams around a single-threaded leader who owns the people, resources and roadmap for a durable area, rather than…
Lenny’s Podcast121 min
Naomi Gleit · Oct 27, 2024
Key learnings- Keep one canonical doc per project that links to all other docs, listing workstreams, single-threaded owners, processes…
- Pursue a dream company or role persistently, even by volunteering informally in the role you want until the formal job becomes a…
- Pick a clear activation or retention milestone so the whole team optimizes toward one shared goal, even if the exact threshold is…
Lenny’s Podcast99 min
Christina Wodtke · Mar 16, 2023
Key learnings- OKRs amplify a company that already has strategy, empowered teams and psychological safety; they reveal dysfunction rather than…
- Use a weekly question as the core unit: what am I doing this week to move closer to our strategic outcomes?
- Keep strategy as a half-built plan across quarters and set the detailed key results only for the current quarter.
Lenny’s Podcast121 min
David Singleton · May 4, 2023
Key learnings- Co-create new products with a small, carefully chosen group of early users, sharing product regularly and expanding only once…
- Engineers at Stripe are expected to act like PMs, so hiring and developing product-minded engineers can reduce the need for early…
- Use friction logging: pick a specific user persona, walk through the product end-to-end, and note every point of friction to find…
Lenny’s Podcast70 min
Paige Costello · Jul 9, 2023
Key learnings- Plan on a rolling 12-month horizon, refreshed every six months, so the immediate half has higher confidence and the business…
- Structure planning in nested altitudes (company, pillar, area, team) with metrics at each level so every team knows the outcome…
- Use a broad-then-narrow process for each problem: choose the customer, then the problem, then the solution, and pick success…
Lenny’s Podcast122 min
Nir Eyal · Dec 29, 2023
Key learnings- Distraction is mostly driven by internal discomfort such as boredom, anxiety, or fatigue rather than external pings, so identify…
- Use the 10-minute rule: when tempted to drift, set a 10-minute timer, return to the task or ride out the urge, and treat it as…
- Replace to-do lists with a calendar: time-box traction activities (work, family, health, rest) in advance so anything outside…
Lenny’s Podcast150 min
Jason Fried · Dec 17, 2023
Key learnings- Software businesses have very low physical costs, so bootstrapping can be practical; treat cash flow and profit as the core skill…
- Venture-scale is an outlier path; most viable businesses sit in the large space between small and unicorn, so consider whether…
- Keep teams small and products simple; Fried argues constraints and a single product offering prevent the complexity that comes…
Lenny’s Podcast133 min
Ryan Singer · Mar 30, 2025
Key learnings- Start from a fixed time budget (appetite) and shape a solution that fits it, rather than estimating a large idea and hoping it…
- Hold shaping sessions where product, design, and a senior engineer work together to sketch the idea and surface technical…
- Aim for a shaped idea describable in under about ten moving pieces; if it takes more, it likely isn't shaped well enough.
Lenny’s Podcast85 min
Ian McAllister · Nov 20, 2022
Key learnings- New PMs should focus first on communicating, prioritizing, and executing, since other skills grow in importance with seniority.
- Answer first and then explain; when asked a 'when' question, give a date, and grade yourself after feedback to improve…
- Prioritization is a core PM skill across themes, projects, sequencing, scope, and personal time, and it strongly multiplies…
Lenny’s Podcast112 min
Nan Yu · Jan 30, 2025
Key learnings- Speed and quality aren't a trade-off; true craftspeople move fast because they are competent, so aim to get a workable version…
- Treat the first version as a best guess to test key assumptions, not a polished deliverable, and release it to internal users…
- Refuse feature requests that add customization for middle-manager reporting at the expense of individual contributors' workflows…
Lenny’s Podcast112 min
Melissa Perri · Jul 28, 2022
Key learnings- The product owner role came from Scrum as a way to help developers prioritize work, not from product management, so it often…
- Frameworks like SAFe are heavily marketed and often adopted rigidly; Perri has seen most teams that found success end up ripping…
- Teams that already talk to customers and iterate quickly may not need a framework at all; the principle of shipping value and…
Lenny’s Podcast119 min
Matt LeMay · Aug 14, 2025
Key learnings- Ask whether you would fully fund your own team if you were the CEO; if you can't answer confidently, that signals a risk worth…
- Set team goals no more than one step away from company goals, so leadership immediately understands how your work contributes to…
- Keep impact first at every step, from OKRs and strategy to epics and daily backlog, rather than letting goals get cascaded into…
Lenny’s Podcast124 min
Jake Knapp + John Zeratsky · Feb 11, 2024
Key learnings- Start each day by choosing a highlight: imagine the day is over and decide what you'd want to call the highlight, then protect a…
- Don't rely on willpower; change your environment by logging out of apps, deleting infinity-pool apps from your phone, or adding…
- Use your calendar as a design tool by blocking focus time, meals, exercise, and personal priorities, then adjust the template…
Lenny’s Podcast150 min
Farhan Thawar · Dec 19, 2024
Key learnings- Choose the harder path when options are close: even if it fails, you gain skills and work with stronger people, whereas the easy…
- Write down a personal framework of what you care about in a job, and use it to filter opportunities and decide when to leave a…
- Build intensity by producing more output per minute rather than adding hours; a focused hour with strong people can outpace a…
Lenny’s Podcast109 min
Ami Vora · Jun 23, 2024
Key learnings- Sublimate your ego: prioritize reaching the right outcome over being right, since others often hold information you lack.
- Respond to disagreement with curiosity by asking the other person to explain their reasoning, and pause before reacting to avoid…
- Keep product reviews short, bring a clear recommendation, and use them to calibrate on reusable principles rather than to approve…
Lenny’s Podcast116 min
Kevin Weil · Apr 10, 2025
Key learnings- Build products at the edge of current model capabilities, since models improve every few months and a barely-working product can…
- Treat evals as unit tests for models: define hero use cases, write evals for them, and hill-climb on those evals to know whether…
- Expect AI behavior to be fuzzy: a model right 60%, 95%, or 99.5% of the time implies very different product designs, so study…
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 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…
Lenny’s Podcast105 min
Varun Parmar · Apr 20, 2023
Key learnings- Organize product teams around personas rather than only outcomes, and embed cross-functional roles like product marketing and…
- Treat every release as a move in the competitive game: each shipped change either improves or weakens your position relative to…
- Be the first to hit the learning wall in competitive markets, since speed of learning often determines who wins, even if that…