Group Call Need Assessment

Company Context

Meta is evaluating a new calling surface inside FB Groups to help members coordinate live discussions without leaving the group. The product team has a table of launch data from a limited pilot across several group types, and needs a decision on whether the feature is worth scaling.

Problem

You are given only the table below, which includes usage, retention, and experiment quality signals for the pilot. Your job is to determine whether a group call feature is actually needed, or whether the observed behavior can be explained by existing surfaces like comments, Messenger, or event posts.

The team also has a pre-experiment baseline for each group, so you can reason about CUPED adjustment, and the pilot was run long enough to observe possible novelty effect decay. Your decision should consider whether the feature improves the AARRR funnel for FB Groups, or whether it is just a temporary spike driven by early adopters.

Deliverables

1. Decide whether the table supports building a group call feature for FB Groups.
2. Identify which segments, if any, justify launch priority.
3. Explain how you would check for SRM, CUPED-adjusted impact, and novelty effect before making a launch call.
4. State the key metric threshold you would use for go/no-go.
5. Recommend the next product action, including whether to iterate, narrow the use case, or stop.

Constraints

• You may use only the provided table and Meta product vocabulary, no external market research.
• Assume engineering can support only one additional iteration in the next quarter.
• The decision must be defensible for FB Groups leadership and should not rely on vanity metrics like raw call starts alone.