Defining a North Star and Guardrails for Meta's New Video Meeting Product

You are a product manager at Meta, and Meta is about to launch a new video conferencing product. Define the metrics you would use to judge whether the launch is a success. ```hint Goal before metrics Decide what Meta wants this product to achieve and which calls it is built for. A metric that fits work meetings may be wrong for friends catching up, and the reverse. ``` ### Clarifying Questions - Is the product a standalone app or part of an existing Meta app such as Messenger, WhatsApp, Instagram or Facebook? - Is it for consumers (friends, families, groups and creators) or for workplace meetings? - Which call formats does it launch with: one-to-one, small groups, large one-to-many broadcasts, or all three? - Is this an MVP launch in one market or a broad rollout? ### What a Strong Answer Covers - The product's goal, tied to Meta's mission and business, stated before any metric - The users on both sides of a call and the main use cases, mapped to a funnel from first call to habit - One north-star metric with a precise definition and a reason it beats alternatives such as call minutes - Supporting metrics for adoption, engagement, retention and call quality, plus guardrails for cannibalization, safety and privacy - How the metrics are read at launch: baselines, targets and a holdout or experiment ### Follow-up Questions - If the product lives inside Messenger, how would you tell new calling apart from calls that simply moved over from Messenger's existing video calls? - Call minutes rise sharply after launch, but the share of calls rated as good falls. What do you do? - How would your metrics change if the product were aimed at workplace meetings?