Subscribe to the Growth Analytics newsletter
By subscribing you agree to our newsletter's privacy policy.
You've been subscribed to the Growth Analytics newsletter
Oops! Something went wrong while submitting the form.

HEART Framework


Great for product teams that want to prioritize usability.

What is the HEART Framework

The HEART framework, conceptualized by a team at Google, marks a paradigm shift in user experience (UX) metrics. Historically, product metrics gravitated towards quantitative data — clicks, page views, time spent. However, this approach often neglected the qualitative aspects of user interaction. The HEART framework emerged as a response, aiming to bridge this gap. It's a holistic tool that considers both the tangible and intangible facets of user experience.

This framework's genesis lies in the recognition that traditional metrics, while robust, often failed to encapsulate the full spectrum of user experience. For example, a product might show high engagement metrics but still suffer from poor user satisfaction. The HEART framework was Google's answer to this discrepancy, representing a more nuanced and user-centered approach to metrics.

What Does HEART Stand For?

HEART is an acronym where each letter represents a distinct aspect of user experience.This segmentation allows for a comprehensive analysis of a product from multiple angles, ensuring that no key aspect of the user experience is overlooked:

  • Happiness: Subjective user satisfaction, often gathered through surveys and feedback.
  • Engagement: The level of user involvement, indicated by frequency, intensity, or depth of interaction.
  • Adoption: The number of new users starting to use the product or feature.
  • Retention: The rate at which existing users continue to use the product.
  • Task Success: Effectiveness and efficiency of task completion, including metrics like error rate and time to task completion.

Examples of HEART Metrics per Category

These metrics are not exhaustive but exemplify how the HEART framework operationalizes abstract concepts into tangible, measurable data.

Happiness Metrics

  • App Rating
  • Survey results for features
  • Net Promoter Score (NPS)
  • Customer Satisfaction Score (CSAT)

Engagement Metrics

  • Breadth, depth and frequency of feature usage
  • Daily Active Users (DAU)
  • Time spent on the product
  • Conversions


  • Feature adoption rate
  • Number of new users over a specific period
  • Adoption rate of new features

Retention Metrics

  • Day 1, 7, 30 Retention Rate
  • Week 1, Month1 Retention Rate
  • Engagement Retention, Customer Retention, Revenue Retention
  • DAU/MAU Ratio (Daily Active Users ÷ Monthly Active Users)
  • Churn rate
  • Session frequency

Task Success Metrics

  • Completion rate of critical tasks
  • Average time taken for task completion
  • Error rate per user

Strengths and Weaknesses of HEART


  • User-Centric: Puts user experience at the forefront, providing a holistic view of product interaction.
  • Measures Satisfaction: Covers metrics on user sentiment about the product and features, which many other frameworks lack.


  • Not for growth: Good for measuring features and UX of the product, but doesn’t cover critical metric categories for growth, such as monetization and activation.
  • Subjectivity in Happiness: Measuring happiness can be subjective and also influenced by external factors.

In conclusion, the HEART framework's unique strength lies in its comprehensive and user-centric approach. However, when compared to other frameworks like LAMERS and AARRR, it falls short in areas such as revenue generation and lead acquisition strategies. These comparative strengths and weaknesses highlight the importance of selecting a framework that aligns with specific business goals and operational capacities.

Shoin Wolfe
Author of Growth Analytics