Overview
UX metrics fail when they measure activity rather than outcomes. Page views, session duration, and click counts are activity metrics — they tell you what users did, not whether they accomplished what they came to do. A user who spends 20 minutes on a checkout page is not an engaged user — they are a confused user. Session duration is not a UX metric. Task completion rate is.
The UX Metrics Framework Prompt builds a measurement system from the user outcomes that matter — defining the metrics that distinguish successful interactions from failed ones, the instrumentation that captures them without requiring custom development for every measurement, and the reporting format that makes UX data actionable for product teams rather than decorative for design presentations.
What you get: - Metric selection framework: the criteria for choosing metrics that measure outcomes, not activity - HEART framework application: how to apply Google's HEART model to a specific product - Instrumentation plan: the events and properties that must be tracked to calculate each metric - Baseline establishment: how to set meaningful targets before optimization begins - Reporting cadence: the dashboard structure and review rhythm that keeps UX data visible - Metric failure modes: the metrics that look good while UX degrades
Built for: UX designers, product managers, and design leads building a UX measurement program for a web or mobile product.