> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/testing/heart-framework.md).

# Heart Framework

The HEART framework is a high-level system created by researchers at Google to help teams measure the quality of the user experience on a large scale. 

Unlike simple metrics that only look at how many people visit a website, this method focuses on the specific emotional and behavioural aspects of how users interact with a product. It allows designers and product managers to choose the right data points to track, ensuring that they are measuring what actually matters for long-term success rather than just vanity numbers.

The name itself is an acronym for five key categories: 

1. Happiness
2. Engagement
3. Adoption
4. Retention
5. Task Success

Happiness measures user satisfaction through surveys or ratings, while Engagement looks at how often and how deeply people use the product. Adoption and Retention track how many new users start using a feature and how many of them keep coming back over time. Finally, Task Success focuses on the efficiency and effectiveness of the design, such as how long it takes a person to complete a specific action or how many errors they make along the way.

To make this framework practical, teams typically define specific goals, signals, and metrics for each of the five categories. For example, a goal for Happiness might be that users find the app easy to use, the signal would be positive ratings in the app store, and the metric would be the average star rating over a month. This structured approach helps a team stay aligned and provides a clear, data-driven story about whether their design changes are truly improving the lives of their users.

#### Further Reading

{% embed url="<https://www.heartframework.com/>" %}

{% embed url="<https://www.interaction-design.org/literature/article/google-s-heart-framework-for-measuring-ux?srsltid=AfmBOooZX-zIV9W1BtCEwJdvv5JwuH_cq_aSyRlVJGHxhKeMZv0BuyCw>" %}

{% embed url="<https://uxdesign.cc/googles-heart-framework-choosing-the-right-metrics-for-your-product-112bd7300d55>" %}

{% embed url="<https://www.productplan.com/glossary/heart-framework/>" %}

{% embed url="<https://uxplanet.org/differences-in-the-the-heart-framework-for-b2b-b2c-designs-de2a2d18bcd9>" %}

#### Further Viewing

{% embed url="<https://www.youtube.com/watch?v=ulQ3NKPBCt0>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.designreference.xyz/ux-methods/testing/heart-framework.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.