Can we Measure Delight?
Delight is measurable; but not just in numbers.
When it comes to building successful products, most teams know how to track things like adoption, engagement, or retention. Those are tangible metrics you can pull straight from analytics dashboards.
But what about something less tangible, like whether your users are happy?
Happiness is at the core of what makes a product delightful. It’s also the hardest part to measure. And yet, if you don’t track it, you risk missing the emotional connection that turns satisfied users into loyal advocates.
This is where the HEART framework, developed by Google’s UX researchers, comes in. It provides a structured way to combine hard data with emotional insights, so you can track progress toward true product delight.
The HEART Framework
The HEART framework organizes product success metrics into five dimensions:
Happiness – User satisfaction and emotional connection.
Engagement – How actively and meaningfully users interact with your product.
Adoption – How many new users become active users.
Retention – How many users continue using your product over time.
Task Success – How efficiently users can achieve their goals.
Together, these dimensions help you determine whether your product not only solves problems, but also does so in a way that feels intuitive, rewarding, and aligned with user values.
Happiness: The Hardest — Yet Most Important — Metric
Happiness measures user satisfaction and emotional connection. It answers the question:
“Do users feel positive about their experience?”
Unlike adoption or retention, which are visible in your data, happiness requires asking users directly. That makes it subjective, but also the clearest lens on product delight.
The main way to capture happiness is through surveys. Let’s explore the most common ones.
NPS: Capturing Long-Term Loyalty
The Net Promoter Score (NPS) asks:
“How likely are you to recommend our product/service to a friend or colleague?”
Responses fall into three categories:
Promoters (9–10): Loyal advocates
Passives (7–8): Neutral users
Detractors (0–6): Unhappy users
Formula: NPS = % Promoters − % Detractors
NPS highlights systemic issues that affect long-term loyalty. However, it’s less effective for diagnosing specific pain points or gauging product delight in the short term.
CSAT: Pinpointing Tactical Pain Points
The Customer Satisfaction Score (CSAT) zooms in on specific actions or features.
Typical question: “How satisfied were you with [specific feature/interaction]?”
Responses are usually scored 1–5.
Formula: CSAT = (Positive Responses ÷ Total Responses) × 100
CSAT is great for spotting friction points in your product. It’s more tactical than NPS, but when combined, the two give you both strategic (NPS) and tactical (CSAT) insight.
HaTS: Tracking Happiness Over Time
During my time at Google, I found a more powerful tool for tracking happiness: HaTS (Happiness Tracking Surveys).
Unlike NPS or CSAT, which provide snapshots, HaTS is an in-product survey designed to track user sentiment continuously over time.
NPS measures overall brand loyalty.
CSAT measures satisfaction with specific features.
HaTS tracks happiness trends linked to product changes.
Imagine launching a new feature in Google Meet. HaTS pops up right after the user interacts with it, asking:
“How satisfied are you with this feature?”
“How easy was it to complete your task?”
By repeating this over weeks and months, HaTS shows how happiness evolves. Did delight increase after your change? Did it fade due to habituation? That trend data is invaluable.
How to Implement HaTS
Define your measurement goals – Are you measuring overall satisfaction, feature-specific happiness, or emotional connection?
Design survey questions – Use both quantitative (scores) and qualitative (open-ended) questions. Keep them specific.
Choose your frequency – HaTS uses random sampling to avoid fatigue. Typically, users are only asked once every few months.
Analyze and act – Track trends across demographics and markets, and always combine HaTS insights with other HEART metrics for context.
All you need to know to measure delight is in Product Delight book.
It’s nice to know what users are feeling, but don’t you think popping up surveys all the time will negatively affect user happiness?