As PM for Facebook Events, would you allow unlimited event creation per user or limit to ensure quality?

Introduction

The trade-off question at hand is whether to allow unlimited event creation per user on Facebook Events or to implement limits to ensure quality. This scenario touches on key aspects of user engagement, platform integrity, and scalability. I'll approach this analysis by examining the product context, identifying metrics, designing experiments, and providing a data-driven recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming this is for the core Facebook platform, not a separate events app. Could you confirm if this is correct, and if there are any specific market segments or user types we're focusing on?

Why it matters: Helps tailor the solution to the right audience and platform constraints. Expected answer: Correct, core Facebook platform for all user types. Impact on approach: Would focus on integrating with existing Facebook features and considering diverse use cases.

• Business Context: Based on Facebook's ad-driven model, I'm thinking event creation might impact ad inventory and targeting. How does event creation currently factor into our revenue model?

Why it matters: Aligns solution with business objectives and potential monetization strategies. Expected answer: Events provide valuable user data and ad placement opportunities. Impact on approach: Would consider balancing user experience with monetization potential.

• User Impact: Considering the diverse Facebook user base, I'm curious about the current distribution of event creation. What percentage of users create events, and how frequently?

Why it matters: Helps understand the scale of impact and identify power users vs. casual creators. Expected answer: Small percentage of power users create most events, with occasional creation by others. Impact on approach: Might lead to a tiered approach based on user behavior and history.

• Technical: Given the potential for increased event creation, I'm wondering about our current infrastructure capacity. Are there any technical limitations or scalability concerns we should be aware of?

Why it matters: Ensures the solution is technically feasible and scalable. Expected answer: Current system can handle increased load, but there may be concerns about spam or abuse. Impact on approach: Would influence whether to focus on hard limits or more nuanced quality control measures.

• Timeline: Considering potential impacts on user behavior and platform integrity, what's our timeline for implementing and testing any changes?

Why it matters: Helps determine the scope and pace of the solution rollout. Expected answer: Aiming for a phased approach over the next two quarters. Impact on approach: Would inform the complexity of the solution and the depth of testing required.