What it is
Structured approaches, such as Google’s HEART and the Goals-Signals-Metrics method, for selecting UX metrics that connect user and business goals to observable signals and specific measures.
When to use it
During Initiate to set targets, and Implement to track them, whenever you need to measure experience quality over time.
Why (value)
Prevents vanity metrics and metric sprawl by deriving a small, meaningful set from explicit goals.
How to run it
- State the user and business goals.
- Identify signals that indicate progress toward each goal.
- Define concrete metrics for each signal.
- Set targets and baselines.
- Instrument, track, and review regularly.
Inputs and outputs
- Inputs: Clear goals and access to measurement.
- Outputs: A goal-aligned metric set with targets.
Time and effort
Medium. The thinking matters more than the tooling.
Evidence and limitations
The framework structures measurement but the metrics themselves are an inference about experience; a metric is a proxy for a goal, and a good number does not prove a good experience. See Evidence and limitations.
Tips and pitfalls
- Derive metrics from goals, not availability.
- Keep the set small and meaningful.
- Revisit metrics as goals evolve.
Variations
HEART, Goals-Signals-Metrics, pirate metrics (AARRR), and SUS or NPS tracking.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Analytics review — Examine real usage data to see what large numbers of users actually do.
- Usability benchmarking — Measure usability metrics the same way over time to track whether the experience is improving.
- Roadmapping — Sequence outcomes and work over time to align the team on where things are heading and why.
