PodcastInsight

Gibson Biddle on his DHM product strategy framework, GEM roadmap prioritization framework, 5 Netflix strategy mini case studies, building a personal board of directors, and much more

with Gibson Biddle · Jun 2022

Clarify what you implicitly allow, don't assume understanding

Netflix allowed account sharing for years without explicitly stating household-only restrictions, then had to clarify the rules later. Ambiguity about product boundaries creates problems at scale. Make your constraints and permissions explicit early, especially around monetization and usage rights.
Share on X

Related

Connected ideas

Ideas from across Lenny's archive that connect to this one

Gibson Biddle on his DHM product strategy framework, GEM roadmap prioritization framework, 5 Netflix strategy mini case studies, building a personal board of directors, and much more

Jun 2022

Kill features that only 2% of users adopt

Features used by only 2% of your customer base create complexity for everyone else without meaningful business impact. Netflix called this 'scraping the barnacles'—ruthlessly removing low-adoption features to maintain simplicity and focus. Reach matters more than the quality of an idea.

Insightpodcast
61%

Gibson Biddle on his DHM product strategy framework, GEM roadmap prioritization framework, 5 Netflix strategy mini case studies, building a personal board of directors, and much more

Jun 2022

Customer choice may trump simplicity and delight

When Netflix faced growth challenges, Reed Hastings shifted from prioritizing simplicity to prioritizing customer choice—offering an ad-supported tier even though it added complexity. Sometimes market conditions force you to serve different customer segments differently, even if it contradicts your original strategy.

Insightpodcast
58%

A Three-Step Framework For Solving Problems 👌

Jun 2019

Problem statements are silver burritos

Everyone on your team has a unique version of the problem in their heads. The larger and more complex the project, the more likely they are different. Your job is to eradicate this misalignment early by making the implicit explicit—opening up the wrapper so everyone agrees on what's inside.

Insightnewsletter
56%

Gokul Rajaram on designing your product development process, when and how to hire your first PM, a playbook for hiring leaders, getting ahead in you career, how to get started angel investing, more

Jun 2022

Empower teams with problems, not solutions

The biggest pitfall is founders becoming too tactical and dictating features instead of presenting problems. Present the goal—'increase weekly usage from 2x to 5x'—and let the team brainstorm solutions. This creates ownership and prevents the feature factory trap.

Insightpodcast
54%

A Three-Step Framework For Solving Problems 👌

Jun 2019

Confusing solution with problem kills projects

Nothing is more certain to cause a project to fail than a misunderstanding of the problem you are solving. The Airbnb social travel team built a beautiful product solving the wrong problem—they thought travelers wanted to hang out together, when the real problem was travelers wanted to find high-quality non-touristy things to do.

Insightnewsletter
54%

Avid does this with your books

Import your highlights, and we'll find the connections you've been missing.