A pragmatic product leader is constantly measuring. The numbers you choose to track are the metrics that determine the success or failure of your product.
Measurement is not an afterthought — it is the foundation of every product decision you make. The actual job of a product manager includes setting clear success criteria and tracking progress toward those goals. Without metrics, your theories and hypotheses remain just opinions. With metrics, you quantify momentum — how fast and in what direction your product is moving.
You will face the challenge of defining the right metrics early in product development — often with limited data and many unknowns. This lesson shows you how to pick metrics that matter, avoid vanity metrics, and use frameworks that connect your product goals to measurable signals.
Metrics are the velocity of your product momentum
Metrics are not just numbers. They are your way to translate strategic goals into quantifiable outcomes. Think of the physics formula for momentum: M = m × v. In product terms, m is the metric you track, and v is the velocity — the rate of change toward your goal.
For example, if your goal is to improve user retention by 10% over one month, your metric is retention rate, and your velocity is roughly 2.5% improvement per week. This velocity becomes your target to hit in each sprint or release cycle.
The pattern is consistent: without a time-bound metric, your goals are meaningless.
A pragmatic product leader is always mindful of these numbers. Measuring is continuous — every release, every experiment, every feature is an opportunity to see if you are moving the needle. If you cannot measure impact, you cannot improve.
Start with business goals, then customer metrics
When launching a new product or feature, defining success metrics can feel overwhelming. There are too many potential metrics, and each seems important. The trap is tracking everything and ending up with noise instead of signal.
The cleanest way to start is:
- Business goals: What does success look like for your company? Revenue targets, customer acquisition cost, gross margin, monthly recurring revenue — these are your north stars.
- Competitive benchmarks: How does your product compare to others in the market on key metrics like conversion rate or retention?
- Customer-specific metrics: What behaviors or outcomes matter most to your users? Product usage frequency, feature adoption, customer lifetime value.
Focus on the metrics that truly drive your business and product strategy, not just what is easy to track or popular.
Business metrics vs customer metrics
Metrics fall into two broad categories:
| Category | Examples | Purpose |
|---|---|---|
| Business-oriented | Customer Acquisition Cost (CAC), Lifetime Value (LTV), Monthly Recurring Revenue (MRR), Annual Recurring Revenue (ARR), Average Revenue Per User (ARPU), Conversion Rate | Track financial health and growth |
| Customer-specific | Product adoption (sign-in frequency, referrals), Feature usage, Retention Rate/Churn Rate, Quality (Net Promoter Score, defect counts) | Understand user engagement and satisfaction |
Indian startups like Razorpay and Swiggy obsess over CAC and retention because these metrics directly impact profitability and scalability. But customer metrics like feature usage and NPS give early warnings when something is broken or delight is slipping.
Product launches demand focused, time-bound metrics
Product launches are the culmination of your go-to-market plan. The metrics you track here should reflect your launch goals — not just vanity numbers.
Common launch metrics include:
- Content views (press releases, blogs)
- New customer sign-ups or upgrades
- Feature adoption rates
But the key is to define a timeframe and target. For example: "Increase usage of Feature ABC by 25% in 120 days."
Without a deadline, your team loses focus and momentum. The timeframe also lets you measure velocity and course-correct.
The HEART framework: a balanced metric set
One of the most practical frameworks for product metrics is the HEART framework developed by Google. It helps ensure you track a balanced set of metrics across user experience dimensions:
| Metric | Description |
|---|---|
| H - Happiness | Measures user attitude — satisfaction, likelihood to recommend (e.g., NPS) |
| E - Engagement | Measures level of user interaction — visit frequency, page depth, intensity of use |
| A - Adoption | Measures new user uptake — number of unique users starting to use your product or feature |
| R - Retention | Measures continued use — how many users return over time |
| T - Task Success | Measures efficiency and effectiveness — error rates, task completion times |
Indian companies like Flipkart and PhonePe track retention and engagement tightly because acquiring users is expensive, and long-term loyalty drives business sustainability.
Goal-Signal-Metrics framework: connect metrics to your product goals
Metrics only matter if they reflect your product goals. The Goal-Signal-Metrics framework keeps you focused:
- Goal: Define the UX or business goal clearly. What outcome do you want?
- Signal: Identify what user behavior or data would indicate success or failure of that goal.
- Metric: Choose sustainable, measurable metrics tied to the signals.
For example:
| Goal | Signal | Metric |
|---|---|---|
| App is easy and trusted for invoice approval on the go | Positive user feedback | User satisfaction scores over time |
| Increase brand loyalty | Membership renewals | Number of renewals |
| App adoption as laptop alternative | Number of new installs | Unique app installs over time |
| Retain users | Continued app use | App deletion rates over time |
| Efficient task completion | Completed invoice dispositions | Time taken to disposition invoices |
Use this framework to avoid chasing metrics that are easy to measure but do not reflect your goals.
Measurement is a balance of data and intuition
Let me be direct about this — data-driven decisions are not the only way to decide. Product intuition and context matter.
You will not always have enough data to make perfect decisions. You will have to balance:
- What the data tells you
- Your product instincts and experience
- The business context and constraints
If you wait for perfect data, you will never ship. If you ignore data, you will steer blindly.
The goal is "just enough" data to make relevant decisions. The right metrics help you get there.
Real-world example: measuring retention velocity
Imagine your goal is to improve retention by 10% in one month. That means a velocity of roughly 2.5% retention improvement per week.
You track weekly retention rates after each release. If you see 1% improvement in week 1, 2% in week 2, you are behind goal and need to adjust your tactics.
This kind of measurement helps you avoid surprises and course-correct quickly.
MeetingScene: Defining metrics for a new feature launch
Product strategy meeting at a Series A fintech startup in Bangalore.
PM Lead: “We are launching the new loan eligibility feature next quarter. What metrics should we track to know if it's successful?”
Data Analyst: “We can track feature adoption — number of users who try the feature, and drop-off rates during the process.”
Marketing Lead: “Also, CAC and conversion rates for loan applications.”
Customer Success Manager: “And NPS scores from users who used the feature.”
PM Lead: “Great. Let's use the HEART framework to balance these and set targets for 3 months post-launch.”
The team aligns on a metric dashboard that combines business and user metrics, with clear goals and timelines.
Aligning cross-functional teams on meaningful metrics for a new product launch.
FieldExercise: Define your product's key metrics (Time: 15 min)
Pick a product or feature you are currently working on or familiar with. Write down:
- Your top 3 business goals for this product (e.g., revenue growth, CAC reduction).
- For each goal, identify 1-2 customer behaviors or signals that indicate success.
- Use the HEART framework to select at least one metric for each dimension (Happiness, Engagement, Adoption, Retention, Task Success).
- Define a time-bound target for each metric (e.g., increase retention by 5% in 2 months).
- Reflect on which metrics you currently track and which you do not but should.
This exercise will help you connect your product goals to meaningful, measurable outcomes.
SlackChat: Debating vanity metrics vs meaningful metrics
JudgmentExercise
scenario="You are the PM at a B2C Indian EdTech startup launching a new video learning feature. The business goal is to increase monthly active users by 15% in 3 months. Early data shows high feature adoption but low retention after 2 weeks." question="What metrics do you prioritize to diagnose the problem and decide your next steps?" expertReasoning="Prioritize retention and engagement metrics over raw adoption. High adoption with low retention signals a product experience issue. Use HEART framework to track happiness (user feedback), engagement (time spent per session), and task success (completion rates). Check if users are dropping off due to content, UX, or technical issues. Set a time-bound target for retention improvement and run experiments to improve it." commonMistake="Focusing only on adoption or downloads without looking at retention leads to misleading conclusions. Teams often celebrate initial sign-ups but ignore whether users stick around, causing wasted effort on features that don't deliver lasting value." />
You are the PM at a B2C Indian EdTech startup launching a new video learning feature. The business goal is to increase monthly active users by 15% in 3 months. Early data shows high feature adoption but low retention after 2 weeks.
Your task: What metrics do you prioritize to diagnose the problem and decide your next steps?
your reasoning:
FromTheField context="from a Pragmatic Leaders session on metrics"
When I train product managers, I see the same mistake repeatedly: obsessing over every number available. The trap is to confuse quantity with quality. You track dozens of metrics but none tell you if the product is truly succeeding.
What I tell PMs is: pick the handful of metrics that matter, tie them directly to your business goals and user outcomes, and measure velocity toward them.
Data is your compass, not your destination. When you lose sight of the goal, metrics become noise.
AlumniCallout
PL alumni now work at Flipkart, Google, Razorpay, PhonePe, Swiggy, Amazon, Microsoft, and 30+ other companies.
Where to go next
- If you want to learn how to translate metrics into product experiments: Experiment Design and Analysis
- If you want to deepen your understanding of product discovery: User Research Methods
- If you want to master stakeholder communication using data: Storytelling with Data
- If you want to prepare for PM interviews focused on metrics: PM Interview Prep: Metrics Questions