Walk Through the Metric Framework You Use to Run the Product You Own Today

Think of the product you are responsible for today. Which metrics do you track to know whether it is succeeding, why those, and how do they shape your decisions? ```hint Start from the goal Before you name a single number, say what the product is for and who it serves; each metric you mention should trace back to that sentence. ``` ### Clarifying Questions - Should I describe the product I own right now even if it is a B2B or internal tool, or would you rather hear about a consumer product I have worked on? - Do you want the full hierarchy, from one top-line metric down to inputs and guardrails, or only the few numbers I review every week? - Is it acceptable to describe trends and relative changes where the actual figures are confidential? ### What a Strong Answer Covers - A one-sentence goal and target users that every metric ties back to - One primary success metric, the input metrics that move it, and guardrails that catch harm - A precise definition for each metric: unit, time window, segment and data source - How often the metrics are reviewed, and a real decision they changed - The known weaknesses of each metric, such as lag, attribution gaps or ease of gaming ### Follow-up Questions - Tell me about a time one of these metrics moved unexpectedly. How did you find the cause? - Which of your metrics lags the most, and what earlier signal do you watch instead? - If you could add one metric your team does not track today, what would it be?