Why Rising Time-on-Page Can Be a Bad Sign, Not a Good One
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?
The correct answer is "Rising time-on-page for a routine task can mean confusion, not value."
This subject's goal-metric mismatch table names this exact case: time-on-page, treated as "more engagement," is a tempting but flawed metric for task efficiency, because a well-designed flow should reduce time-on-page for a routine task — a rising number can mean confusion rather than deepened engagement. The better metric is time-on-task trending down for a routine task, which is the opposite direction "more engagement" would suggest reading it.
The distractors misapply the framework: "time-on-page always means engagement regardless of task type" is precisely the goal-metric mismatch this subject is warning against — the correct read depends on whether the task is routine/efficiency-oriented or open-ended content consumption; "the metric is meaningless and should never be tracked" overcorrects — this subject's fix is interpreting it correctly, not discarding it; and interpreting it doesn't require a North Star metric specifically — the fix is the GSM discipline of checking the metric against the actual stated goal.
Share this question