//pragmatic leaders

Choosing and Using Metrics That Matter

Reading time
6 min
Section
Section A - Question Bank
6 min left0%
choosing and using metrics that matter0%
6 min left
A pragmatic product leader is constantly measuring. The numbers you choose are the momentum that drives your product forward.
Talvinder Singh, from a Pragmatic Leaders session on metrics

Metrics are not just numbers. They are the language of your product’s health and progress. The actual job is to pick metrics that reflect real user value and business impact — not just what looks good on a slide deck.

If you cannot answer which metrics matter and why, you are flying blind. This is what separates a product manager from a business analyst or project coordinator.

Why metrics are momentum

Think of metrics as mass (m) and velocity (v) in the formula for momentum (M = m × v). The metric is your mass — the quantity you want to move. The velocity is the speed at which you improve that metric over time.

For example, if your goal is to improve retention by 10% in one month, your velocity is roughly 2.5% per week. That is the momentum you want to hit.

Without metrics, you cannot quantify whether your work is moving the needle. You cannot prove hypotheses. You cannot prioritize effectively.

The trap of too many metrics

So many metrics, so little time. It is extremely easy to track every metric because each one feels important. The trap is measuring everything and learning nothing.

The honest truth: good metric selection is hard and requires practice. You must learn to spot the signal from the noise.

Imagine you are tasked to improve the search experience on an app. What does that mean? Search results are incorrect? Suggestions are missing? Real-time results are slow? Each of these can generate dozens of potential metrics.

A pragmatic product leader starts with the end goal and then identifies the handful of metrics that will give the clearest insight into progress toward that goal.

The frameworks that help

Two frameworks are especially useful to structure your thinking:

AARRR (Pirate Metrics)

This framework breaks down the user lifecycle into five key metrics:

  • Acquisition: How do users find your product? Example: app installs, website visits.
  • Activation: Do users have a great first experience? Example: signups that complete onboarding.
  • Retention: Do users come back over time? Example: Day 7 or Day 30 retention rate.
  • Referral: Do users tell others? Example: invite shares, word of mouth.
  • Revenue: Do users pay? Example: monthly recurring revenue, average revenue per user.

AARRR helps you map your metrics to stages in the user journey and identify where the biggest leaks or opportunities are.

HEART

Developed by Google Ventures, HEART measures user experience quality across five dimensions:

  • Happiness: User satisfaction, measured via NPS or surveys.
  • Engagement: Frequency and depth of user interaction.
  • Adoption: Rate of new users starting to use your product or feature.
  • Retention: How many users return over time.
  • Task Success: How effectively users complete their goals (success rate, error rate, time taken).

HEART is especially useful for UX and feature-level metrics.

The difference between KPIs and metrics

All KPIs are metrics, but not all metrics are KPIs.

  • KPIs (Key Performance Indicators) are the few critical metrics that signal your product’s success against strategic goals.
  • Metrics are any data points you track.

For example, in a social media app:

  • KPI: Daily Active Users (DAU) — core measure of engagement.
  • Metric: Number of likes per post — informative but less critical.

Focus your energy on KPIs that drive decision-making and align with your business objectives.

Indian context matters

In India, local consumer behavior and market conditions influence which metrics matter.

For example, Swiggy focuses heavily on 'delivery time' as a KPI because customer satisfaction depends on speed and reliability.

You must consider your users and business model. Vanity metrics like total app downloads look good, but if users are not retained or monetized, they are meaningless.

Common pitfalls in metric selection

  • Tracking too many metrics without focus.
  • Choosing vanity metrics that don’t drive action.
  • Ignoring the timeframe and definition of success.
  • Failing to connect metrics to user value or business goals.

For example, tracking "number of files uploaded" without knowing if that leads to retention or revenue is a waste of effort.

