# HEART Framework

Google’s HEART framework organizes user-experience measurement around Happiness, Engagement, Adoption, Retention, and Task success.

- Type: framework
- Domain: Data, experimentation & growth
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/heart-framework/>)

## What it means

HEART is a user-centered metrics framework created at Google for measuring experience at scale. Its five categories are Happiness, Engagement, Adoption, Retention, and Task success; teams select only the categories relevant to a product or feature.

## Why it matters

Teams can collect many behavioral metrics without knowing what a good experience means. HEART pairs broad experience dimensions with a goals–signals–metrics process, helping teams connect product telemetry and research measures to intended user outcomes.

## When to use it

Use HEART when defining or revising experience metrics for a product, journey, or feature, especially when several teams need a shared measurement vocabulary. It works for both large-scale telemetry and mixed-method measurement, provided the scope and users are explicit.

## How it works

1. Define the product area, user group, and decision the measurement system should support.
2. Choose the HEART categories that matter; do not force a metric into every category.
3. Write a user-centered goal for each selected category before choosing data.
4. Identify observable signals that would indicate progress or regression toward each goal.
5. Operationalize a small set of metrics from those signals, adding guardrails and qualitative evidence where numbers are incomplete.
6. Review whether the metrics still represent the goal as the product and user behavior evolve.

## A practical example

For a collaborative editor, a team chooses Happiness, Adoption, and Task success. It combines perceived ease ratings, the share of eligible teams that try co-editing, completion of a shared-review task, and observed collaboration failures. It avoids using raw session duration because longer sessions may indicate either engagement or difficulty.

## Where it breaks

HEART supplies categories and a process, not universal metric definitions or target values. Engagement and retention may be inappropriate for occasional or problem-solving products. Instrumentation can miss context, and optimizing a single HEART measure can still harm accessibility, trust, or broader outcomes.

## Common mistakes

- Selecting metrics before writing goals and signals.
- Measuring all five categories when only some fit the product.
- Assuming more engagement always means a better user experience.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/heart-framework/#visualization-heart-framework>)

## Sources

1. [Measuring the User Experience on a Large Scale](<https://research.google/pubs/measuring-the-user-experience-on-a-large-scale-user-centered-metrics-for-web-applications/>) — Google Research · Original research paper
2. [Measuring the user experience on a large scale](<https://dl.acm.org/doi/10.1145/1753326.1753687>) — Association for Computing Machinery · Peer-reviewed conference paper
3. [The HEART framework for UX metrics](<https://kerryrodden.com/heart/>) — Kerry Rodden · Creator guidance

## Related topics

- [Task Success Rate](<https://wiki.soroush.uk/topic/task-success-rate/>)
- [Time on Task](<https://wiki.soroush.uk/topic/time-on-task/>)
- [System Usability Scale \(SUS\)](<https://wiki.soroush.uk/topic/system-usability-scale/>)
