By Simon Sovič, Senior Product Manager

Most product teams track metrics. Fewer track the right ones. This guide walks you through a practical process for choosing, setting up, and acting on the metrics that actually tell you whether your product is succeeding. You can complete the core steps in a single working session. No analytics background required.

What You'll Need

  • A clear product goal or objective (even a rough one is fine to start)

  • Access to at least one data source: your analytics platform, CRM, or backend database

  • A shared document or spreadsheet where your team can align on definitions

  • A basic understanding of what your product does and who it serves

Step 1: Start With the Outcome, Not the Metric

Before you open any dashboard, write down what success looks like for your product right now. Be specific. "Growth" is not a goal. "Increase the percentage of users who complete onboarding within 7 days" is a goal.

This step matters because metrics are only useful when they point toward a real outcome. Without a stated outcome, you end up tracking whatever is easy to measure, not what matters. Many teams fall into this trap, watching page views climb while retention quietly drops.

  • Write one sentence describing the outcome you want to achieve in the next 30 to 90 days.

  • Identify who benefits when that outcome is reached: users, the business, or both.

  • Check whether the outcome is something you can influence with product decisions. If not, it belongs on a business report, not your product dashboard.

Step 2: Choose a North Star Metric

A North Star Metric (NSM) is the single number that best captures the core value your product delivers to users. It sits between revenue (a lagging indicator) and activity (a leading but shallow indicator).

Examples from real products: Spotify tracks time spent listening. Airbnb tracks nights booked. A B2B SaaS tool might track weekly active teams. The right NSM reflects genuine user value, not just engagement for its own sake.

  • Ask: "What does a user do that signals they actually got value from our product?"

  • The answer is usually a specific action, not a session or a login.

  • Pick one NSM. You can have supporting metrics, but a team that optimizes for two North Stars at once usually optimizes for neither.

  • Write the NSM on your team's shared document. Everyone on the team should be able to state it from memory.

If you are early in building your product strategy, the Product Management for Startups: Essential Guide Covers how to frame product goals before your metrics infrastructure exists.

Step 3: Select Supporting Metrics Across the User Journey

Your NSM tells you whether the product is working overall. Supporting metrics tell you where it is breaking down. Map them to the stages a user goes through: acquisition, activation, retention, revenue, and referral. This framework, often called AARRR or the Pirate Metrics framework, gives you a structured way to cover the full journey without tracking everything.

  • Acquisition:How are users finding you? Track channel-level conversion rates, not just total signups.

  • Activation:What percentage of new users reach the "aha moment" - the point where they first experience core value? Track this within a specific time window, such as day 1 or day 7.

  • Retention:What percentage of users come back after week 1, week 4, and week 12? Retention curves reveal whether your product has lasting value or just novelty.

  • Revenue:For paid products, track conversion from free to paid, average revenue per user, and churn rate separately. Do not blend them into a single revenue figure.

  • Referral:Are users bringing other users? Net Promoter Score (NPS) is one proxy, but word-of-mouth referral rate is more direct if you can measure it.

Aim for three to five supporting metrics total. More than that and your team loses focus. Fewer and you miss important signals.

Step 4: Define Each Metric Precisely

Vague metric definitions cause real problems. Two team members can look at the same dashboard and report different numbers if "active user" means different things to each of them.

For every metric you track, write down:

  • The exact definition: what counts and what does not

  • The time window: daily, weekly, monthly, rolling 30 days

  • The data source: which system or query produces this number

  • The owner: who is responsible for monitoring and acting on it

In practice, a short metrics glossary in your team wiki prevents most alignment arguments. It also makes onboarding new team members faster.

Step 5: Set a Baseline Before You Set a Target

A target without a baseline is a guess. Before you decide you want to grow activation by 20%, find out what your current activation rate actually is.

  • Pull at least four weeks of historical data for each metric if it exists.

  • If your product is new and you have no historical data, run for two to four weeks before setting targets. Targets set on fewer than two weeks of data are usually wrong.

  • Look for seasonality or external events that might distort your baseline, such as a product launch, a marketing campaign, or a holiday period.

  • Document the baseline next to the metric definition. Update it quarterly.

