The WhatsApp Calls team is discussing: should we add more call features or focus on improving call stability?

Introduction

The WhatsApp Calls team is facing a critical trade-off: should we add more call features or focus on improving call stability? This decision will significantly impact user experience, product differentiation, and resource allocation. I'll analyze this trade-off by examining the current product landscape, potential impacts, and key metrics, then design an experiment to inform our decision-making process.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming WhatsApp Calls is facing increased competition. Could you share how our market share has trended over the past year compared to competitors like Zoom or FaceTime?

Why it matters: Helps prioritize between feature parity and core stability Expected answer: Slight decline in market share Impact on approach: Would lean towards feature addition if significant decline

• Business Context: Based on our revenue model, I'm thinking call quality might indirectly impact our business through user retention. How does call performance currently factor into our key business metrics?

Why it matters: Aligns solution with business objectives Expected answer: Strong correlation between call quality and daily active users Impact on approach: Would prioritize stability if closely tied to revenue

• User Impact: Considering our diverse user base, I'm curious about the distribution of complaints between feature requests and stability issues. Do we have data on the top reasons for user churn or dissatisfaction?

Why it matters: Ensures we're addressing the most pressing user needs Expected answer: Mix of both, with slight lean towards stability issues Impact on approach: Would balance both aspects based on user feedback weight

• Technical: Given our current architecture, I'm wondering about the feasibility of improving stability without sacrificing new feature development. What's our engineering team's assessment of our technical debt in the calling infrastructure?

Why it matters: Determines if we can realistically pursue both paths Expected answer: Moderate technical debt, requiring some dedicated focus Impact on approach: Might suggest a phased approach, tackling stability first

• Resource: Considering our team's capacity, I'm thinking this might require trade-offs in other product areas. How flexible are our resources for the Calls team in the next two quarters?

Why it matters: Helps determine the scope of what we can realistically achieve Expected answer: Limited flexibility, requiring clear prioritization Impact on approach: Would focus on highest impact area based on earlier answers