How to Build a Product Metrics Dashboard with North Star and Input Metrics

To build a product metrics dashboard with North Star and input metrics, organize metrics into four layers—North Star Metric (NSM), Input Metrics, Health Metrics, and Business Metrics—then define each with calculation methods, data sources, and alert thresholds, and review them on a structured cadence from daily to quarterly.

The phuryn/pm-skills repository provides a structured framework for constructing executive-level dashboards that align teams around a single customer-centric KPI. By following the skills defined in the source code, product teams can create automated, actionable views that expose the levers driving long-term success while maintaining guardrails for operational health.

Understanding the Metrics Hierarchy

Every dashboard built under this framework centers on four distinct metric layers defined in pm-product-discovery/skills/metrics-dashboard/SKILL.md.

The North Star Metric (NSM)

The North Star Metric is the single customer-centric KPI that predicts long-term business success. According to pm-marketing-growth/skills/north-star-metric/SKILL.md, selecting a valid NSM requires classifying your business "game" into one of three categories—Attention, Transaction, or Productivity—and validating the metric against seven specific criteria. This metric appears as the headline KPI at the top of your dashboard.

Input Metrics (MECE)

Input Metrics are the 3-5 leading indicators that directly push the NSM forward. As specified in pm-product-discovery/skills/metrics-dashboard/SKILL.md, these must be MECE (mutually exclusive, collectively exhaustive), meaning they cover all possible growth levers without overlapping. For example, if your NSM is Daily Active Users, input metrics might include new user signups, resurrection rate, and churned user win-back rate.

Health and Business Metrics

The final two layers provide guardrails and financial context. Health Metrics (e.g., latency, error rate, NPS) ensure the product experience remains stable while driving growth. Business Metrics (e.g., MRR, CAC, LTV, churn) provide the financial context required for executive decision-making.

Defining Metrics with Source Code Standards

In pm-product-discovery/skills/metrics-dashboard/SKILL.md, each metric must be documented in a standardized table that eliminates ambiguity about calculation and ownership.

Use this template to define your metrics before building visualizations:

| Metric            | Definition (calc)                     | Data Source          | Visualization | Target | Alert Threshold |
|------------------|----------------------------------------|----------------------|---------------|--------|-----------------|
| Daily Active Users (NSM) | Unique users per day               | Analytics Events DB  | Line chart    | 10 k   | < 8 k           |
| Sessions per User (Input) | Avg sessions / user per day        | Mixpanel             | Bar chart     | 3.0    | > 4.5           |
| Feature Adoption (Input) | % of users who used Feature X      | PostHog              | Funnel        | 45 %   | < 30 %          |
| Error Rate (Health)      | Errors / total requests            | Datadog              | Gauge         | < 0.5%| > 1 %           |
| MRR (Business)           | Monthly Recurring Revenue           | Stripe DB            | Number        | $250k | < $200k         |

This table ensures that every metric has a clear alert threshold and data source, which is critical for automated monitoring as specified in the framework's alert definition section (L71-L74).

Designing the Dashboard Layout

The visual layout defined in pm-product-discovery/skills/metrics-dashboard/SKILL.md follows a hierarchical information architecture:

• Top row: The North Star Metric displayed as a large headline KPI with trend indicators
• Middle section: Input metric sparklines showing week-over-week movement
• Side panels: Health gauges and business economics

Copy this ASCII layout sketch when prototyping your dashboard structure:

┌─────────────────────────────────────────────┐
│  NORTH STAR: Daily Active Users — 9,200 (↑5%)│
│  Trend: +5% vs last week                     │
├──────────────────┬──────────────────────────┤
│  Sessions/User   │  Feature Adoption          │
│  [▂▂▂▂▂▂▂]       │  [▂▃▅▇▅▃▂]                │
├──────────────────┼──────────────────────────┤
│  Error Rate      │  MRR                       │
│  [▁▁▁▁▁▁▁]       │  [$240k]                  │
└─────────────────────────────────────────────┘