Step 6: Build a Simple Metrics Dashboard

A dashboard is only useful if your team checks it regularly and trusts the numbers. Keep it simple at first.

  • Put your NSM at the top, visible without scrolling.

  • Group supporting metrics by funnel stage beneath it.

  • Add a trend line for each metric, not just the current value. Direction matters more than a single data point.

  • Set up a weekly review reminder. Looking at a dashboard once a month is not enough to catch problems early.

Free tools like Google Looker Studio, Metabase, or even a well-structured Google Sheet work for early-stage products. You do not need enterprise software to start.

Step 7: Connect Metrics to Your Product Roadmap

Metrics only create value when they influence decisions. The link between metrics and your roadmap is where this happens. Each item on your roadmap should map to at least one metric it is expected to move.

Before adding a feature to your roadmap, ask: which metric will this improve, and by how much? After shipping, check whether the metric moved. If it did not, that is a signal worth investigating before moving to the next feature.

For a practical starting point, the Product Roadmap Templates: Free Download and How to Use Includes a structure that connects roadmap items to measurable outcomes.

  • Add a "success metric" column to your roadmap template.

  • Review metric impact in your retrospective or sprint review.

  • Kill or revise features that shipped without moving the target metric. This is harder than it sounds, but it is one of the most effective ways to keep a roadmap honest.

Step 8: Review and Iterate on Your Metrics Quarterly

Metrics that were right six months ago may no longer reflect your product's current stage. A startup in early growth needs different signals than a product optimizing for retention at scale.

  • Schedule a quarterly metrics review separate from your roadmap planning.

  • Ask whether each metric is still actionable. If a metric has been flat for three months and no one is doing anything about it, either act on it or remove it.

  • Retire metrics that have served their purpose. A metric that helped you fix activation in Q1 may not need to stay on your primary dashboard in Q3.

  • Add new metrics only when you have a clear reason. Curiosity is not a reason. A specific decision you need to make is.

Common Mistakes to Avoid

  • Tracking vanity metrics:Total downloads, total signups, and social followers feel good but rarely drive product decisions. Ask whether a metric would change your behavior if it went up or down. If not, it is probably vanity.

  • Measuring too many things:A dashboard with 40 metrics is a dashboard no one reads. Start with five to eight and add only when needed.

  • Confusing correlation with causation:Two metrics moving together does not mean one caused the other. Run experiments when you need to establish cause.

  • Ignoring qualitative signals:Numbers tell you what is happening. User interviews and support tickets often tell you why. Use both.

  • Setting targets without a plan:A target is only useful if you have at least one hypothesis for how to reach it. Otherwise it is just a number on a slide.

For more on how product managers approach these decisions day to day, see What Does a Product Manager Actually Do Day to Day.

FAQ

What is the difference between a KPI and a metric?

A metric is any number you track. A KPI (Key Performance Indicator) is a metric that is directly tied to a strategic goal. All KPIs are metrics, but not all metrics are KPIs. Keep your KPI list short and deliberate.

How many metrics should a product team track?

Most teams track too many metrics, not too few. A focused product team typically has one North Star Metric and three to five supporting metrics. You might monitor additional metrics in the background, but the active decision-making set should stay small.

What is a good North Star Metric for a SaaS product?

It depends on your product's core value. Common examples include weekly active users who complete a core action, number of reports generated, or projects created per active team. The right NSM reflects genuine user value, not just presence in the app.

How do I know if a metric has improved because of my product changes?

The most reliable method is a controlled experiment, often called an A/B test, where one group sees the change and another does not. If running an experiment is not possible, document the timing of changes and look for a clear shift in the metric trend at the point the change went live. Be honest about the limits of this approach.

How often should I review product metrics?

Check your dashboard weekly to catch anomalies early. Do a deeper review of targets versus actuals monthly. Revisit the full set of metrics you are tracking every quarter to remove what is no longer relevant and add what you now need.

This page was made by SuperDuperSEO →