How to Approach Metrics Definition Cases

Metrics Definition Cases

As a Product Manager, metrics are your compass. They tell you whether you're shipping the right thing and whether it's actually working for users.

Metrics cases show up when a team needs to decide what success means. You may see cases in different forms:

• "Build a LinkedIn for blue collar workers. What metrics would you track?"
• "What is the north star metric for Uber and why?"
• "How would you set up an A/B test for this feature?"

You must be thinking, "How do I pick the right metrics when there are so many options?"

Before we dive into the framework, let's understand what good product thinking looks like.

What good product thinking looks like

Strong metrics cases test whether you can show:

1. Product Sense - Can you connect metrics to what actually matters for the product?
2. Analytical Thinking - Do you understand the difference between vanity metrics and actionable ones?
3. Business Acumen - Can you tie metrics to business outcomes?
4. Prioritization - Can you focus on the few metrics that matter vs. tracking everything?

The Metrics Definition Framework

A structured approach to defining metrics:

1. Understand the Product/Feature Objective

   • What problem does it solve? What outcome are we hoping for?
   • This guides which metrics are actually relevant

2. Identify Key Stakeholders

   • Users, business, engineering - each cares about different outcomes
   • Consider whose success you're measuring

3. Define Success Criteria

   • What does "working" look like for this product?
   • Be specific: "Increased engagement" is vague; "Users return 3+ times per week" is clear

4. Brainstorm Metrics by Category

   Think across these dimensions:

   • Engagement: DAU, MAU, time spent, feature adoption rate
   • Retention: Retention rate, churn rate, cohort analysis
   • Conversion: Conversion rate, CTR, funnel completion rate
   • Satisfaction: NPS, CSAT, user feedback ratings

5. Prioritize and Select

   • Pick 1 north star metric + 2-3 supporting metrics
   • Ask: Is it measurable? Is it actionable? Is it tied to the goal?

Tips for Success

1. Start with the goal - Metrics should flow from what you're trying to achieve, not the other way around
2. Distinguish leading vs. lagging indicators - Leading indicators predict future success; lagging indicators confirm past results
3. Avoid vanity metrics - Total users sounds impressive but doesn't tell you if the product is healthy
4. Consider counter-metrics - If you optimize for speed, track quality too. Prevent gaming.
5. Be specific - "Improve retention" is vague; "Increase D7 retention from 30% to 40%" is actionable

Sample Cases

• What metrics would you use to measure the success of Instagram Stories?
• How would you know if a new checkout flow is working?
• What's the north star metric for Spotify and why?
• You launched a new feature and DAU increased 10%. Is that good?

Remember: The goal isn't to list every possible metric - it's to demonstrate that you can identify the few metrics that truly matter and explain why they're the right ones to track.

Define metrics precisely

Do not stop at names such as “retention” or “engagement.” Define the eligible population, qualifying event, numerator, denominator, and time window. For example: “D7 retained creators = creators who published in their first 24 hours and publish again on day seven, divided by all creators who published in their first 24 hours.”

In your answer, connect one north-star or outcome metric to two or three input metrics the team can influence. Add guardrails for quality, trust, or ecosystem health. Then explain the likely failure mode: could the metric be gamed, lag too much, or improve while an important user segment gets worse? That discussion is often more valuable than a long metric list.