Defining the right metrics is one of the most important skills a product manager can develop. The wrong metrics lead you to optimize for the wrong things. The right metrics align your team around outcomes that matter and give you clear signals about whether your product is healthy.

Here is how senior PMs approach metrics in 2026.

The Problem With Vanity Metrics

Many PM teams track metrics that look good in presentations but do not drive real business outcomes. Total signups, page views, and app downloads are common culprits. These numbers go up and to the right, but they do not tell you whether users are actually getting value from your product.

Senior PMs distinguish between vanity metrics (numbers that feel good) and actionable metrics (numbers that inform decisions). An actionable metric answers a specific question: "Is this feature working? Should we invest more or pivot?"

The North Star Metric

A North Star metric is the single metric that best captures the core value your product delivers to users. It should reflect real user engagement, not just passive usage.

For Spotify, the North Star might be "time spent listening per user per week." For Airbnb, it might be "nights booked per month." For Slack, it might be "messages sent per active user per day."

The North Star metric serves two purposes. First, it aligns the team around a common goal. When every PM, engineer, and designer is optimizing for the same outcome, the product moves in a coherent direction. Second, it provides a single health indicator that tells you whether the product is getting better or worse.

Supporting Metrics and Guardrails

A North Star metric alone is not enough. You need supporting metrics that break down the drivers of the North Star, and guardrail metrics that ensure you are not sacrificing something important.

Supporting metrics decompose the North Star into actionable components. If your North Star is "weekly active buyers" for an e-commerce platform, your supporting metrics might be: new buyer acquisition rate, buyer return rate, and average orders per buyer per week. Each supporting metric can be improved independently.

Guardrail metrics protect against unintended consequences. If you are pushing to increase weekly active buyers, a guardrail might be "seller satisfaction score" or "return rate." If your growth strategy is hurting sellers or product quality, the guardrails will catch it.

Building a Metrics Framework for Your Product

Step 1: Start with the business objective. What does the company need this product to achieve? Revenue growth? User acquisition? Retention?

Step 2: Define your North Star. What single user behavior most closely correlates with that business objective?

Step 3: Decompose into supporting metrics. What drives the North Star? Break it into the key input metrics.

Step 4: Set guardrails. What could go wrong? What should you not sacrifice while pursuing your goals?

Step 5: Create dashboards. Make metrics visible to the entire team. If people cannot see the metrics, they cannot optimize for them.

Using Metrics in Interviews

PM interviews frequently test your metrics skills. You might be asked: "Define the success metrics for Facebook Marketplace" or "Instagram Reels engagement is flat. What metrics would you investigate?"

Strong answers demonstrate that you can connect metrics to user value and business outcomes, not just list numbers. Show that you understand the relationship between leading indicators (things that predict the future) and lagging indicators (things that measure past performance).

Product Alliance's Advanced Product Management Skills Course includes dedicated lessons on metrics frameworks, with real-world examples from Google, Meta, and Amazon products. It teaches you to think about metrics the way senior PMs do at top tech companies.