Build a goal and measurement framework for a video chat app you admire

Choose the video-calling product you like most: any app people use to talk face to face over live video, for personal or work calls. Explain what makes it your choice, then set out the goals the product should pursue and the metrics you would use to tell whether it is succeeding. ### Clarifying Questions - If the chosen app does more than video calls (messaging, meetings, social features), should the goals and metrics cover the whole app or only its video-calling experience? - Should the metrics serve the product team's week-to-week decisions, the company's business goals such as revenue, or both? - Should I assume the product is mature and widely adopted, or still growing? That shifts the goals between call quality and habit on one side and reach on the other. ### Part 1 — Pick the product and explain its value Name the product, who uses it and for what, and what it does better than the alternatives for those users. ```hint Make the choice useful for Part 2 Describe the main use precisely (who calls whom, about what, on which devices and networks), because the goals and metrics in the next part should follow from it. ``` #### What This Part Should Cover - A specific product with its core users and main use cases. - What sets it apart, stated as value to users rather than as a feature list. - A one-line purpose or mission that the goals can be derived from. ### Part 2 — Set goals and success metrics Define the product's goals and the metrics that show whether it is meeting them. ```hint Start from one good call Ask what has to happen for a single call to be a success for the people on it, then roll that up to the product level. Then ask what could get worse if the team pushed that number as hard as possible. ``` #### What This Part Should Cover - Goals that follow from the purpose, for users and for the business. - One primary metric with a precise definition, and why it reflects value rather than raw activity. - Supporting metrics across the call journey and call quality, plus guardrails. ### What a Strong Answer Covers - A clear chain from the product's purpose to its goals to its metrics. - Metric definitions precise enough to compute: the unit, the time window and what counts as a call. - Call quality and reliability measured directly, not inferred from usage counts. - Awareness of trade-offs and of ways a metric can be inflated, such as very short or accidental calls. ### Follow-up Questions - After a launch, your primary metric rises but the average call length falls. How do you work out whether that is good news? - Which of your metrics would decide an A/B test of a new background-noise suppression feature, and what result would make you stop the test early? - How would your goals and guardrails change if the company started charging for some calling features? - Suppose the interviewer picks the product for you: a video meeting tool for work, such as Zoom or Google Meet, where hosts run meetings, attendees join from a link and there is a free plan alongside paid ones. How do your goals, primary metric and guardrails change?