Metrics dashboard skill

Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds.

by phuryn·MIT license·★ 26,557 Stars on the repo·GitHub ↗

Use now

Files of Metrics dashboard

phuryn/main1 file shown
SKILL.md
Show the full text95 lines
metrics-dashboard/SKILL.md95 lines · 5.6 KB

Product Metrics Dashboard

Design a comprehensive product metrics dashboard with the right metrics, visualizations, and alert thresholds.

Context

You are designing a metrics dashboard for $ARGUMENTS.

If the user provides files (existing dashboards, analytics data, OKRs, or strategy docs), read them first.

Domain Context

Metrics vs KPIs vs NSM: Metrics = all measurable things. KPIs = a few key quantitative metrics tracked over a longer period. North Star Metric = a single customer-centric KPI that is a leading indicator of business success.

4 criteria for a good metric (Ben Yoskovitz, Lean Analytics): (1) Understandable — creates a common language. (2) Comparative — over time, not a snapshot. (3) Ratio or Rate — more revealing than whole numbers. (4) Behavior-changing — the Golden Rule: "If a metric won't change how you behave, it's a bad metric."

8 metric types: Vanity vs Actionable (only actionable metrics change behavior), Qualitative vs Quantitative (WHAT vs WHY — you need both; never stop talking to customers), Exploratory vs Reporting (explore data to uncover unexpected insights), Lagging vs Leading (leading indicators enable faster learning cycles, e.g. customer complaints predict churn).

5 action steps: (1) Audit metrics against the 4 good-metric criteria. (2) Update dashboards — ensure all key metrics are good ones. (3) Identify vanity metrics — be careful how you use them. (4) Classify leading vs lagging indicators. (5) Pick one problem and dig deep into the data.

For case studies and more detail: Are You Tracking the Right Metrics? by Ben Yoskovitz

Instructions
  1. Identify the metrics framework — organize metrics into layers:

    North Star Metric: The single metric that best captures core value delivery

    Input Metrics (3-5): The levers that drive the North Star

    Health Metrics: Guardrails that ensure overall product health

    Business Metrics: Revenue, cost, and unit economics

  2. For each metric, define:

    Metric Definition Data Source Visualization Target Alert Threshold
    [Name] [Exact calculation: numerator/denominator, time window] [Where the data comes from] [Line chart / Bar / Number / Funnel] [Goal value] [When to trigger an alert]
  3. Design the dashboard layout:

    ┌─────────────────────────────────────────────┐
    │  NORTH STAR: [Metric] — [Current Value]     │
    │  Trend: [↑/↓ X% vs last period]             │
    ├──────────────────┬──────────────────────────┤
    │  Input Metric 1  │  Input Metric 2          │
    │  [Sparkline]     │  [Sparkline]             │
    ├──────────────────┼──────────────────────────┤
    │  Input Metric 3  │  Input Metric 4          │
    │  [Sparkline]     │  [Sparkline]             │
    ├──────────────────┴──────────────────────────┤
    │  HEALTH: [Latency] [Error Rate] [NPS]       │
    ├─────────────────────────────────────────────┤
    │  BUSINESS: [MRR] [CAC] [LTV] [Churn]        │
    └─────────────────────────────────────────────┘
    
  4. Set review cadence:

    • Daily: Operational health (errors, latency, critical flows)
    • Weekly: Input metrics and engagement trends
    • Monthly: North Star, business metrics, OKR progress
    • Quarterly: Strategic review and metric recalibration
  5. Define alerts:

    • What thresholds trigger investigation?
    • Who gets alerted and through what channel?
    • What's the expected response time?
  6. Recommend tools based on the user's context:

    • Amplitude, Mixpanel, PostHog for product analytics
    • Looker, Metabase, Mode for SQL-based dashboards
    • Datadog, Grafana for operational health

Think step by step. Save the dashboard specification as a markdown document.


