How to choose a North Star metric in a PM interview
When choosing a North Star metric in a PM interview, focus on a measure that captures sustainable value for users and the business. Avoid vanity metrics, state your assumptions, and be ready to discuss trade-offs and potential blind spots.
PMMockr.comDeciding on a North Star metric: The trap of chasing growth
A common mistake in PM interviews is to pick the most obvious growth metric and assume it is always the right answer. For example, a candidate may recommend 'daily active users' for a new social app, hoping it signals ambition and focus. However, this metric alone may not reflect whether users find enduring value or if the business is moving toward long-term success. Instead, the North Star metric should tie directly to meaningful value exchanged between users and the product, not just raw engagement or reach.
Start with the value exchange
Before naming any metric, clarify what users gain from the product and how the business benefits in return. For instance, if you're asked about a ride-hailing app, consider what riders want (reliable, fast rides) and what drivers or the platform need (fair compensation, repeat usage). The right metric encapsulates this relationship, acting as a guide for teams to align priorities and measure progress toward the product’s mission.
Resist the urge to select a metric just because it's easy to measure or widely used elsewhere. Instead, ask: Does this metric reinforce the product's core value? Does it encourage the right behaviors from both users and the company?
Four checks before committing to your metric
A strong North Star metric passes four tests:
- Is it actionable? Teams can influence it through their work. - Is it durable? It remains relevant as the product evolves. - Does it avoid encouraging negative behaviors (like spammy growth hacks)? - Can it be measured reliably?
Briefly walk through each check when presenting your choice. For example: 'Completed rides per week per active user' is actionable (teams can improve matching or supply), durable (remains relevant even as features change), less prone to gaming than raw signups, and measurable with transaction data.
Why counting rules matter more than the noun
It's not enough to say 'rides' or 'messages'—how you count them shapes team incentives. For example, counting only initiated rides might reward spammy behavior, while counting completed rides ensures actual value was delivered. Similarly, measuring 'messages sent' on a chat app might inflate numbers via bots or spam, while 'meaningful conversations' could better capture true engagement, though it's harder to define.
Explain your counting rules clearly. Specify if you mean 'unique users completing at least one ride per week' or 'total rides completed,' and why that level of granularity aligns with product goals.
Worked example: Choosing a North Star metric for a fitness app
Suppose the interview scenario is a digital fitness app aiming to help users build consistent exercise habits. Assume the app has 1 million weekly active users, and offers both guided workouts and social features. The business earns revenue through subscriptions.
First, segment users by intent: some want structured programs, others just track activity, and some engage mainly with the community. The core value exchange is helping users stick to workouts, while the business grows by retaining these users.
A candidate might propose 'Total workouts logged per week.' The reasoning: every logged workout reflects a user taking action and getting value, and the metric is easy to track. But this metric risks over-emphasizing quantity (users logging trivial activities) and ignores whether users are actually progressing or satisfied.
A more thoughtful alternative is 'Active users who complete at least three guided workouts per week.' This threshold balances consistency (habit formation) with meaningful engagement (not just any activity, but guided, higher-value sessions). For prioritization, focus on this metric because it ties to both user outcomes (habit-building) and business goals (engagement correlates with retention).
A competing option might be 'Average session duration per user.' While longer sessions could indicate deeper engagement, this metric can be skewed by a small subset of power users, and doesn't ensure the activity is helpful or healthy.
The trade-off: Setting too strict a threshold (like five guided workouts) may exclude new users or those with limited time, while too loose a definition (any activity) dilutes the metric's value. To validate, run an experiment: segment users by their weekly guided workout count, and track retention and satisfaction over a month. If retention jumps for users who complete at least three guided workouts, and these users renew at a higher rate, the metric is justified. If not, revisit the threshold or definition—perhaps including some unstructured activity, or lowering the bar for new users. New evidence (e.g., a significant group achieving value with just one or two workouts) would prompt a revision.
Anticipating blind spots and unintended incentives
No metric is perfect. Good interview answers proactively name what the metric might miss. For the fitness app, 'guided workouts completed' could overlook users who prefer solo runs or yoga tracked via the app, undervaluing their experience. It might also incentivize superficial completion (users skipping through videos just to check a box).
State these blind spots, and suggest how you’d monitor or mitigate them. For example, track the ratio of completed to started workouts, or run periodic user surveys to capture satisfaction beyond the primary metric.
Weak reasoning vs. thoughtful justification
Weak reasoning: 'I would pick daily active users as the North Star because more users is always better for business.' This answer ignores the quality of engagement and assumes volume equals value, which can lead to optimizing for empty activity.
A better approach: 'I propose using weekly users who complete at least three guided workouts, because this reflects meaningful, repeat engagement—the behavior that correlates with retention and revenue for a fitness app. I would monitor for users who may be underserved by this metric, such as those who prefer unstructured activity.'
The key difference is that the stronger answer ties the metric to both the value delivered and the business model, and explicitly considers who might be excluded or misrepresented.
Practice exercise: Time-bound scenario
Set a timer for 15 minutes. Choose a product (for example: a language learning app). List the core value provided and the main user segments. Propose a North Star metric, explain your counting rules, discuss one risk or blind spot, and outline a basic experiment or data slice to validate your choice.
Afterward, review your answer using the checklist below. Practicing twice a week on different products will help you internalize this process. PMMockr offers scenario drills for additional reps.
Self-review checklist for North Star metrics
Use this checklist to evaluate your practice answers: - Did I link the metric to the value users get and the business goal? - Are my counting rules explicit and justified? - Did I name at least one trade-off or limitation? - Did I describe how I would validate or adjust the metric? - Did I avoid assuming that volume alone equals value?
FAQ
How do I handle interview pushback on my North Star metric?
Acknowledge the interviewer's concerns, clarify your assumptions, and explain your reasoning. Be ready to discuss trade-offs and alternative metrics, and describe how you'd monitor for issues or adjust based on new evidence.
What if there’s no perfect metric for the product?
Perfection isn’t required. Choose the metric that best captures the main value exchange and call out its blind spots. Suggest supplemental metrics or monitoring to cover gaps, and explain how you would revisit the choice as the product evolves.
Should I always avoid simple metrics like DAU or MAU?
Not necessarily. Use them if they truly reflect meaningful engagement for your specific product. However, you must justify why these metrics capture the core value and explain how you’d avoid optimizing for empty or low-value activity.