The metric model that turns UX quality into something a product team can actually act on

The HEART Framework is a UX measurement model developed by Kerry Rodden, Hilary Hutchinson, and Xin Fu at Google, published in 2010. It gives teams a structured way to evaluate user experience across five categories: Happiness, Engagement, Adoption, Retention, and Task Success.

The problem it solves is real. Most product teams measure engagement (DAU, sessions, clicks) and some track retention, but rarely tie these back to whether users actually find the product useful or satisfying. HEART creates a shared vocabulary for UX quality — one that maps naturally to the metrics product managers, engineers, and designers already talk about.

You don't have to use all five dimensions. The framework is designed to be selective — choose the ones that match your current product question.

Each letter maps to a distinct aspect of user experience:

• Happiness — Subjective satisfaction. Typically measured through NPS, CSAT, or post-session surveys. Captures the emotional side of using a product.
• Engagement — Frequency, depth, or breadth of interaction. Sessions per week, feature usage rates, content interactions.
• Adoption — New users picking up a feature or reaching a milestone. Especially relevant after a launch or onboarding flow change.
• Retention — Whether users come back. Churn rate, return rate, long-term stickiness.
• Task Success — Whether users complete what they set out to do. Error rates, completion rates, time-on-task.

A common adaptation — especially at larger product orgs — is the Goals-Signals-Metrics (GSM) process that pairs with HEART. For each dimension you track:

1. Goal — What does success look like?
2. Signal — What behaviour would indicate that goal is being met?
3. Metric — How do you measure that signal?

This turns an abstract framework into something you can wire up in your analytics tooling.

Page views, total signups, and time-on-site are easy to measure and easy to misread. They go up when things look good on the surface and stay flat while real problems quietly compound.

HEART pushes teams to ask a sharper question: what would success actually look like for this feature? A long average session duration isn't necessarily positive — it could mean users are confused. HEART asks you to pair engagement with task success so you know which is which.

Teams that use it well define their metrics before launching a feature. When you agree on what signals matter at the start, post-launch analysis becomes a conversation about evidence rather than a fight over interpretation.

The most common mistake is treating HEART as a dashboard template rather than a thinking tool. Filling in all five dimensions with whatever data is easy to pull doesn't make for a useful measurement strategy — it just creates noise.

The second mistake: over-indexing on Task Success at the expense of Happiness. You can design a flow that users complete efficiently but still find tedious or stressful. In products people use daily, both dimensions matter.

If you're trying to build a more rigorous approach to measuring product experience, an UX Research engagement can help you identify which dimensions are most meaningful for your specific product context and set up the signals worth tracking.