Master North Star Metrics
Choose a measurable customer outcome, define its counting rules, and connect it to inputs, business health and decisions.
Original PMMockr learning guide · Examples are illustrative, not company interview transcripts.
Before you start
Understand a distinct user, an event and a time window.
What you will learn
- Connect the chosen measure to delivered value.
- Compare candidates and define counting exclusions.
- Separate input movement from evidence of durable outcomes.
Read the explanation, attempt the problem yourself, then compare the worked answer.
Choose a North Star for an online tutoring marketplace.
Original teaching scenario. Any figures are illustrative assumptions.
Scope and assumptions
- All event records and arithmetic below are hypothetical teaching inputs.
- Assume repeat useful learning is the customer value; booking alone is not proof of learning.
How to tackle this question
- Describe the repeated value received by the learner and tutor. Compare registrations, bookings and useful completed sessions.
- Define the chosen entity, event, eligibility, window and duplicate exclusions; keep missing feedback unknown.
- Connect input metrics to an action and add a check for gaming, lost coverage or weak economics.
Try a short outline and spoken answer before comparing.
Reveal model solution and reasoning
Compare candidate metrics
Registrations measure acquisition, bookings measure intent, and completed useful sessions are closer to delivered learning. I would provisionally select weekly learners completing a useful session, with usefulness validated through learner feedback and appropriate learning checks. Revenue remains necessary for viability.
Specify the counting contract
Count a distinct learner once per stated calendar week after a completed eligible session and a defined usefulness signal. Exclude cancellations, tests and duplicate events. In an illustrative log, learner A has two eligible sessions, B cancels, and C completes one eligible session: the weekly learner count is two, not three. Missing feedback stays unknown and its coverage is reported.
Connect inputs to action
Track matching success, attendance and useful-session rate by subject and tutor availability. If bookings rise while useful-session completion falls, investigate matching or delivery rather than spending more on acquisition. Monitor tutor cancellations, learner complaints and contribution after refunds.
Interviewer follow-up
What if usefulness feedback becomes less frequent?
Report response coverage and compare like-for-like cohorts before claiming improvement. Audit a consented sample; do not silently count every unreviewed session as useful. Revisit the measurement if it systematically excludes learners.
Check your reasoning
- Is the metric tied to repeated customer value?
- Are entity, event, eligibility, window and deduplication explicit?
- Did I identify an input, a blind spot and a business check?
Try a changed constraint
Write the metric as an event specification. Calculate it for three learners with duplicate, cancelled and missing-feedback events, then propose a gaming attempt.
Go deeper
A proposed North Star is a hypothesis about value. Validate its relationship to durable outcomes; correlation alone does not prove causation.
Use separate product-level measures when customer jobs differ enough that one aggregate would conceal tradeoffs.
Start with the vocabulary
North Star metric
A primary measure of the value customers repeatedly receive from a product. Define the event, eligible population and time window. It should connect customer value to a sustainable business outcome.
For a learning tool, weekly learners completing a useful practice session can be more informative than total registrations.
Common mistake: Choosing revenue or daily activity without explaining how it reflects value for this product.
Cohort and funnel
A cohort groups users by a shared starting event or characteristic. A funnel measures movement through ordered steps. Combining them helps locate where an experience breaks for a particular group.
Compare new Android users moving from signup to payment before and after a release, using the same observation window.
Common mistake: Comparing this week’s new users with last month’s mature users without accounting for age.
Guardrail metric
A measure that tells you whether improving your main objective is causing unacceptable harm elsewhere. Name the downside, how you measure it and what action a breach would trigger.
A faster checkout experiment can improve conversion while increasing refund requests. Track refund rate alongside conversion and agree a rollback threshold before the experiment.
Common mistake: Listing “quality” as a guardrail without an observable measure or decision rule.
Counter-metric and tradeoff
A counter-metric makes the downside of your chosen objective visible. A tradeoff is the decision to accept one cost in return for a benefit; explain who bears that cost and why it is justified.
More notifications may lift return visits but also increase notification opt-outs. Decide what balance would justify launching.
Common mistake: Claiming the recommendation has no meaningful downsides.
Build your answer, layer by layer
This is a learning sequence, not a mandatory order for presenting every answer. Adapt to the actual question.
Identify the value users return for
Describe the recurring benefit users receive without naming a metric yet. This makes it easier to reject numbers that only measure exposure.
Apply it: For a language tutor, the value is useful learning practice rather than app opens.
Go deeper: Explain the difference between a customer outcome and a company revenue outcome.
Connect user value to business outcomes
Connect a user action to the benefit and explain why repeated delivery could support the business.
Apply it: Learners who complete useful sessions may be more likely to return; validate that relationship rather than assuming it.
Go deeper: Identify a case where more activity signals frustration instead of value.
Compare North Star metric candidates
Consider whether each candidate measures value, can be influenced by the team and is understandable. Explain its blind spots.
Apply it: Compare completed lessons, demonstrated learning and weekly returning learners.
Go deeper: Discuss delayed outcomes when the best value measure is slow to observe.
Define the event, population and time window
Specify the event, population, time window and aggregation. Two people should calculate the same result from your definition.
Apply it: “Unique eligible learners completing at least one qualifying practice session in a calendar week.”
Go deeper: Explain exclusions, deduplication and how eligibility changes affect trends.
Break the North Star into input metrics
Break down the primary outcome into levers that teams can investigate. Avoid treating a convenient correlation as proof of a causal driver.
Apply it: Useful weekly sessions may depend on activation, successful session completion and repeat usage.
Go deeper: Show how an experiment can test whether a proposed driver actually moves value.
Spot metric gaming and blind spots
Ask how a team could increase the number without helping users. Add complementary evidence for the gap.
Apply it: Shortening every lesson may increase completions without improving learning.
Go deeper: Explain how qualitative research or outcome sampling would detect the problem.
Adapt metrics to product stage and business model
A new product may need to establish value before optimizing scale. A marketplace must consider the health of both sides.
Apply it: More tutoring bookings do not help if tutors cancel or learner outcomes deteriorate.
Go deeper: Defend whether one shared North Star or several product-level measures are appropriate.
Use metric changes to make a product decision
Connect a change in the metric to an investigation or product decision. Include uncertainty and guardrails.
Apply it: If sessions increase but learning outcomes weaken, investigate session quality before expanding acquisition.
Go deeper: Explain when the product strategy has changed enough to revisit the North Star itself.
Compare what each candidate rewards
For tutoring, registrations reward acquisition, bookings reward intent and completed useful sessions are closer to learning value. None proves learning by itself. Explain the behavioral incentive each creates and its blind spot. Revenue and supplier economics remain necessary business checks even when another measure guides product learning. A single North Star does not remove the need for a balanced view.
Specify an auditable definition
Name the entity, qualifying event, eligibility, time zone, time window, deduplication rule and missing-data behavior. Distinct weekly learners differ from session count: one learner completing three sessions counts once in the former and three times in the latter. Report feedback coverage if usefulness depends on surveys. Build inputs such as available tutors, successful matches and attendance, then validate whether improvements are associated with repeat useful learning rather than metric gaming.
Connect the reading to this case
Activity is only useful when its connection to the intended behavior is clear. Specify what your metric counts and why that represents progress.
Julia Winn: Analytical interview mistakesDefine a North Star metric for Maps serving commuters.
Attempt this second problem before comparing. Behavioral answers must use a true experience.
Compare with PMMockr’s worked solution
Original public teaching answer; hypothetical figures and fictional experience are not results to claim as your own.
I would clarify whether we are improving driving, transit or mixed-mode commuting. Assume the goal is a dependable transit journey for recurring commuters. Opening the app is an input, not the outcome we want.
I would propose the share of eligible planned commute journeys completed within the arrival window shown when the route was chosen. Define the arrival window, eligible journeys, observation period and completion signal before comparing results. Location consent and incomplete observation matter: do not classify missing telemetry as successful travel.
Diagnose route selection, departure timing, missed connections and arrival errors by route and service disruption. Track coverage and opted-in sample composition alongside reliability so a higher rate cannot hide excluding difficult journeys. Compare against the existing experience in a controlled trial before attributing a change to recommendations.
Pushback
The rate improves after telemetry permission drops. Is that success?
Not yet. Check whether the observed commuters changed. Report coverage, compare like-for-like cohorts and use consented research to investigate journeys the telemetry misses.
Common mistake
Track daily active commuters.
Why this answer is stronger
Usage can grow while journeys get worse. The stronger answer defines an outcome, denominator, missing-data rule and a way to detect selection bias.
From a weak answer to a defensible one
Weak: The North Star is daily active users because all teams can grow it.
Stronger: I would compare value-linked candidates, define exactly what counts, and test whether the selected measure hides poor outcomes or excluded learners.
Prepare your own answer
Invent a way to game your proposed metric, then add a diagnostic or guardrail without redefining away the problem.
Close the guide and answer aloud. After reviewing, identify one missing decision and retry on a different problem.
Watch one interview
Google Product Manager Data Interview: Define TikTok Success ↗
Exponent · Mock interview · YouTube
Watch with a task: Compare time spent, sessions and user value. Specify what your chosen metric misses and how to count it consistently.
Practice with a PMMockr worked answer
Open the practice problem and attempt it before comparing.
Compare after your attempt
Read the original worked answer, follow-up and feedback
Compare problem framing, assumptions, rejected options, evidence and response to pushback. Explain what evidence would settle a disagreement.
Further reading and perspectives
Official documentation explains product behavior; coaching and community accounts offer preparation perspectives. Interview examples do not confirm a company’s current hiring process.
- Amplitude: North Star Framework
Distinguish the value outcome from the inputs a team can influence.
Primary framework · Public page - IGotAnOffer: Product metrics interview questions
Compare metric definition with metric diagnosis, then practice each separately.
Interview coach guidance · Public page - Julia Winn: Analytical interview mistakes
Connect the intended behavior change to a computable metric and explain the estimate. This historical account is not a current interview specification.
Medium · practitioner guidance · Public article reviewed
Turn the reading into practice
- Easy: outline your answer and explain every term you use.
- Medium: compare two options, defend one and name a downside.
- Hard: handle uncertainty, conflicting goals and a changed assumption.
Complete three questions at each level in your selected learning path where available. Review model solutions through the question’s solution action after meeting its access requirements.
Choose a learning path →Further reading
Continue with these related PMMockr articles. Examples in this guide are illustrative practice scenarios.