| name | lennypodcast-product-management |
| description | Product management wisdom from 200+ Lenny's Podcast episodes. Covers discovery, delivery, prioritization, roadmaps, metrics, OKRs, and PM frameworks. Use when building product strategies, prioritizing features, running discovery, setting metrics, creating roadmaps, or improving PM processes. |
Lenny's Product Management Playbook
Curated product management insights from 196 Lenny's Podcast episodes featuring world-class PMs from Stripe, Airbnb, Meta, Netflix, Spotify, and more.
Core Principles
Product Discovery
- Understand before executing: Do "understand work" before building. Invest time in data instrumentation, analysis, and user conversations. Going slow upfront leads to higher experiment win rates.
- Voice of customer: Bring the literal voice of the customer into product conversations through customer advisory councils and direct user research.
- Adjacent possible: Focus on small, actionable steps within reach. Define a clear North Star, then identify incremental steps toward it.
Prioritization Frameworks
- 4BB Framework (Anuj Rathi): Categorize work into Brilliant Basics, Bread and Butter, Big Bets, and Breaking Bad.
- Pre-mortems (Annie Duke): Before starting, imagine failure and set kill criteria. Commit to reassess if red flags appear.
- Hill climbing (Ami Vora): Recognize that reaching global optimum requires leaving local peaks and traversing valleys.
Strategy & Vision
- Strategy changes behavior: The goal of a strategy is to change the team's behavior, not just document direction.
- Perceived simplicity: Even if underlying technology is complex, user experience should be simple and intuitive.
- Gardener vs. builder mindset: Builders plan meticulously; gardeners allow for unexpected breakthroughs.
Execution Excellence
- End every meeting with 3 questions (Alisa Cohn): What did we decide? Who does what by when? Who else needs to know?
- De-risk meetings: Pre-socialize ideas with stakeholders before formal meetings.
- Managing Complex Change framework: Teams need Vision, Skills, Incentives, Resources, and Action Plan. Missing any causes specific failure modes.
Metrics & OKRs
- North Star + input metrics: Define one North Star (e.g., weekly active users) with input metrics that ladder up to it.
- Quantify non-sexy work: Justify tech debt and bug fixes by quantifying impact on performance, costs, or satisfaction.
- Culture of experimentation: Create an environment where it's okay to fail and learn.
Key Frameworks
| Framework | Source | Use Case |
|---|
| Working Backwards | Amazon/Anuj Rathi | Align products with customer needs |
| Jobs-to-be-Done | Bob Moesta | Understand why customers hire products |
| RICE/ICE | Various | Prioritize features by impact |
| OKRs | Various | Set and track objectives |
| Shape Up | Ryan Singer | 6-week cycles with fixed time, variable scope |
| Design Sprint | Jake Knapp | Rapid prototyping and validation |
When to Use This Skill
- Building or refining product strategy
- Prioritizing features or initiatives
- Running product discovery
- Setting up metrics and OKRs
- Creating product roadmaps
- Improving PM team processes
- Preparing for product reviews with executives
Reference Files
references/knowledge_base.md - Full insights from 196 podcast guests
references/frameworks.md - Complete list of 400+ frameworks mentioned
Usage
For specific insights, grep the knowledge base:
grep -i "prioritization\|roadmap\|discovery" references/knowledge_base.md
For framework details, search:
grep -i "RICE\|OKR\|Jobs-to-be-Done" references/frameworks.md