HEART combined with GSM is a powerful framework to quickly brainstorm and come up with the metrics most relevant for your product or feature at hand.
Frameworks are the mental scaffolding that help you make sense of complexity and focus your work. The actual job is not to memorize frameworks, but to know which one to apply when — and how to adapt it to the reality of your product and customers.
The trap is treating frameworks as checklists or silver bullets. They are tools to structure thinking, not substitutes for judgment.
This lesson covers three foundational frameworks every product manager uses regularly: HEART, AARRR, and Lean Canvas. Master these, and you can measure what matters, align teams, and build a roadmap grounded in evidence.
The HEART framework measures user experience quality
Google Ventures developed HEART to capture the multidimensional nature of user experience and product success. The acronym stands for:
| Metric | What it measures | How to measure |
|---|---|---|
| Happiness | User satisfaction and likelihood to recommend | User surveys, NPS |
| Engagement | Frequency and intensity of user interaction | Analytics (sessions, time) |
| Adoption | Percentage of users who start using the product or a feature | Analytics (activation rates) |
| Retention | Percentage of users who return over time | Analytics (cohort analysis) |
| Task success | How effectively users complete key tasks (speed, errors) | User testing, surveys |
Happiness is quantitative — you ask users directly how they feel. Net Promoter Score (NPS) is a common way to capture this, but simple satisfaction surveys work too.
Engagement answers: how much do users use your product? Google Analytics or Mixpanel reports sessions per user, time on site, or actions per session.
Adoption measures how many new users onboard successfully or start using a new feature. This is critical for growth and feature launches.
Retention tracks whether users keep coming back. A high retention rate signals a sticky product.
Task success is about usability — can users complete their goals efficiently and without frustration? This may require usability testing or detailed surveys.
The actual job is to pick the HEART metrics that align with your product goals. Not all apply equally to every product or feature.
GSM: Goals, Signals, Metrics — pairing with HEART
HEART alone is a framework for categories of metrics. To operationalize it, Google Ventures paired it with GSM: a way to turn goals into measurable signals and metrics.
- Goals are high-level objectives (e.g., "Increase checkout satisfaction").
- Signals are observable behaviors or attitudes that indicate progress toward goals (e.g., "App store rating").
- Metrics are quantifiable measurements of those signals (e.g., "Average app rating improves each month").
This layered approach helps teams brainstorm relevant metrics quickly and avoid getting lost in vanity metrics.
Product Analytics Review at a Series A e-commerce startup in Bangalore
You (PM): “Our HEART metrics show retention is flat, but adoption of the new one-click checkout is below our target.”
Data Analyst: “Engagement metrics indicate users drop off after adding items to cart but before checkout.”
Design Lead: “We could run usability tests to improve task success — maybe the checkout flow is confusing.”
You (PM): “Let's run surveys for happiness and usability tests for task success, then prioritize fixes based on impact.”
The team aligns around concrete metrics, not just gut feelings. This is HEART + GSM in action.
Choosing which metrics to prioritize when resources are limited
AARRR metrics analyze the customer lifecycle end to end
Also called Pirate Metrics, AARRR was proposed by Dave McClure of 500 Startups. It focuses on the user journey from discovery to advocacy:
| Stage | What it measures | Typical Metrics |
|---|---|---|
| Acquisition | How users find you and become aware | Traffic, mentions, cost per click |
| Activation | Users’ first satisfying experience | Signups, onboarding completion, first use |
| Retention | Users returning and staying engaged | DAU/MAU, churn rate |
| Revenue | How you monetize users | Conversion rate, average revenue per user |
| Referral | Users recommending your product to others | Viral coefficient, invites sent |
AARRR is a lifecycle funnel. You start with a large number of visitors (Acquisition), then filter down through Activation, Retention, Revenue, and Referral.
Each stage requires different tactics and metrics to optimize. The trap is focusing only on Acquisition or Revenue without improving Activation or Retention.
Consider this example from a typical Indian e-commerce startup:
| Stage | Metric | Value |
|---|---|---|
| Acquisition | Visitors per month | 1,000 |
| Activation | % who sign up or visit product | 70% (700 users) |
| Retention | % who return after first visit | 20% (140 users) |
| Revenue | % paying customers | 10% (14 users) |
| Referral | % who refer others | 10% |
This tells a story:
- The startup has decent Activation — people explore after landing.
- Retention is low — only 20% return, signaling a product or UX issue.
- Revenue conversion is a bottleneck — only 10% of those retained pay.
- Referral is modest, indicating room to improve word-of-mouth.
The team can prioritize retention improvements (e.g., better onboarding, engagement emails) and revenue conversion (e.g., pricing experiments).
Engines of growth: Sticky, Virality, Paid
Eric Ries described three engines that drive growth, mapping well onto AARRR:
- Sticky engine is about retention and engagement — keeping users coming back.
- Virality engine focuses on Referral — users inviting others.
- Paid engine centers on Revenue and Acquisition via paid marketing.
Most startups start with the sticky engine, then layer virality and paid growth.
Lean Canvas: a living plan for continuous experimentation
The Lean Canvas is a one-page business plan designed for startups and product teams to test hypotheses quickly. Unlike traditional business plans, it is a “living, breathing” document that evolves as you learn.
It has nine boxes:
| Box | Focus |
|---|---|
| Problem | Top 3 problems your product solves |
| Customer Segments | Who has these problems |
| Unique Value Proposition | What makes you different and valuable |
| Solution | Your product or feature concept |
| Channels | How you reach customers |
| Revenue Streams | How you make money |
| Cost Structure | Major costs involved |
| Key Metrics | The metrics you track to measure success |
| Unfair Advantage | What you have that competitors can’t easily copy |
The Lean Canvas encourages continuous validation:
- Run experiments to test problems, solutions, and value propositions.
- If an experiment fails, iterate or pivot before moving on.
- Keep updating key metrics as you learn what matters.
The trap is treating the Lean Canvas as a static document. It only works if you review and revise it frequently.
Product Strategy Workshop at a Bangalore SaaS startup
You (PM): “Our Lean Canvas shows acquisition through organic search and referrals as key channels.”
CEO: “But what if paid ads scale faster? Should we add that?”
You (PM): “Let's run a small paid campaign experiment next quarter and update the canvas based on results.”
Product Lead: “Our unfair advantage is proprietary client data — we should build features that leverage it.”
The team treats the Lean Canvas as a roadmap, not a fixed plan.
Balancing strategic planning with agility
Applying frameworks in the Indian product context
India’s diverse and fast-growing market demands that you adapt frameworks thoughtfully:
- Metrics matter, but so do qualitative signals. In many Indian startups, user surveys and interviews reveal pain points and satisfaction nuances not visible in raw analytics.
- Data quality varies. Analytics setups may be incomplete or inconsistent. Cross-check quantitative data with customer conversations.
- Startups evolve fast. The Lean Canvas must be revisited monthly or quarterly, not annually.
- User behavior is complex. Engagement patterns differ across regions, languages, and device types. Segment your metrics accordingly.
- Retention is king. Many Indian apps have high acquisition but poor retention. HEART and AARRR help you diagnose root causes and focus fixes.
For example, Razorpay uses HEART metrics to measure feature adoption and task success in its payment dashboards. Meesho tracks AARRR funnel metrics closely to optimize activation and referral among tier-2/3 users. Swiggy combines analytics with user surveys to improve happiness and retention in a highly competitive market.
Field exercise: Apply HEART + GSM to your product (15 min)
Pick a digital product you use regularly — it could be Swiggy, PhonePe, or a local app you rely on.
- Write down one goal for the product or a feature (e.g., "Make ordering food faster").
- Identify 2-3 signals that would indicate success for that goal (e.g., "Average order time", "User satisfaction with app speed").
- Find or imagine 2-3 metrics that measure those signals (e.g., "Median checkout time", "NPS score from 100 users").
- Map which HEART categories each metric belongs to.
- Reflect: which metric is the most actionable? Which might be misleading?
This exercise grounds you in the practical use of HEART + GSM. Use it as a starting point for your own product analytics conversations.
Pick a product or feature you care about.
- Define a clear goal (e.g., improve user onboarding completion).
- Identify signals that show progress toward the goal.
- List metrics that measure those signals.
- Classify each metric under HEART categories.
- Choose the one metric you would track weekly.
Test yourself: The Shipping Metrics Dilemma
You are the PM at a Series B Mumbai-based fintech app with 2 million users. Your team has launched a new 'Instant Loan' feature. Early data shows high acquisition but low retention on the feature. Your CEO wants a report with a single metric to show the board next week.
The call: Which metric do you pick to report, and how do you justify it? How do you avoid misleading the board with vanity metrics?
Your reasoning:
You are the PM at a Series B Mumbai-based fintech app with 2 million users. Your team has launched a new 'Instant Loan' feature. Early data shows high acquisition but low retention on the feature. Your CEO wants a report with a single metric to show the board next week.
Your task: Which metric do you pick to report, and how do you justify it? How do you avoid misleading the board with vanity metrics?
your reasoning:
Where to go next
- Master user research to complement metrics: User Research Methods
- Learn to translate metrics into product vision: Product Vision and Strategy
- Understand Agile planning and execution: Agile and Scrum for PMs
- Explore advanced growth strategies: Growth Hacking and Metrics
- Develop skills in data-driven decision making: Metrics and KPIs
PL alumni now work at Razorpay, Swiggy, Meesho, PhonePe, Flipkart, and 30+ other companies.