HEART Framework: How Every Product Manager Can Measure UX at Scale
The HEART Framework is a UX measurement methodology developed at Google by Kerry Rodden. It organizes user experience metrics into five categories—Happiness, Engagement, Adoption, Retention, and Task Success. A product manager uses a Goals-Signals-Metrics process within each category to translate broad product objectives into quantifiable, actionable metrics that drive data-informed decisions across the product lifecycle.
Overview
The HEART Framework was created by Kerry Rodden and the Google research team to solve a persistent challenge: how do you measure user experience at scale in a way that is both meaningful and actionable? Before HEART, many product teams relied on vanity metrics or a hodgepodge of analytics that failed to connect user sentiment to business outcomes. HEART provides a structured vocabulary—Happiness, Engagement, Adoption, Retention, and Task Success—that gives every product manager a comprehensive lens through which to evaluate product health.
What makes HEART especially powerful is its companion process: Goals-Signals-Metrics (GSM). Rather than jumping straight to dashboard numbers, GSM forces teams to first articulate what success looks like for a given feature or product (Goals), what user behaviors would indicate progress toward that goal (Signals), and only then which specific metrics to track (Metrics). This prevents the common anti-pattern of measuring what's easy rather than what matters.
For a product manager, the HEART Framework serves multiple roles. It's a strategic alignment tool during roadmap planning, a communication bridge in cross-functional meetings, and a rigorous evaluation system during post-launch reviews. Whether you're an associate product manager defining your first KPIs or a senior product manager presenting quarterly results to leadership, HEART provides the structure to ensure that user-centered measurement is embedded in every decision.
The framework is intentionally modular. Not every product or feature requires all five HEART categories. A product manager should select the dimensions most relevant to their current goals—for instance, a new feature launch might prioritize Adoption and Task Success, while a mature product might focus on Retention and Happiness. This flexibility is what has made HEART a staple methodology at Google and across the broader product management community.
How It Works
Step 1: Choose the Relevant HEART Categories
Not every HEART dimension applies to every product or feature. Begin by selecting which of the five categories—Happiness, Engagement, Adoption, Retention, Task Success—are most relevant to your current product context. A new onboarding flow might prioritize **Adoption** and **Task Success**, while a mature social product would focus on **Engagement** and **Retention**. As a product manager, resist the urge to track everything; focus creates clarity.
Step 2: Define Goals for Each Category
For each selected HEART category, articulate a clear, qualitative goal. Goals should describe the desired user outcome, not a metric. For example, under Happiness: *'Users feel confident and satisfied completing their first project.'* Under Retention: *'Users return weekly because they find ongoing value.'* Write goals collaboratively with your design, engineering, and research partners to ensure alignment.
Step 3: Identify Signals That Indicate Progress
Signals are observable user actions or attitudes that would suggest you're moving toward your goal. For a Happiness goal, a signal might be *'users rate their experience 4+ stars in the in-app survey.'* For an Engagement goal, a signal could be *'users interact with the core feature at least 3 times per session.'* List multiple candidate signals per goal before narrowing down.
Step 4: Translate Signals into Quantifiable Metrics
Convert each signal into a specific, measurable metric with a clear data source. Examples: *Average satisfaction score (from quarterly NPS survey)*, *Weekly active users / Monthly active users ratio (from product analytics)*, *Percentage of new users completing onboarding within 24 hours (from event tracking)*. Each metric should be unambiguous enough that any team member can compute it independently.
Step 5: Instrument and Baseline Your Metrics
Work with engineering to ensure the necessary event tracking, survey triggers, and data pipelines are in place. Collect baseline measurements before making product changes. A product manager should document the baseline, the data source, and the measurement cadence (daily, weekly, monthly) for each metric. Without baselines, you cannot measure impact.
Step 6: Build a HEART Dashboard
Create a centralized dashboard that visualizes your HEART metrics in one place. Organize it by HEART category so stakeholders can quickly assess product health across all dimensions. Include trend lines, targets, and annotations for major releases. Tools like Looker, Amplitude, or even a well-structured spreadsheet work—what matters is accessibility and regular review.
Step 7: Review, Interpret, and Act
Schedule regular review cadences—weekly for fast-moving products, bi-weekly or monthly for mature ones. During reviews, don't just read numbers; interpret them. If Adoption is rising but Retention is falling, you're acquiring users who don't find lasting value. Use HEART insights to prioritize your roadmap, design experiments, and communicate product strategy to leadership.
Step 8: Iterate on Your Goals-Signals-Metrics
HEART is not a set-it-and-forget-it framework. As your product evolves, revisit your GSM mappings quarterly. Goals shift as you move from growth to maturity. Signals become irrelevant as user behavior changes. Metrics need recalibration as you hit or miss targets. A disciplined product manager treats the HEART Framework as a living system, not a static artifact.
When to Use
- When launching a new product or major feature and you need a comprehensive measurement plan that covers both attitudinal and behavioral user experience dimensions.
- When your product team has an abundance of analytics data but lacks a coherent framework to prioritize which metrics actually matter for user-centered decision-making.
- When aligning cross-functional stakeholders—engineering, design, marketing, and leadership—around a shared definition of product success that goes beyond revenue or growth metrics.
- When preparing for a product manager interview or quarterly business review and you need a structured way to present how your product is performing across multiple UX dimensions.
- When transitioning from a feature-shipping mindset to an outcomes-driven culture and you need a framework that forces goal articulation before metric selection.
When Not to Use
- When you're in the earliest discovery or ideation phase and don't yet have a live product or prototype generating user data—HEART requires observable signals to be meaningful.
- When the decision at hand is purely a business model or pricing question with no direct UX component; financial frameworks like unit economics analysis would be more appropriate.
- When you only need to track a single, well-understood metric (e.g., conversion rate for an A/B test)—HEART's breadth adds unnecessary overhead for narrowly scoped experiments.
- When your team lacks the instrumentation or analytics infrastructure to collect the signals required; invest in event tracking and data pipelines first before adopting HEART.
Skills in This Method
Measuring Adoption Rates and Task Success for New Features
Methods for tracking new user onboarding funnels, feature adoption curves, and task-completion rates to evaluate Adoption and Task Success.
Tracking Engagement and Retention Metrics at Scale
How to instrument and analyze behavioral data—session frequency, feature usage, and cohort retention—to measure the Engagement and Retention dimensions.
Measuring User Happiness Through Surveys and Satisfaction Scores
Techniques for designing and deploying user satisfaction surveys, NPS, and sentiment analysis to quantify the Happiness dimension of HEART.
Defining Goals, Signals, and Metrics with the HEART Framework
How to use the Goals-Signals-Metrics (GSM) process to translate each HEART dimension into measurable, actionable product metrics.
Running HEART Framework Workshops with Cross-Functional Teams
A facilitation guide for leading collaborative sessions where designers, engineers, and PMs align on HEART goals, signals, and success metrics.
Presenting HEART Metrics in Product Manager Interviews
How to articulate UX measurement strategies using the HEART framework when answering product manager interview questions about metrics and impact.
Building HEART Metric Dashboards for Product Teams
Step-by-step guidance on creating live dashboards that visualize all five HEART dimensions to inform roadmap decisions and stakeholder reviews.