Definition
A user-experience metrics framework from Google. Introduced by Kerry Rodden, Hilary Hutchinson, and Xin Fu in their 2010 paper. That measures five dimensions: Happiness, Engagement, Adoption, Retention, and Task success. For each dimension, teams define Goals, Signals, and Metrics. PMs use HEART to establish a balanced scorecard of UX quality that goes beyond a single vanity metric like NPS. Teams often pair HEART with the AARRR pirate metrics funnel: AARRR tracks business-level health while HEART zooms into user-experience quality at each stage. The Product Analytics Handbook covers how to select and combine metric frameworks for different product contexts.
Why It Matters for Product Managers
Understanding heart framework is critical for product managers because it directly influences how teams prioritize work, measure progress, and deliver value to users. PMs use HEART to establish a balanced scorecard of UX quality that goes beyond a single vanity metric. Without a clear grasp of this concept, PMs risk making decisions based on assumptions rather than evidence, which can lead to wasted engineering effort and missed market opportunities.
How It Works in Practice
Teams typically implement this framework by following a structured process:
- Introduce. Share the framework with the team, explaining the problem it solves and when it is most useful.
- Calibrate. Run a practice session with a small set of real examples so the team develops a shared understanding of how to apply it.
- Apply. Use the framework on actual backlog items, roadmap decisions, or discovery questions during a dedicated working session.
- Review. After a cycle (sprint or quarter), evaluate whether the framework produced better outcomes and adjust how the team uses it.
The goal is not to follow heart framework dogmatically but to use it as a thinking tool that brings structure to decisions that would otherwise rely on gut feel.
Common Pitfalls
- Applying the framework mechanically without understanding the reasoning behind each step.
- Using the framework as a substitute for product judgment rather than as an input to decisions.
- Skipping calibration sessions, which causes inconsistent scoring or categorization across the team.