Principles of Product Management: HEART Framework (Happiness, Engagement, Adoption, Retention, Task Success)

HEART Framework (Happiness, Engagement, Adoption, Retention, Task Success)

HEART Framework: Study Guide

What This Is

The HEART Framework (Happiness, Engagement, Adoption, Retention, Task Success) is a user-centric metrics framework developed by Google to measure product health beyond vanity metrics (e.g., DAU, page views). It helps PMs quantify user experience and align product decisions with long-term value—not just growth. Unlike AARRR (which focuses on funnel stages), HEART zooms in on user sentiment, behavior, and outcomes to answer: "Are we building something people truly love and use effectively?"

Real-world example: A fintech app (e.g., Revolut) redesigned its budgeting feature using HEART. They tracked: - Happiness (NPS after using the feature), - Engagement (weekly sessions per user), - Adoption (% of users who set up a budget), - Retention (returning after 30 days), - Task Success (time to complete a budget review). The data revealed that while adoption was high, task success was low (users struggled to categorize transactions). This led to a simplified UI and in-app tutorials, which improved retention by 22% and NPS by 15 points.

Key Terms & Frameworks

• HEART Framework: A 5-pillar metrics system to measure user experience:
• Happiness (subjective satisfaction, e.g., NPS, CSAT),
• Engagement (frequency/intensity of use, e.g., sessions/week, time spent),
• Adoption (new users or feature uptake, e.g., % of users who try a feature),
• Retention (repeat usage over time, e.g., Day 7/30 retention),
• Task Success (efficiency/effectiveness, e.g., completion rate, error rate).
• Goals-Signals-Metrics (GSM): A 3-step process to operationalize HEART:
• Goal (what you want to achieve, e.g., "Improve onboarding"),
• Signal (user behavior that indicates progress, e.g., "Users complete profile setup"),
• Metric (quantifiable measure, e.g., "% of users who finish onboarding in <2 mins").
• NPS (Net Promoter Score): "How likely are you to recommend [product] to a friend?" (0–10 scale). Detractors (0–6), Passives (7–8), Promoters (9–10). Formula: % Promoters – % Detractors.
• DAU/MAU Ratio: Daily Active Users / Monthly Active Users (measures stickiness; 20%+ is strong).
• Retention Rate: % of users who return after X days (e.g., Day 7 retention = users active on Day 7 / users active on Day 0).
• Feature Adoption Rate: # of users who use a feature / # of total users (tracked over time).
• Task Success Rate: % of users who complete a task without errors (e.g., checkout completion rate).
• Time-on-Task: Average time to complete a key action (e.g., "Add to cart"-"Purchase").
• HEART vs. AARRR:
• HEART = User experience (qualitative + quantitative).
• AARRR = Growth funnel (acquisition-revenue).
• Leading vs. Lagging Indicators:
• Leading (predictive, e.g., "Time to first key action"-future retention).
• Lagging (historical, e.g., "Churn rate"-past behavior).
• ICE Score: Impact × Confidence × Ease (prioritization framework; higher score = higher priority).

Step-by-Step Process Flow

How to Apply HEART in a Real Product Scenario

1. Define the Goal
2. Start with a product objective (e.g., "Improve mobile app onboarding").

3. Use GSM to break it down:

   • Goal: Increase new user activation.
   • Signal: Users complete profile setup and make their first transaction.
   • Metric: % of users who complete onboarding in <3 mins and make a transaction within 24 hours.

4. Map Metrics to HEART Pillars

5. Happiness: NPS after onboarding, CSAT survey ("How easy was onboarding?").
6. Engagement: Sessions in first 7 days, time spent in-app.
7. Adoption: % of users who complete onboarding, % who try a key feature (e.g., "Add payment method").
8. Retention: Day 7 retention rate, % of users who return after 30 days.

9. Task Success: Onboarding completion rate, error rate (e.g., failed payment attempts).

10. Set Baselines & Targets

11. Measure current performance (e.g., "Current onboarding completion rate = 45%").
12. Set ambitious but realistic targets (e.g., "Increase to 65% in 3 months").

13. Use A/B tests to validate changes (e.g., "Simplified onboarding flow vs. control").

14. Instrument & Track

15. Tools: Mixpanel (behavioral), SurveyMonkey (NPS/CSAT), Amplitude (retention), Hotjar (task success).

16. Example query: "Show me the % of users who complete onboarding AND make a transaction within 24 hours, segmented by device (iOS/Android)."

17. Analyze & Iterate

18. Look for correlations (e.g., "Users who complete onboarding in <2 mins have 30% higher Day 7 retention").
19. Identify drop-off points (e.g., "60% of users abandon at the 'Add payment method' step").

20. Prioritize fixes using ICE Score (e.g., "Simplify payment flow" = Impact 8, Confidence 7, Ease 6-Score = 336).

