Your director at Netflix asks about Multiple Screens: should we add more Netflix screen-specific settings that increase complexity, or keep unified settings?

Introduction

The trade-off we're examining today is whether Netflix should add more screen-specific settings, increasing complexity, or maintain unified settings across all screens. This scenario touches on the delicate balance between customization and simplicity in user experience. I'll approach this analysis by first clarifying the context, then diving into the product understanding, identifying key metrics, designing an experiment, and finally providing a recommendation with next steps.

Step 1

Clarifying Questions (3 minutes)

• Based on recent market trends, I'm thinking this might be driven by increased multi-device usage. Could you share any data on how our users are currently interacting across different screens?

Why it matters: Helps understand the scale and urgency of the problem Expected answer: Significant increase in multi-device usage over the past year Impact on approach: Would prioritize a solution that addresses cross-device consistency

• Considering our revenue model, I'm curious about how this aligns with our subscription tiers. Are we seeing any correlation between multi-screen usage and higher-tier subscriptions?

Why it matters: Helps assess potential revenue impact of the decision Expected answer: Higher-tier subscribers tend to use multiple devices more frequently Impact on approach: Might lean towards more customization for premium users

• Looking at user behavior, I'm wondering about the most common pain points in the current unified settings. What are the top user complaints or feature requests related to screen-specific settings?

Why it matters: Identifies key areas for improvement and potential customization Expected answer: Complaints about video quality settings not transferring well across devices Impact on approach: Would focus on specific high-impact settings for customization

• From a technical perspective, I'm thinking about the complexity of implementing and maintaining screen-specific settings. Could you give me an overview of our current architecture and how flexible it is for this kind of customization?

Why it matters: Assesses feasibility and potential technical debt Expected answer: Current architecture can support some customization, but major changes would require significant refactoring Impact on approach: Might suggest a phased approach, starting with high-impact, low-complexity customizations