metrics-dashboard

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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.
你正在为**$ARGUMENTS**设计一款指标仪表盘。
如果用户提供了文件(现有仪表盘、分析数据、OKR或战略文档),请先阅读这些文件。

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
指标 vs KPI vs 北极星指标(NSM):指标=所有可衡量的事物。KPI=少数需要长期跟踪的关键量化指标。北极星指标=一个以客户为中心的单一KPI,是业务成功的领先指标。
优质指标的4个标准(来自Ben Yoskovitz的《精益分析》):(1) 易懂性——创造通用语言。(2) 可比性——随时间变化,而非单一快照。(3) 比率或速率——比绝对值更具参考价值。(4) 促进行为改变——黄金法则:“如果一个指标无法改变你的行为,那它就是个糟糕的指标。”
8类指标:虚荣指标 vs 可行动指标(只有可行动指标能改变行为)、定性指标 vs 定量指标(是什么 vs 为什么——两者都需要;永远不要停止与客户沟通)、探索性指标 vs 报告性指标(探索数据以发现意外洞察)、滞后指标 vs 领先指标(领先指标能加速学习周期,例如客户投诉可预测用户流失)。
5个行动步骤:(1) 对照优质指标的4个标准审核现有指标。(2) 更新仪表盘——确保所有关键指标都是优质指标。(3) 识别虚荣指标——谨慎使用它们。(4) 分类领先指标与滞后指标。(5) 挑选一个问题,深入挖掘数据。
如需案例研究和更多细节: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:
    MetricDefinitionData SourceVisualizationTargetAlert 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.

  1. 确定指标框架——将指标分层:
    北极星指标:最能体现核心价值交付的单一指标
    输入指标(3-5个):驱动北极星指标的杠杆
    健康指标:确保整体产品健康的保障指标
    业务指标:收入、成本和单位经济效益
  2. 为每个指标定义
    指标定义数据源可视化类型目标值告警阈值
    [指标名称][精确计算方式:分子/分母,时间窗口][数据来源][折线图 / 柱状图 / 数值 / 漏斗图][目标数值][触发告警的条件]
  3. 设计仪表盘布局
    ┌─────────────────────────────────────────────┐
    │ 北极星指标: [指标] — [当前值]     │
    │ 趋势: [较上期 ↑/↓ X%]             │
    ├──────────────────┬──────────────────────────┤
    │ 输入指标1  │ 输入指标2          │
    │  [迷你趋势图]     │  [迷你趋势图]             │
    ├──────────────────┼──────────────────────────┤
    │ 输入指标3  │ 输入指标4          │
    │  [迷你趋势图]     │  [迷你趋势图]             │
    ├──────────────────┴──────────────────────────┤
    │ 健康指标: [Latency] [Error Rate] [NPS]       │
    ├─────────────────────────────────────────────┤
    │ 业务指标: [MRR] [CAC] [LTV] [Churn]        │
    └─────────────────────────────────────────────┘
  4. 设置审核节奏
    • 每日:运营健康度(错误、延迟、关键流程)
    • 每周:输入指标和用户参与趋势
    • 每月:北极星指标、业务指标、OKR进展
    • 每季度:战略复盘和指标重新校准
  5. 定义告警规则
    • 哪些阈值会触发调查?
    • 谁会收到告警,通过什么渠道?
    • 预期响应时间是多少?
  6. 根据用户场景推荐工具
    • Amplitude, Mixpanel, PostHog 用于产品分析
    • Looker, Metabase, Mode 用于基于SQL的仪表盘
    • Datadog, Grafana 用于运营健康监控
逐步思考。将仪表盘规范保存为Markdown文档。

Further Reading

拓展阅读