21. Communicate Insights

22. Stakeholder-friendly format: 1-pager with:
    • Current state (baselines),
    • Goal (targets),
    • Key findings (e.g., "Task success is the bottleneck"),
    • Recommendations (e.g., "Add a guided tour for payment setup").

Common Mistakes

PM Interview / Practical Insights

What Interviewers Probe

1. "How would you use HEART to measure the success of [feature X]?"
2. Trap: Answering with generic metrics (e.g., "Track DAU").

3. Strong Answer:

   • "For a new social media ‘Stories’ feature, I’d focus on:
   • Adoption (% of users who post a Story in Week 1),
   • Engagement (avg. views per Story, sessions/week),
   • Retention (Day 7 retention of Story posters),
   • Task Success (completion rate for posting a Story),
   • Happiness (NPS of Story users vs. non-users).*
   • I’d use GSM to define signals (e.g., ‘Users who post >3 Stories in Week 1 are 2x more likely to retain’)."

4. "HEART vs. AARRR: When would you use each?"

5. Trap: Saying they’re interchangeable.

6. Strong Answer:

   • "Use HEART for product health (e.g., ‘Is our onboarding delightful?’) and AARRR for growth (e.g., ‘How do we acquire more users?’).
   • Example: If we’re launching a new checkout flow, I’d use:
   • HEART to measure Task Success (completion rate) and Happiness (NPS),
   • AARRR to measure Activation (first purchase) and Revenue (AOV)."*

7. "A feature increases Engagement but hurts Happiness. How do you decide?"

8. Trap: Defaulting to "Engagement is more important."

9. Strong Answer:

   • "I’d dig into the ‘why’ with qualitative data (e.g., user interviews, NPS comments).
   • Example: If a ‘Dark Mode’ toggle increases sessions/week (Engagement) but lowers NPS (Happiness) because it’s buggy, I’d:
   • Fix the bugs (prioritize Task Success),
   • A/B test a smoother implementation,
   • Monitor if Engagement stays high and Happiness improves.*
   • Long-term, Happiness drives Retention, which is more valuable than short-term Engagement spikes."

10. "How do you balance HEART metrics with business goals (e.g., revenue)?"

11. Trap: Ignoring business metrics entirely.
12. Strong Answer:
    • "HEART and business metrics should reinforce each other. Example:
    • Goal: Increase subscription conversions.
    • HEART metrics:
      • Adoption (% of users who start a trial),
      • Task Success (trial completion rate),
      • Happiness (NPS of trial users).
    • Business metrics:
      • Conversion rate (trial-paid),
      • LTV (lifetime value of subscribers).
    • If Adoption is high but conversions are low, I’d investigate Task Success (e.g., ‘Are users confused about pricing?’) or Happiness (e.g., ‘Do they see value in the trial?’)."

Quick Check Questions

1. Scenario: Your team wants to add a gamified "streaks" feature to a meditation app. It increases Engagement (daily sessions) but lowers NPS (users say it feels "stressful"). How do you decide?

2. Answer: Run a qualitative deep dive (interviews, NPS comments) to understand the ‘why’. If users feel pressured, test a less aggressive version (e.g., "weekly streaks") and measure Happiness + Retention. Long-term retention > short-term engagement spikes.

3. Scenario: You’re launching a new AI-powered resume builder. Which 2 HEART pillars would you prioritize, and what metrics would you track?

4. Answer: Prioritize Task Success (e.g., % of users who generate a resume in <5 mins, error rate) and Adoption (e.g., % of users who try the feature in Week 1). Why? If users can’t complete the task (Task Success) or don’t try it (Adoption), other metrics don’t matter.

5. Scenario: Your Day 7 retention is 30%, but your NPS is 50. What’s your next step?

6. Answer: Segment the data to find discrepancies (e.g., "Do power users retain at 50% but have NPS 70?"). Then, interview churned users to understand why they left (e.g., "Did they not see value?"-Improve Task Success or Happiness).

Last-Minute Cram Sheet

1. HEART = Happiness, Engagement, Adoption, Retention, Task Success – measures user experience, not growth.
2. GSM (Goals-Signals-Metrics) – bridge between product goals and quantifiable metrics.
3. Happiness = NPS/CSAT (qualitative); Engagement = sessions/time spent (quantitative).
4. Adoption = % of users who try a feature; Retention = % who return after X days.
5. Task Success = completion rate + time-on-task (e.g., checkout flow success).
6. HEART-AARRR – HEART = user experience, AARRR = growth funnel.
7. Always segment data (e.g., new vs. returning users) – averages lie.
8. Prioritize 1–2 HEART pillars per initiative (e.g., "Onboarding = Adoption + Task Success").
9. Leading indicators (e.g., "Time to first key action") predict future retention.
10. High Engagement-Happy Users – check NPS to confirm.