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

A product metrics dashboard centers on a single North Star Metric supported by 3-5 actionable Input Metrics, organized into hierarchical layers with defined review cadences and alert thresholds.

The phuryn/pm-skills repository provides a battle-tested framework for constructing dashboards that align cross-functional teams around customer-centric outcomes. By combining the metrics-dashboard skill with the north-star-metric validation process, you create a single source of truth that connects leading indicators to long-term business health while maintaining clear operational guardrails.

Understanding the North Star Metric (NSM)

According to pm-marketing-growth/skills/north-star-metric/SKILL.md, the North Star Metric is the single customer-centric KPI that predicts long-term success. Before building your dashboard, you must validate your chosen NSM against seven specific criteria and classify your business "game" to ensure the metric truly represents sustainable value delivery.

Validating Your NSM Against Seven Criteria

The north-star-metric skill requires rigorous validation against seven criteria to prevent vanity metrics from dominating your dashboard. This validation ensures that the metric correlates with actual user value and business sustainability rather than superficial engagement.

Classifying Your Business Game

The framework forces classification into three business types: Attention (engagement duration), Transaction (conversion efficiency), or Productivity (output per unit of input). This classification determines which Input Metrics are most relevant to your NSM and ensures that your dashboard reflects the fundamental mechanics of your product.

Structuring Metric Layers in Your Dashboard

The pm-product-discovery/skills/metrics-dashboard/SKILL.md file organizes metrics into four distinct tiers. This hierarchical approach ensures that stakeholders can drill from high-level outcomes to operational drivers without losing context.

The Four-Tier Hierarchy

1. North Star Metric: The headline KPI displayed prominently at the top of the dashboard.
2. Input Metrics: 3-5 leading indicators that product teams can directly influence to push the NSM forward.
3. Health Metrics: Guardrails like latency, error rates, and NPS that ensure sustainable growth and user satisfaction.
4. Business Metrics: Financial context including MRR, CAC, LTV, and churn rates that justify continued investment.

Ensuring MECE Input Metrics

Input Metrics must be MECE (mutually exclusive, collectively exhaustive). As specified in SKILL.md, this principle ensures that your 3-5 leading indicators cover all leverage points without overlap, providing clear ownership for product teams and preventing duplicate efforts across squads.

Defining Metrics with Precision

Each metric requires a standardized definition table. According to the metrics-dashboard skill, you must document the calculation method, data source, visualization type, target value, and alert threshold.

Copy this template into your specifications:

| 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         |

Designing the Visual Layout

The layout suggested in pm-product-discovery/skills/metrics-dashboard/SKILL.md places the NSM as a headline figure, followed by Input Metric sparklines, Health Metric gauges, and Business Metric economics.

Use this ASCII sketch as your layout specification:

┌─────────────────────────────────────────────┐
│  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 with any markdown viewer or feed it to a diagram-as-code tool like Mermaid for interactive dashboards.

Implementing Review Cadences and Alerts

The framework defines specific review frequencies in pm-product-discovery/skills/metrics-dashboard/SKILL.md:

• Daily: Operational Health Metrics (error rates, system latency)
• Weekly: Input Metric trends (feature adoption rates, sessions per user)
• Monthly: NSM and Business Metrics (MRR growth, LTV/CAC ratios)
• Quarterly: Strategic recalibration of the NSM itself and Input Metric selection

Configuring Alert Thresholds

Define explicit thresholds and ownership within the metric definition table. For example, configure error rate > 1% to trigger alerts to the infrastructure team, while NSM drops below 8,000 notify product leadership immediately.

Selecting the Right Tooling Stack

The metrics-dashboard skill recommends specific tooling tiers to support each metric layer:

• Product Analytics: Amplitude or Mixpanel for event tracking and funnel analysis
• Business Intelligence: Looker or Metabase for SQL-based dashboards accessible to non-technical stakeholders
• Operational Monitoring: Grafana or Datadog for real-time system health and latency tracking

Integrating the PM-Skills Framework

To implement this in your organization, invoke the skills via the command layer. Use pm-marketing-growth/commands/north-star.md to validate your NSM against the seven criteria, then apply pm-product-discovery/commands/setup-metrics.md to initialize the dashboard structure with the four-tier hierarchy and MECE Input Metrics.

Summary

• The North Star Metric is the single customer-centric KPI that predicts long-term success, validated against seven criteria and classified by business game type.
• Input Metrics must be 3-5 MECE (mutually exclusive, collectively exhaustive) leading indicators that product teams can directly influence.
• Metric definitions require standardized tables covering calculation, data source, visualization, target, and alert threshold.
• Review cadences should follow daily (Health), weekly (Input), monthly (NSM/Business), and quarterly (Strategic) rhythms.
• Tooling should layer Amplitude/Mixpanel for product data, Looker/Metabase for business intelligence, and Grafana/Datadog for operational health.

Frequently Asked Questions

What is the difference between a North Star Metric and Input Metrics?

The North Star Metric is the single outcome measure that represents long-term value delivered to customers, while Input Metrics are the 3-5 leading indicators that product teams can directly manipulate to drive that outcome. As defined in pm-marketing-growth/skills/north-star-metric/SKILL.md, the NSM is a lagging indicator of success, whereas Input Metrics provide immediate feedback on tactical initiatives.

How many Input Metrics should a product dashboard include?

The pm-product-discovery/skills/metrics-dashboard/SKILL.md specifies exactly 3-5 Input Metrics. This constraint forces prioritization and ensures that teams focus on the highest-leverage drivers rather than diluting attention across dozens of vanity metrics.

What does MECE mean in the context of product metrics?

MECE stands for Mutually Exclusive, Collectively Exhaustive. In the framework defined in SKILL.md, this means your Input Metrics should cover all possible levers that influence the NSM without overlapping or double-counting effects. This structure ensures clear ownership and prevents teams from optimizing the same user behavior through different metric names.

Which tools are recommended for building a product metrics dashboard?

The framework recommends Amplitude or Mixpanel for product analytics (Input Metrics), Looker or Metabase for SQL-based business dashboards (Business Metrics), and Grafana or Datadog for operational monitoring (Health Metrics). This three-tier stack ensures that each metric layer is captured by the appropriate specialized tool.

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