Practice — Design Metrics and Product Thinking (9 questions)

Your VP asks: "We just launched in-app commenting on shared documents. I want to know if it's actually working — figure out how we'd measure that." There's no existing dashboard for this feature, and the VP hasn't defined what "working" means.

1. Pick the HEART category (or categories) most relevant to this request and justify the choice.
2. Walk through the Goals-Signals-Metrics process to turn this into one or two specific, instrumentable metrics.
3. Name one guardrail metric you'd track alongside your primary metric, and explain what it would catch if the primary metric improved for the wrong reason.
4. The VP says "just tell me engagement went up." Why is that answer insufficient, and what would you say instead?

A team is instrumenting metrics for a one-time account setup wizard using Google's HEART framework.

Per this subject's guidance that not every category applies to every project, which HEART category has no meaningful version here?

A two-sided marketplace is deciding on its North Star metric.

Per this subject's canonical example, why is "total signups" a weaker choice than an alternative like "successful transactions completed"?

A team simplifies a signup form and tracks form-completion rate as the primary target metric.

Per this subject's guidance, what's the purpose of also tracking activation and retention as guardrail metrics alongside it?

After a redesign, a routine task's average time-on-page goes up, and a PM celebrates it as "more engagement."

Per this subject's goal-metric mismatch table, what's the better interpretation for a routine, non-content task?