A product metrics dashboard template should organize metrics into three layers — north star metric, input metrics, and health metrics — with leading indicators surfaced prominently and lagging indicators used for trend analysis rather than daily decision-making.
Most product dashboards are graveyards of metrics. Fifty charts, forty of which nobody looks at, and the three that actually matter buried on the third page. A well-designed metrics dashboard is not comprehensive — it's opinionated about what drives the business and surfaces those signals clearly.
This guide provides a template and principles for building a product metrics dashboard that PMs and leadership actually use.
The Three-Layer Metrics Architecture
Layer 1: North Star Metric (1 metric)
↑
Layer 2: Input Metrics (3-5 metrics that drive the north star)
↑
Layer 3: Health Metrics (technical, acquisition, retention baselines)
H3: Layer 1 — North Star Metric
Your north star metric is the single number that best captures the value your product delivers to customers and, when it grows, predicts long-term business health.
Examples by product type:
- SaaS productivity tool: Weekly Active Users who complete the core workflow
- Ecommerce: Gross Merchandise Value (GMV) per active buyer
- Marketplace: Number of successful transactions per week
- Content platform: Time spent on content per daily active user
- Developer tool: Number of API calls from production apps
According to Lenny Rachitsky's writing on north star metrics, the most common mistake is choosing revenue as the north star metric. Revenue is a lagging outcome of value delivery — when revenue falls, you already missed the signal weeks or months earlier.
H3: Layer 2 — Input Metrics
Input metrics are the levers that drive the north star. If your north star is weekly active users completing the core workflow:
- Activation rate: % of new signups who complete the core workflow once
- Day-7 retention: % of activated users who return within 7 days
- Workflow completion rate: % of sessions that result in a completed workflow
- Feature adoption: % of active users using the features that correlate with retention
The relationship between input metrics and the north star should be testable. If you improve activation rate, does the north star go up? If not, either your measurement is wrong or activation isn't actually the right lever.
H3: Layer 3 — Health Metrics
Health metrics are the guardrails — they shouldn't drive strategy, but their degradation signals a problem:
- Uptime / availability: Service reliability
- P95 response time: Performance baseline
- Error rate: Application health
- Churn rate: Long-term retention health
- Support ticket volume: Quality signal
- NPS / CSAT: Customer satisfaction baseline
Dashboard Structure Template
H3: Section 1 — Executive Summary (Above the Fold)
| Metric | Current | Last Week | Last Month | Trend | |--------|---------|-----------|------------|-------| | North Star Metric | [value] | [value] | [value] | ↑↓→ | | Input Metric 1 | [value] | [value] | [value] | ↑↓→ | | Input Metric 2 | [value] | [value] | [value] | ↑↓→ | | Input Metric 3 | [value] | [value] | [value] | ↑↓→ |
This section answers the question every stakeholder asks first: are we growing or not?
H3: Section 2 — Funnel Breakdown
For each stage of the user journey, track conversion rate:
- Visit → Signup
- Signup → Activation (first core action)
- Activation → Retention (return within 7 days)
- Retained → Power User (regular high-frequency use)
- Power User → Advocate (referral or review)
Funnel breakdowns reveal where value delivery breaks down.
H3: Section 3 — Cohort Analysis
Track retention curves by signup cohort (weekly or monthly). This is the most important chart for understanding product-market fit. If retention curves flatten (stop declining), you have a retained user base. If they continue to slope to zero, PMF is not yet achieved.
According to Shreyas Doshi on Lenny's Podcast, the retention curve is the most honest metric in a product dashboard — it can't be gamed by acquisition spend or pricing changes, and it directly reflects whether the product delivers ongoing value.
H3: Section 4 — Feature Adoption
For each major feature, track:
- Adoption rate (% of active users who have used it)
- Frequency (how often adopted users use it)
- Correlation with retention (do feature adopters retain better?)
Features with high adoption and high retention correlation are the core of your product. Features with low adoption and low retention correlation are candidates for removal.
H3: Section 5 — Health and Alerts
Automatic alerts (not charts to check manually) for:
- Error rate > X% (set based on your baseline)
- P95 latency > X ms
- Conversion rate drops >10% week-over-week
- North star metric drops >5% week-over-week
According to Annie Pearl on Lenny's Podcast discussing data-driven product management, the most valuable thing a product metrics dashboard can do is tell you when something has gone wrong without you having to check. Alerts are more valuable than additional charts.
FAQ
Q: What is a product metrics dashboard? A: A structured view of the metrics that drive product health, organized into north star metric, input metrics, and health metrics — designed to surface the signals that matter for product decisions without burying them in noise.
Q: What should a product metrics dashboard include? A: North star metric with week-over-week trend, 3-5 input metrics that drive the north star, funnel conversion rates, cohort retention curves, feature adoption by active users, and automated alerts for metric degradation.
Q: What is a north star metric for a SaaS product? A: The single number that best captures the value delivered to customers and predicts long-term business health. For SaaS, this is typically weekly active users completing the core workflow, not revenue.
Q: What is the difference between input metrics and health metrics? A: Input metrics are the levers you pull to move the north star — activation rate, retention, workflow completion. Health metrics are guardrails that signal problems when they degrade — uptime, error rate, churn.
Q: How do you set up alerts in a product metrics dashboard? A: Define threshold values for critical metrics — error rate, P95 latency, north star decline — and configure automatic alerts when thresholds are crossed. Alerts should notify you without requiring manual dashboard review.
HowTo: Build a Product Metrics Dashboard
- Define your north star metric — the single number that best captures value delivered to customers and predicts long-term business health
- Identify three to five input metrics that are the levers most correlated with moving the north star metric
- Define health metrics as guardrails including uptime, error rate, churn, and NPS that signal problems when they degrade
- Structure the dashboard with executive summary above the fold, funnel breakdown, cohort retention curves, feature adoption, and health metrics in that order
- Configure automatic alerts for critical threshold breaches including error rate spikes, latency increases, and north star metric drops above five percent week over week
- Review the dashboard weekly with the team and quarterly to audit whether the metrics still reflect the right signals as the product evolves