Further Reading
1---
2name: metrics-dashboard
3description: "Define and design a product metrics dashboard with key metrics, data sources, visualization types, and alert thresholds. Use when creating a metrics dashboard, defining KPIs, setting up product analytics, or building a data monitoring plan."
4---
5 
6## Product Metrics Dashboard
7 
8Design a comprehensive product metrics dashboard with the right metrics, visualizations, and alert thresholds.
9 
10### Context
11 
12You are designing a metrics dashboard for **$ARGUMENTS**.
13 
14If the user provides files (existing dashboards, analytics data, OKRs, or strategy docs), read them first.
15 
16### Domain Context
17 
18**Metrics vs KPIs vs NSM**: Metrics = all measurable things. KPIs = a few key quantitative metrics tracked over a longer period. North Star Metric = a single customer-centric KPI that is a leading indicator of business success.
19 
20**4 criteria for a good metric** (Ben Yoskovitz, *Lean Analytics*): (1) Understandable — creates a common language. (2) Comparative — over time, not a snapshot. (3) Ratio or Rate — more revealing than whole numbers. (4) Behavior-changing — the Golden Rule: "If a metric won't change how you behave, it's a bad metric."
21 
22**8 metric types**: Vanity vs Actionable (only actionable metrics change behavior), Qualitative vs Quantitative (WHAT vs WHY — you need both; never stop talking to customers), Exploratory vs Reporting (explore data to uncover unexpected insights), Lagging vs Leading (leading indicators enable faster learning cycles, e.g. customer complaints predict churn).
23 
24**5 action steps**: (1) Audit metrics against the 4 good-metric criteria. (2) Update dashboards — ensure all key metrics are good ones. (3) Identify vanity metrics — be careful how you use them. (4) Classify leading vs lagging indicators. (5) Pick one problem and dig deep into the data.
25 
26For case studies and more detail: [Are You Tracking the Right Metrics?](https://www.productcompass.pm/p/are-you-tracking-the-right-metrics) by Ben Yoskovitz
27 
28### Instructions
29 
301. **Identify the metrics framework** — organize metrics into layers:
31 
32 **North Star Metric**: The single metric that best captures core value delivery
33 
34 **Input Metrics** (3-5): The levers that drive the North Star
35 
36 **Health Metrics**: Guardrails that ensure overall product health
37 
38 **Business Metrics**: Revenue, cost, and unit economics
39 
402. **For each metric, define**:
41 
42 | Metric | Definition | Data Source | Visualization | Target | Alert Threshold |
43 |---|---|---|---|---|---|
44 | [Name] | [Exact calculation: numerator/denominator, time window] | [Where the data comes from] | [Line chart / Bar / Number / Funnel] | [Goal value] | [When to trigger an alert] |
45 
463. **Design the dashboard layout**:
47 
48 ```
49 ┌─────────────────────────────────────────────┐
50 │ NORTH STAR: [Metric] — [Current Value] │
51 │ Trend: [↑/↓ X% vs last period] │
52 ├──────────────────┬──────────────────────────┤
53 │ Input Metric 1 │ Input Metric 2 │
54 │ [Sparkline] │ [Sparkline] │
55 ├──────────────────┼──────────────────────────┤
56 │ Input Metric 3 │ Input Metric 4 │
57 │ [Sparkline] │ [Sparkline] │
58 ├──────────────────┴──────────────────────────┤
59 │ HEALTH: [Latency] [Error Rate] [NPS] │
60 ├─────────────────────────────────────────────┤
61 │ BUSINESS: [MRR] [CAC] [LTV] [Churn] │
62 └─────────────────────────────────────────────┘
63 ```
64 
654. **Set review cadence**:
66 - **Daily**: Operational health (errors, latency, critical flows)
67 - **Weekly**: Input metrics and engagement trends
68 - **Monthly**: North Star, business metrics, OKR progress
69 - **Quarterly**: Strategic review and metric recalibration
70 
715. **Define alerts**:
72 - What thresholds trigger investigation?
73 - Who gets alerted and through what channel?
74 - What's the expected response time?
75 
766. **Recommend tools** based on the user's context:
77 - Amplitude, Mixpanel, PostHog for product analytics
78 - Looker, Metabase, Mode for SQL-based dashboards
79 - Datadog, Grafana for operational health
80 
81Think step by step. Save the dashboard specification as a markdown document.
82 
83---
84 
85### Further Reading
86 
87- [The Ultimate List of Product Metrics](https://www.productcompass.pm/p/the-ultimate-list-of-product-metrics)
88- [The North Star Framework 101](https://www.productcompass.pm/p/the-north-star-framework-101)
89- [The Product Analytics Playbook: AARRR, HEART, Cohorts & Funnels for PMs](https://www.productcompass.pm/p/the-product-analytics-playbook-aarrr)
90- [AARRR (Pirate) Metrics: The 5-Stage Framework for Growth](https://www.productcompass.pm/p/aarrr-pirate-metrics)
91- [The Google HEART Framework: Your Guide to Measuring User-Centric Success](https://www.productcompass.pm/p/the-google-heart-framework)
92- [Funnel Analysis 101: How to Track and Optimize Your User Journey](https://www.productcompass.pm/p/funnel-analysis)
93- [Are You Tracking the Right Metrics?](https://www.productcompass.pm/p/are-you-tracking-the-right-metrics)
94- [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
95 

Discussion

Alternatives

/ar:ar-status — Experiment DashboardShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.Data & AI · MITAnalytics dashboardTurn a LinkedIn Analytics export into an interactive dark-themed React dashboard plus a written strategic analysis with 5 data-backed content recommendations. Reads every sheet in the export, builds charts for engagement trend, follower growth, post performance scatter, day-of-week heatmap, and audience breakdown. Use this skill whenever the user says "analyse my linkedin", "linkedin analytics", "build my dashboard", "review my performance", or uploads a LinkedIn Analytics export file. Requires the user's LinkedIn Analytics export (xlsx) as input.Creator · MITEarnings Preview SkillGenerate a pre-earnings briefing for any stock using Yahoo Finance data. Use this skill whenever the user wants to prepare for an upcoming earnings report, understand what analysts expect, review a company's beat/miss track record, or get a quick overview before an earnings call. Triggers include: "earnings preview for AAPL", "what to expect from TSLA earnings", MSFT reports next week", "earnings preview", "pre-earnings analysis", what are analysts expecting for NVDA", "earnings estimates for", will GOOGL beat earnings", "earnings beat/miss history", upcoming earnings", "before earnings", "earnings setup", consensus estimates", "earnings whisper", "EPS expectations", what's the street expecting", "earnings season preview", any mention of preparing for or previewing an earnings report, or any request to understand expectations ahead of a company's earnings date. Always use this skill when the user mentions a ticker in context of upcoming earnings, even if they don't say "preview" explicitly. · MITPath A — List-styleSave the results of an in-chat data-exploration session as a TL report. Triggers when the user wants to persist a channels / brands / videos (uploads) / sponsorships list or filtered set they've been working with — phrases like "save this as a report", "save the list", "turn this into a campaign", "persist this", "make a report from what you found", "save the result", "I want to come back to this".Creator · MIT