How to pick the right metrics

  1. Start with your goal. What outcome matters most this quarter? Retention? Revenue? Engagement?
  2. List possible suspects. What could be causing success or failure? For search, it could be relevance, speed, or UI.
  3. Triangulate with data. Look at industry benchmarks and your product data to find gaps.
  4. Prioritize metrics that can be influenced. Measure what you can improve.
  5. Validate with experiments. Run tests to confirm your hypotheses about what affects the metric.

Example: Improving search conversion

Say your industry average conversion from search to product details page is 20%, but you are at 10%.

Potential causes:

  • Poor product images.
  • Prices too high.
  • Too many or irrelevant products.
  • Filters missing or broken.
  • Search results irrelevant.

You can test hypotheses like price sensitivity by running discounts on selected products and measuring impact on clicks.

Aligning metrics to business stage

Early-stage startups focus on adoption and retention to show product-market fit.

Growth-stage companies focus on revenue and engagement.

Enterprise SaaS companies track churn and monthly recurring revenue closely.

Your metric priorities should evolve with your company’s lifecycle.

From the field: Metrics in Indian SaaS

Translating metrics into product decisions

Metrics are not just for reporting — they should drive what you build next.

If retention is low, dig into why users leave. Is onboarding confusing? Is the core value unclear?

If activation is poor, hypothesize fixes, build experiments, measure results.

Metrics close the feedback loop between releases and learning.

Slack conversation: Translating model metrics into user impact

// thread: #product-metrics — PM translating technical metrics into user outcomes
Data AnalystOur search relevance score is 85%.
PMWhat does 85% relevance mean for users? How often do they find what they want on first try?
Data AnalystAbout 60% of searches lead to a product click on first attempt.
PMSo 40% get frustrated and leave or try again. That’s a big leak in the funnel.
Data AnalystYes, and our bounce rate from search is 30%.
PMWe should prioritize improving relevance and reducing bounce to improve retention.

Field exercise: Identify your product’s key metrics (time=15 min)

Pick a product you use daily or work on (Swiggy, Flipkart, Google Pay).

Write down:

  1. What is the core user problem the product solves?
  2. What are the 3–5 metrics that best measure success on that problem?
  3. Which metrics track acquisition, activation, retention, referral, and revenue?
  4. Which metrics relate to user happiness, engagement, task success?
  5. How would you prioritize these metrics for your next product cycle?

Review your answers against frameworks like AARRR and HEART.

Judgment exercise

// learn the judgment

You are a PM at a Series B Indian fintech startup. Your CEO wants to track as many metrics as possible to impress investors. Your product has low retention, moderate activation, and high acquisition. You have limited engineering bandwidth to build dashboards.

The call: Which metrics do you prioritize to track this quarter and why?

Your reasoning:

// practice

You are a PM at a Series B Indian fintech startup. Your CEO wants to track as many metrics as possible to impress investors. Your product has low retention, moderate activation, and high acquisition. You have limited engineering bandwidth to build dashboards.

Your task: Which metrics do you prioritize to track this quarter and why?

your reasoning:

0 chars (min 80)

Meeting scene: Defining success metrics for a new feature

// scene:

Feature planning meeting at a Mumbai-based B2C startup

Product Manager (You): “Before we build the new referral program, let's define what success looks like.”

Marketing Lead: “We want to increase user referrals by 30% in 3 months.”

Engineering Lead: “We can track number of invites sent and number of successful signups from invites.”

CEO: “I want to see impact on monthly active users and revenue.”

You: “Great. So our KPIs are referral conversion rate, increase in MAU, and incremental revenue. We will also monitor engagement and retention of referred users.”

By agreeing on clear metrics upfront, the team aligns on goals and can measure impact effectively.

// tension:

Aligning on clear, actionable success metrics before building prevents wasted effort and misaligned expectations.

From the field: Metrics questions in interviews

Where to go next

PL alumni now work at Razorpay, Swiggy, Meesho, Flipkart, PhonePe, and other leading Indian startups.