At a Glance: Why UX Needs Its Own Measurement Framework
Google's HEART framework, developed by Kerry Rodden, Hilary Hutchinson, and Xin Fu from Google's UX Research team in 2010, is the industry standard for measuring user experience quality at scale. While AARRR covers growth funnels and OKRs align business outcomes, HEART answers a different question: is the product interface actually easy, pleasant, and effective to use? By mapping UX metrics across five key dimensions—Happiness, Engagement, Adoption, Retention, and Task Success—product teams can identify usability blocks that quietly cause user churn.
The 5 HEART Dimensions
Happiness captures the attitudinal dimension—how users perceive their interaction with your software. Typically measured via NPS, CSAT, app store ratings, and micro-surveys, Happiness is a critical metric for brand sentiment.
Lagging Indicator Warning: Happiness is a lagging indicator. A user experiencing growing friction may still write a positive review because of past utility, only to churn abruptly when a simpler alternative emerges. attitudinal data must always be paired with behavioral telemetry (Engagement and Task Success).
Metric ideas: Post-onboarding CSAT · App Store rating · Post-transaction NPS · In-app smileys
Indian benchmarks: App Store rating ≥ 4.3/5 · CSAT ≥ 82% · NPS ≥ 45 for leading Consumer/Fintech products
Engagement monitors user behavior over time. Instead of simple signups, it tracks active, recurring habits. A common mistake is looking only at overall app DAU/MAU; HEART encourages you to look at feature-level engagement. If you ship a new dashboard widget, are users returning to it weekly, or is it a one-time novelty?
Metric ideas: Weekly Active Users (WAU) · Average session length · Features used per session · Daily notification CTR
Benchmarks: Daily-use consumer apps DAU/MAU: 0.35+ · Fintech/Wealth apps WAU/MAU: 0.25+ · EdTech WAU/MAU: 0.30+
Adoption measures the transition from non-user to user. It maps how successfully users cross the threshold into a new feature. For instance, when an Indian payments app launches "Credit on UPI," adoption tracks what percentage of eligible active users successfully link their credit line in the first 30 days. High adoption with low retention indicates a feature with good marketing but poor real utility.
Metric ideas: Activation rate · First-time transaction conversion · % of users setting up a recurring auto-pay mandate
Benchmarks: Primary feature adoption (D30): 40%+ · Secondary feature adoption (D30): 15% - 25%
Retention measures how many users continue to perform key actions over time. While general product retention is a standard metric, HEART focuses on *feature-specific retention*. If users adopt your personal finance manager, do they return to log expenses the following month? Feature retention curves are the ultimate truth detector for UX design changes.
Metric ideas: Feature re-use rate (used ≥3 times in D30) · Cohort retention at Day 7/30/90 · Churn rate
Key target: Day 30 feature retention should level off above 20% to confirm the feature has found its "retained core" of users.
Task Success is the most granular, directly actionable dimension. It measures the efficiency and error rates of specific interaction flows. This is highly critical in Indian digital environments, where complex flows like UPI bank linking, Aadhaar e-Sign, and multi-step KYC are vulnerable to network latency and UI confusion.
Metric ideas: Checkout completion rate · KYC success rate · Form validation error rate · Time-to-complete transaction
Indian benchmarks: UPI transaction success rate ≥ 92% (NPCI benchmark) · KYC single-session completion rate ≥ 70% · Checkout drop-off < 15%
The Goals → Signals → Metrics (GSM) Process
The core of the HEART framework is the **Goals → Signals → Metrics (GSM)** process. Rather than tracking random analytics, GSM forces you to align metrics with specific user experience goals.
1. Goal
What does success look like for this UX dimension?
"Users complete KYC quickly and feel secure sharing sensitive ID cards"
"First-time investors set up a monthly SIP without feeling confused by mutual fund jargon"
2. Signal
What user behaviors indicate the goal is met?
User completes the camera photo capture on the first attempt without retrying or opening support chat
User navigates to the SIP setup screen and completes the mandate setup in under 3 minutes
3. Metric
How do we measure the signal quantitatively?
KYC single-session success rate (%) + support tickets tagged "KYC OCR issues" per 1,000 signups
Average time-on-task for SIP setup + mandate setup conversion rate (%)
Worked Example: HEART Worksheet for an Indian Payments App
Here is how a leading Indian UPI-based payments app applies the HEART framework to audit and optimize its user onboarding and activation flow:
| Dimension |
Goal |
Signal |
Metric |
Current |
Target |
| Happiness |
Users feel the onboarding is fast, secure, and straightforward. |
High post-onboarding CSAT surveys; positive reviews highlighting the simplicity of setup. |
CSAT score (1-5 scale) shown immediately after the first successful transaction. |
74% |
85%+ |
| Engagement |
New users establish a regular payment habit in their first week. |
Multiple app opens in week 1; scanning merchant QR codes for daily offline transactions. |
Average transactions per active user in D7; WAU/MAU ratio of the onboarding cohort. |
2.4 |
4.0+ |
| Adoption |
New users complete KYC registration and link their active bank accounts. |
Reaching the "KYC approved" status and successfully making a bank penny-drop check. |
Bank linking success rate (% of app installs that link a bank account within 24 hours). |
52% |
68%+ |
| Retention |
Users continue to use the app for payments month after month. |
Making at least one bill payment or peer-to-peer transfer in days 25–35. |
Day 30 cohort transacting retention rate (%). |
32% |
45%+ |
| Task Success |
Users complete the Aadhaar OTP and bank linking flows without timeouts. |
Zero OTP retries; completing the bank SMS verification loop on the first attempt. |
Single-session bank verification success rate (%); average time-on-task (seconds). |
61% |
80%+ |
HEART vs. AARRR: Rationale for Coexistence
Product managers often ask whether they should use HEART or AARRR. The answer is **both**, as they measure different aspects of the product lifecycle:
- AARRR (Funnel Mechanics): Tells you *where* you are losing users. (e.g., "We have a 45% drop-off at the KYC step").
- HEART (Interface Quality): Tells you *why* they are dropping off and how the interface design causes it (e.g., "The Aadhaar photo upload fails because the capture target does not guide the user, leading to poor Task Success").
AARRR acts as your macro growth diagnostic, while HEART provides micro-level usability diagnostics to seal those funnel leaks.
Step-by-Step Checklist: Implementing HEART GSM
- [ ] Select the Scope: Decide whether you are auditing a single critical flow (e.g., signup, checkout) or the entire product.
- [ ] Hold a GSM Workshop: Bring Product, Design, Engineering, and QA into a room. Brainstorm Goals, Signals, and Metrics for all 5 dimensions.
- [ ] Build Telemetry Hooks: Implement event tracking (e.g., tracking form validation errors, camera retries, and time-on-task).
- [ ] Set up a Dashboard: Visualize these metrics in a dedicated product analytics dashboard (e.g., PostHog, Mixpanel).
- [ ] Audit and Iterate: Monitor these metrics weekly. When Task Success rates drop, run qualitative usability tests to diagnose the friction.
Need a HEART Usability Audit?
We help Indian tech teams run HEART workshops, set up event telemetry, and optimize high-friction flows like KYC and checkout. Book a free session with us.
Book a Free Call