As PM for Facebook Live, would you allow longer streams with basic features or shorter streams with advanced features?

Introduction

The trade-off we're considering for Facebook Live is whether to allow longer streams with basic features or shorter streams with advanced features. This scenario involves balancing user engagement, technical constraints, and product differentiation. I'll analyze this trade-off by examining user needs, technical feasibility, business impact, and potential experiments to inform our decision.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming this is a strategic decision for Facebook Live's future direction. Could you confirm if this is a proactive product evolution or a reaction to specific user feedback or competitor moves?

Why it matters: Helps frame the urgency and strategic importance of the decision. Expected answer: Proactive evolution based on user behavior trends. Impact on approach: Would focus on long-term strategy rather than immediate competitive response.

• Business Context: I'm thinking about our monetization strategy for Live. How does the current revenue model for Facebook Live factor into this decision?

Why it matters: Aligns product decisions with business objectives. Expected answer: Ad-based revenue with potential for creator monetization features. Impact on approach: Would consider how stream length and features affect ad inventory and creator earnings.

• User Impact: Based on our user segments, I'm curious about the primary use cases driving longer streams. Can you share insights on who's pushing for longer streams and why?

Why it matters: Ensures we're solving real user needs rather than assumed ones. Expected answer: Certain creator types (e.g., gamers, educators) need longer streams for their content. Impact on approach: Would tailor solution to specific high-value user segments.

• Technical: Considering the infrastructure required, what are our current technical limitations for supporting longer streams or more advanced features?

Why it matters: Determines feasibility and potential development costs. Expected answer: Bandwidth and storage concerns for longer streams; processing power for advanced features. Impact on approach: Would balance user desires with technical constraints and development timelines.

• Resource: I'm thinking about our team structure. Do we have separate teams for stream length optimization and feature development, or is it a single team?

Why it matters: Influences resource allocation and implementation strategy. Expected answer: Single team responsible for both aspects. Impact on approach: Would need to carefully prioritize efforts between the two options.