Metrics question

Describe the metrics you would use to see if the product you are launching will be a success or not.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Ability to define a structured metrics framework for judging a launch, not just naming random KPIs.

Clarify the product goal first, since success metrics depend entirely on whether the goal is growth, engagement, or revenue.
Define a north star metric tied directly to the core value proposition, like weekly active users completing the core action.
Add adoption metrics: activation rate and time to first value for new users.
Add retention metrics: week over week or month over month return rate.
Set guardrails: ensure the launch doesn't regress an adjacent metric, like overall app performance or support ticket volume.
Set a time horizon, since a 2 week launch spike differs from a sustained 90 day success signal.

Anchors the metric choice explicitly to the product's stated goal rather than a generic list of vanity metrics.
Distinguishes activation, the first value moment, from retention, sustained return usage, as separate concerns.
Adds a guardrail metric, protecting against a launch that boosts one number while quietly harming another.
Specifies a time horizon for judging success, avoiding a premature call based only on launch week data.

Naming a random list of metrics without connecting them to the specific product goal.
Judging success purely from short term launch spike numbers.

Chapters of the AI PM course that teach what this question tests.