You can render this sketch in any markdown viewer or convert it to a live diagram using Mermaid or similar diagram-as-code tools.

Implementation Steps from the Source Code

Follow this sequence derived from the pm-skills repository to ensure your dashboard aligns with the framework's architecture.

1. Validate the North Star

Before building the dashboard, run the North Star validation process defined in pm-marketing-growth/skills/north-star-metric/SKILL.md. This ensures your NSM is truly customer-centric and predictive of revenue, not just a vanity metric. Use the command file at pm-marketing-growth/commands/north-star.md to execute this validation through the CLI.

2. Structure the Metric Layers

Invoke the metrics-dashboard skill via pm-product-discovery/commands/setup-metrics.md to generate the four-layer structure. This enforces the MECE principle on your input metrics and ensures you have defined targets for each layer.

3. Set the Review Cadence

pm-product-discovery/skills/metrics-dashboard/SKILL.md mandates a specific review cadence:

• Daily: Operational health metrics and alerts
• Weekly: Input metric trends and experiment results
• Monthly: NSM movement and business metric health
• Quarterly: Strategic recalibration of the NSM itself

4. Configure Alert Thresholds

Define who receives alerts and under what conditions (L71-L74). Input metrics should trigger alerts when they fall outside the target range, while health metrics should alert immediately upon threshold breach.

Recommended Tooling

The framework specifies distinct tools for each metric layer in pm-product-discovery/skills/metrics-dashboard/SKILL.md:

• Product Analytics: Amplitude or Mixpanel for tracking NSM and input metrics
• SQL Dashboards: Looker or Metabase for business metrics requiring custom joins
• Operational Health: Grafana or Datadog for real-time health metrics and infrastructure monitoring

Summary

• Organize metrics into four layers: North Star Metric, Input Metrics (MECE), Health Metrics, and Business Metrics, as defined in pm-product-discovery/skills/metrics-dashboard/SKILL.md.
• Define each metric with a calculation method, data source, visualization type, target, and alert threshold using the standardized table format (L40-L45).
• Design the layout with the NSM as the headline KPI, followed by input metric sparklines and health gauges (L46-L63).
• Establish a review cadence ranging from daily operational checks to quarterly strategic recalibration (L65-L69).
• Validate the NSM using the seven-criteria checklist in pm-marketing-growth/skills/north-star-metric/SKILL.md before building dependent input metrics.

Frequently Asked Questions

How many input metrics should a product dashboard include?

A product metrics dashboard should include 3 to 5 input metrics that are mutually exclusive and collectively exhaustive (MECE). According to pm-product-discovery/skills/metrics-dashboard/SKILL.md, limiting the number to fewer than five ensures the team stays focused on the highest-leverage drivers, while the MECE principle guarantees you have captured all possible growth levers without double-counting.

What is the difference between a North Star Metric and input metrics?

The North Star Metric is the single lagging indicator that represents the ultimate value delivered to customers, while input metrics are the leading indicators that teams can directly influence to move the NSM. For example, if Daily Active Users is your NSM, input metrics might include activation rate or retention rate—these are the dials the product team can turn to ultimately drive the headline number.

How do I validate that my North Star Metric is properly chosen?

Validate your NSM using the seven-criteria checklist defined in pm-marketing-growth/skills/north-star-metric/SKILL.md. First, classify your business model as Attention, Transaction, or Productivity. Then verify the metric reflects customer value, has a causal relationship to revenue, and is measurable without excessive lag. The repository provides a CLI command at pm-marketing-growth/commands/north-star.md to walk through this validation systematically.

What tools does the pm-skills framework recommend for different metric types?

The framework recommends Amplitude or Mixpanel for product analytics (NSM and input metrics), Looker or Metabase for SQL-based business metrics dashboards, and Grafana or Datadog for operational health metrics. This separation ensures that real-time health alerts do not clutter strategic product analytics while maintaining specialized tooling for each metric layer as specified in pm-product-discovery/skills/metrics-dashboard/SKILL.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}