Back to Details

metrics-tracking

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Metrics Tracking Skill

产品指标追踪技能

You are an expert at product metrics — defining, tracking, analyzing, and acting on product metrics. You help product managers build metrics frameworks, set goals, run reviews, and design dashboards that drive decisions.
你是产品指标领域的专家——擅长定义、追踪、分析产品指标，并基于指标采取行动。你可以帮助产品经理搭建指标框架、设定目标、开展复盘会议，以及设计可驱动决策的仪表盘。

Product Metrics Hierarchy

产品指标层级

North Star Metric

北极星指标

The single metric that best captures the core value your product delivers to users. It should be:
  • Value-aligned: Moves when users get more value from the product
  • Leading: Predicts long-term business success (revenue, retention)
  • Actionable: The product team can influence it through their work
  • Understandable: Everyone in the company can understand what it means and why it matters
Examples by product type:
  • Collaboration tool: Weekly active teams with 3+ members contributing
  • Marketplace: Weekly transactions completed
  • SaaS platform: Weekly active users completing core workflow
  • Content platform: Weekly engaged reading/viewing time
  • Developer tool: Weekly deployments using the tool
最能体现产品为用户传递核心价值的单一指标。它需要满足：
  • 价值对齐：当用户从产品中获得更多价值时，该指标会随之变化
  • 前瞻性：可预测长期业务成功（如营收、留存）
  • 可落地：产品团队可通过自身工作影响该指标
  • 易理解：公司内所有人都能理解其含义及重要性
按产品类型划分的示例:
  • 协作工具：每周活跃且有3名以上成员贡献的团队数量
  • 交易平台：每周完成的交易笔数
  • SaaS平台：完成核心工作流的周活跃用户数
  • 内容平台：每周用户参与的阅读/观看时长
  • 开发者工具：使用该工具完成的每周部署次数

L1 Metrics (Health Indicators)

L1指标（健康指标）

The 5-7 metrics that together paint a complete picture of product health. These map to the key stages of the user lifecycle:
Acquisition: Are new users finding the product?
  • New signups or trial starts (volume and trend)
  • Signup conversion rate (visitors to signups)
  • Channel mix (where are new users coming from)
  • Cost per acquisition (for paid channels)
Activation: Are new users reaching the value moment?
  • Activation rate: % of new users who complete the key action that predicts retention
  • Time to activate: how long from signup to activation
  • Setup completion rate: % who complete onboarding steps
  • First value moment: when users first experience the core product value
Engagement: Are active users getting value?
  • DAU / WAU / MAU: active users at different timeframes
  • DAU/MAU ratio (stickiness): what fraction of monthly users come back daily
  • Core action frequency: how often users do the thing that matters most
  • Session depth: how much users do per session
  • Feature adoption: % of users using key features
Retention: Are users coming back?
  • D1, D7, D30 retention: % of users who return after 1 day, 7 days, 30 days
  • Cohort retention curves: how retention evolves for each signup cohort
  • Churn rate: % of users or revenue lost per period
  • Resurrection rate: % of churned users who come back
Monetization: Is value translating to revenue?
  • Conversion rate: free to paid (for freemium)
  • MRR / ARR: monthly or annual recurring revenue
  • ARPU / ARPA: average revenue per user or account
  • Expansion revenue: revenue growth from existing customers
  • Net revenue retention: revenue retention including expansion and contraction
Satisfaction: How do users feel about the product?
  • NPS: Net Promoter Score
  • CSAT: Customer Satisfaction Score
  • Support ticket volume and resolution time
  • App store ratings and review sentiment
5-7个指标共同构成产品健康的完整视图，这些指标对应用户生命周期的关键阶段：
获客：新用户是否能发现产品？
  • 新注册或试用启动数（数量及趋势）
  • 注册转化率（访客到注册用户的比例）
  • 渠道构成（新用户的来源分布）
  • 获客成本（针对付费渠道）
激活：新用户是否触达价值时刻？
  • 激活率：完成可预测留存的关键动作的新用户占比
  • 激活时长：从注册到完成激活动作的时间
  • 新手引导完成率：完成所有入职步骤的用户占比
  • 首次价值时刻：用户首次体验产品核心价值的节点
活跃：活跃用户是否获得价值？
  • DAU / WAU / MAU：不同时间维度的活跃用户数
  • DAU/MAU比值（粘性）：月活跃用户中每日回访的用户占比
  • 核心动作频率：用户完成关键动作的频次
  • 会话深度：用户每次会话的操作量
  • 功能 adoption：使用核心功能的用户占比
留存：用户是否会回头使用？
  • D1、D7、D30留存率：注册1天、7天、30天后仍活跃的用户占比
  • 同期群留存曲线：各注册批次用户的留存变化趋势
  • 流失率：每周期流失的用户或营收占比
  • 复活率：流失后再次回归的用户占比
变现：价值是否转化为营收？
  • 转化率：免费用户转为付费用户的比例（针对免费增值模式）
  • MRR / ARR：月度/年度经常性营收
  • ARPU / ARPA：平均每用户/每账户营收
  • 拓展营收：现有客户带来的营收增长
  • 净营收留存率：包含拓展与收缩的营收留存情况
满意度：用户对产品的感受如何？
  • NPS：净推荐值
  • CSAT：客户满意度得分
  • 支持工单数量及解决时长
  • 应用商店评分及评论情感倾向

L2 Metrics (Diagnostic)

L2指标（诊断指标）

Detailed metrics used to investigate changes in L1 metrics:
  • Funnel conversion at each step
  • Feature-level usage and adoption
  • Segment-specific breakdowns (by plan, company size, geography, user role)
  • Performance metrics (page load time, error rate, API latency)
  • Content-specific engagement (which features, pages, or content types drive engagement)
用于深入分析L1指标变化的详细指标：
  • 各步骤的漏斗转化率
  • 功能级别的使用与adoption情况
  • 细分群体拆解（按套餐、公司规模、地域、用户角色）
  • 性能指标（页面加载时间、错误率、API延迟）
  • 内容相关的活跃度（哪些功能、页面或内容类型驱动用户活跃）

Common Product Metrics

常见产品指标

DAU / WAU / MAU

DAU / WAU / MAU

What they measure: Unique users who perform a qualifying action in a day, week, or month.
Key decisions:
  • What counts as "active"? A login? A page view? A core action? Define this carefully — different definitions tell different stories.
  • Which timeframe matters most? DAU for daily-use products (messaging, email). WAU for weekly-use products (project management). MAU for less frequent products (tax software, travel booking).
How to use them:
  • DAU/MAU ratio (stickiness): values above 0.5 indicate a daily habit. Below 0.2 suggests infrequent usage.
  • Trend matters more than absolute number. Is active usage growing, flat, or declining?
  • Segment by user type. Power users and casual users behave very differently.
衡量内容：在一天、一周或一个月内完成合格动作的独立用户数。
关键决策:
  • 如何定义“活跃”？登录？页面浏览？核心动作？需谨慎定义——不同定义会呈现不同的用户行为画像。
  • 哪个时间维度最重要？日常使用产品（如通讯、邮件）看DAU；周度使用产品（如项目管理）看WAU；低频使用产品（如税务软件、旅游预订）看MAU。
使用方法:
  • DAU/MAU比值（粘性）：数值高于0.5表明用户已形成每日使用习惯；低于0.2则说明使用频次较低。
  • 趋势比绝对值更重要。活跃用户数是增长、持平还是下降？
  • 按用户类型细分。核心用户与普通用户的行为差异显著。

Retention

留存率

What it measures: Of users who started in period X, what % are still active in period Y?
Common retention timeframes:
  • D1 (next day): Was the first experience good enough to come back?
  • D7 (one week): Did the user establish a habit?
  • D30 (one month): Is the user retained long-term?
  • D90 (three months): Is this a durable user?
How to use retention:
  • Plot retention curves by cohort. Look for: initial drop-off (activation problem), steady decline (engagement problem), or flattening (good — you have a stable retained base).
  • Compare cohorts over time. Are newer cohorts retaining better than older ones? That means product improvements are working.
  • Segment retention by activation behavior. Users who completed onboarding vs those who did not. Users who used feature X vs those who did not.
衡量内容：在周期X开始使用的用户中，有多少比例在周期Y仍保持活跃？
常见留存时间维度:
  • D1（次日）：首次体验是否足够好，能吸引用户回头？
  • D7（一周后）：用户是否形成使用习惯？
  • D30（一个月后）：用户是否长期留存？
  • D90（三个月后）：用户是否成为稳定的长期用户？
使用方法:
  • 按同期群绘制留存曲线。关注：初始流失（激活问题）、持续下降（活跃问题）或趋于平稳（良好——已形成稳定的留存用户群）。
  • 对比不同同期群的留存情况。新用户群的留存是否比老用户群更好？这说明产品优化已见成效。
  • 按激活行为细分留存率。完成新手引导的用户与未完成的用户，留存情况差异明显；使用过功能X的用户与未使用的用户也是如此。

Conversion

转化率

What it measures: % of users who move from one stage to the next.
Common conversion funnels:
  • Visitor to signup
  • Signup to activation (key value moment)
  • Free to paid (trial conversion)
  • Trial to paid subscription
  • Monthly to annual plan
How to use conversion:
  • Map the full funnel and measure conversion at each step
  • Identify the biggest drop-off points — these are your highest-leverage improvement opportunities
  • Segment conversion by source, plan, user type. Different segments convert very differently.
  • Track conversion over time. Is it improving as you iterate on the experience?
衡量内容：从一个阶段进入下一阶段的用户占比。
常见转化漏斗:
  • 访客到注册用户
  • 注册用户到激活用户（触达核心价值时刻）
  • 免费用户到付费用户（试用转化）
  • 试用用户到付费订阅用户
  • 月度套餐到年度套餐
使用方法:
  • 绘制完整漏斗图，衡量每个步骤的转化率
  • 找出流失最严重的环节——这些是优先级最高的优化机会
  • 按来源、套餐、用户类型细分转化率。不同群体的转化情况差异显著。
  • 追踪转化率的变化趋势。随着体验迭代，转化率是否有所提升？

Activation

激活率

What it measures: % of new users who reach the moment where they first experience the product's core value.
Defining activation:
  • Look at retained users vs churned users. What actions did retained users take that churned users did not?
  • The activation event should be strongly predictive of long-term retention
  • It should be achievable within the first session or first few days
  • Examples: created first project, invited a teammate, completed first workflow, connected an integration
How to use activation:
  • Track activation rate for every signup cohort
  • Measure time to activate — faster is almost always better
  • Build onboarding flows that guide users to the activation moment
  • A/B test activation flows and measure impact on retention, not just activation rate
衡量内容：触达产品核心价值时刻的新用户占比。
定义激活动作:
  • 对比留存用户与流失用户的行为。留存用户做了哪些流失用户没做的动作？
  • 激活动作应能强烈预测长期留存
  • 用户应能在首次会话或前几天内完成该动作
  • 示例：创建首个项目、邀请同事、完成首个工作流、连接集成工具
使用方法:
  • 追踪每个注册用户群的激活率
  • 衡量激活时长——越快完成激活越好
  • 设计新手引导流程，引导用户触达激活时刻
  • A/B测试激活流程，衡量其对留存率的影响，而非仅关注激活率

Goal Setting Frameworks

目标设定框架

OKRs (Objectives and Key Results)

OKRs（目标与关键成果）

Objectives: Qualitative, aspirational goals that describe what you want to achieve.
  • Inspiring and memorable
  • Time-bound (quarterly or annually)
  • Directional, not metric-specific
Key Results: Quantitative measures that tell you if you achieved the objective.
  • Specific and measurable
  • Time-bound with a clear target
  • Outcome-based, not output-based
  • 2-4 Key Results per Objective
Example:
Objective: Make our product indispensable for daily workflows

Key Results:
- Increase DAU/MAU ratio from 0.35 to 0.50
- Increase D30 retention for new users from 40% to 55%
- 3 core workflows with >80% task completion rate
目标：定性、具有抱负的目标，描述你想要达成的结果。
  • 鼓舞人心且易于记忆
  • 有时间限制（按季度或年度）
  • 指明方向，而非具体指标
关键成果：量化指标，用于判断是否达成目标。
  • 具体且可衡量
  • 有时间限制及明确目标值
  • 基于结果，而非产出
  • 每个目标对应2-4个关键成果
示例:
Objective: Make our product indispensable for daily workflows

Key Results:
- Increase DAU/MAU ratio from 0.35 to 0.50
- Increase D30 retention for new users from 40% to 55%
- 3 core workflows with >80% task completion rate

OKR Best Practices

OKR最佳实践

  • Set OKRs that are ambitious but achievable. 70% completion is the target for stretch OKRs.
  • Key Results should measure outcomes (user behavior, business results), not outputs (features shipped, tasks completed).
  • Do not have too many OKRs. 2-3 objectives with 2-4 KRs each is plenty.
  • OKRs should be uncomfortable. If you are confident you will hit all of them, they are not ambitious enough.
  • Review OKRs at mid-period. Adjust effort allocation if some KRs are clearly off track.
  • Grade OKRs honestly at end of period. 0.0-0.3 = missed, 0.4-0.6 = progress, 0.7-1.0 = achieved.
  • 设定有抱负但可实现的OKRs。挑战性OKRs的目标完成率为70%。
  • 关键成果应衡量结果（用户行为、业务成果），而非产出（发布的功能、完成的任务）。
  • OKRs数量不宜过多。2-3个目标，每个目标对应2-4个关键成果即可。
  • OKRs应带来一定的压力。如果你确信能完成所有OKRs，说明目标不够有挑战性。
  • 中期复盘OKRs。如果部分关键成果明显偏离轨道，调整资源分配。
  • 期末如实评分OKRs。0.0-0.3=未达成，0.4-0.6=有进展，0.7-1.0=已达成。

Setting Metric Targets

设定指标目标

  • Baseline: What is the current value? You need a reliable baseline before setting a target.
  • Benchmark: What do comparable products achieve? Industry benchmarks provide context.
  • Trajectory: What is the current trend? If the metric is already improving at 5% per month, a 6% target is not ambitious.
  • Effort: How much investment are you putting behind this? Bigger bets warrant more ambitious targets.
  • Confidence: How confident are you in hitting the target? Set a "commit" (high confidence) and a "stretch" (ambitious).
  • 基准值：当前指标的数值是多少？设定目标前需先确定可靠的基准值。
  • 行业基准：同类产品的指标表现如何？行业基准可提供参考context。
  • 趋势：当前指标的变化趋势是什么？如果指标每月已增长5%，那么6%的目标就不够有挑战性。
  • 投入：你在该指标上投入了多少资源？更大的投入应对应更有抱负的目标。
  • 信心：你对达成目标有多大信心？设定“承诺型”（高信心）和“挑战型”（高抱负）两种目标。

Metric Review Cadences

指标复盘节奏

Weekly Metrics Check

每周指标检查

Purpose: Catch issues quickly, monitor experiments, stay in touch with product health. Duration: 15-30 minutes. Attendees: Product manager, maybe engineering lead.
What to review:
  • North Star metric: current value, week-over-week change
  • Key L1 metrics: any notable movements
  • Active experiments: results and statistical significance
  • Anomalies: any unexpected spikes or drops
  • Alerts: anything that triggered a monitoring alert
Action: If something looks off, investigate. Otherwise, note it and move on.
目的：快速发现问题、监控实验进展、掌握产品健康状况。 时长：15-30分钟。 参会人员：产品经理，可能包含工程负责人。
复盘内容:
  • 北极星指标：当前数值、周环比变化
  • 核心L1指标：任何显著变化
  • 进行中的实验：结果及统计显著性
  • 异常情况：任何意外的飙升或下降
  • 告警信息：触发监控告警的内容
行动：如果发现异常，立即展开调查；否则记录情况后继续推进。

Monthly Metrics Review

每月指标复盘

Purpose: Deeper analysis of trends, progress against goals, strategic implications. Duration: 30-60 minutes. Attendees: Product team, key stakeholders.
What to review:
  • Full L1 metric scorecard with month-over-month trends
  • Progress against quarterly OKR targets
  • Cohort analysis: are newer cohorts performing better?
  • Feature adoption: how are recent launches performing?
  • Segment analysis: any divergence between user segments?
Action: Identify 1-3 areas to investigate or invest in. Update priorities if metrics reveal new information.
目的：深入分析趋势、追踪目标进展、挖掘战略意义。 时长：30-60分钟。 参会人员：产品团队、关键利益相关者。
复盘内容:
  • 完整的L1指标评分卡及月环比趋势
  • 季度OKR目标的进展情况
  • 同期群分析：新用户群的表现是否更好？
  • 功能adoption：近期发布的功能表现如何？
  • 细分群体分析：不同用户群体的指标是否存在差异？
行动：确定1-3个需要深入调查或投入资源的领域。如果指标揭示了新信息，更新工作优先级。

Quarterly Business Review

季度业务复盘

Purpose: Strategic assessment of product performance, goal-setting for next quarter. Duration: 60-90 minutes. Attendees: Product, engineering, design, leadership.
What to review:
  • OKR scoring for the quarter
  • Trend analysis for all L1 metrics over the quarter
  • Year-over-year comparisons
  • Competitive context: market changes and competitor movements
  • What worked and what did not
Action: Set OKRs for next quarter. Adjust product strategy based on what the data shows.
目的：对产品表现进行战略评估，为下一季度设定目标。 时长：60-90分钟。 参会人员：产品、工程、设计、管理层。
复盘内容:
  • 本季度OKRs评分
  • 所有L1指标的季度趋势分析
  • 同比对比
  • 竞争环境：市场变化及竞品动态
  • 经验总结：哪些措施有效，哪些无效
行动：设定下一季度的OKRs。基于数据调整产品战略。

Dashboard Design Principles

仪表盘设计原则

Effective Product Dashboards

高效的产品仪表盘

A good dashboard answers the question "How is the product doing?" at a glance.
Principles:
  1. Start with the question, not the data. What decisions does this dashboard support? Design backwards from the decision.
  2. Hierarchy of information. The most important metric should be the most visually prominent. North Star at the top, L1 metrics next, L2 metrics available on drill-down.
  3. Context over numbers. A number without context is meaningless. Always show: current value, comparison (previous period, target, benchmark), trend direction.
  4. Fewer metrics, more insight. A dashboard with 50 metrics helps no one. Focus on 5-10 that matter. Put everything else in a detailed report.
  5. Consistent time periods. Use the same time period for all metrics on a dashboard. Mixing daily and monthly metrics creates confusion.
  6. Visual status indicators. Use color to indicate health at a glance:
    • Green: on track or improving
    • Yellow: needs attention or flat
    • Red: off track or declining
  7. Actionability. Every metric on the dashboard should be something the team can influence. If you cannot act on it, it does not belong on the product dashboard.
优秀的仪表盘应能一眼回答“产品表现如何？”的问题。
设计原则:
  1. 从问题出发，而非数据：该仪表盘支持哪些决策？从决策倒推设计。
  2. 信息层级清晰：最重要的指标应最醒目。北极星指标放在顶部，L1指标紧随其后，L2指标可通过钻取查看。
  3. 附带context的数值：脱离context的数值毫无意义。始终展示：当前数值、对比项（上期、目标值、行业基准）、趋势方向。
  4. 少而精，重洞察：包含50个指标的仪表盘毫无用处。聚焦5-10个关键指标，其他内容放在详细报告中。
  5. 时间周期一致：仪表盘上所有指标使用相同的时间周期。混合使用日度和月度指标会造成混淆。
  6. 可视化状态标识：用颜色直观展示指标健康状况：
    • 绿色：符合预期或呈上升趋势
    • 黄色：需关注或持平
    • 红色：偏离目标或呈下降趋势
  7. 可落地：仪表盘上的每个指标都应是团队可以影响的。如果无法采取行动，该指标不应出现在产品仪表盘上。

Dashboard Layout

仪表盘布局

Top row: North Star metric with trend line and target.
Second row: L1 metrics scorecard — current value, change, target, status for each key metric.
Third row: Key funnels or conversion metrics — visual funnel showing drop-off at each stage.
Fourth row: Recent experiments and launches — active A/B tests, recent feature launches with early metrics.
Bottom / drill-down: L2 metrics, segment breakdowns, and detailed time series for investigation.
第一行：北极星指标，附带趋势线和目标值。
第二行：L1指标评分卡——每个核心指标的当前值、变化量、目标值、状态。
第三行：关键漏斗或转化指标——可视化漏斗图，展示各步骤的流失情况。
第四行：近期实验与发布——进行中的A/B测试、近期发布的功能及早期指标表现。
底部/钻取层：L2指标、细分群体拆解、用于深入调查的详细时间序列数据。

Dashboard Anti-Patterns

仪表盘反模式

  • Vanity metrics: Metrics that always go up but do not indicate health (total signups ever, total page views)
  • Too many metrics: Dashboards that require scrolling to see. If it does not fit on one screen, cut metrics.
  • No comparison: Raw numbers without context (current value with no previous period or target)
  • Stale dashboards: Metrics that have not been updated or reviewed in months
  • Output dashboards: Measuring team activity (tickets closed, PRs merged) instead of user and business outcomes
  • One dashboard for all audiences: Executives, PMs, and engineers need different views. One size does not fit all.
  • 虚荣指标：持续增长但无法反映产品健康状况的指标（如累计注册用户数、累计页面浏览量）
  • 指标过多：需要滚动查看的仪表盘。如果无法在一屏内展示，精简指标。
  • 无对比项：仅展示原始数值，无context（如仅显示当前值，无上期或目标值对比）
  • 过时仪表盘：数月未更新或复盘的指标
  • 产出型仪表盘：衡量团队活动（如关闭的工单数量、合并的PR数量），而非用户及业务成果
  • 通用仪表盘：高管、产品经理、工程师需要不同的视图。通用仪表盘无法满足所有人群的需求。

Alerting

告警设置

Set alerts for metrics that require immediate attention:
  • Threshold alerts: Metric drops below or rises above a critical threshold (error rate > 1%, conversion < 5%)
  • Trend alerts: Metric shows sustained decline over multiple days/weeks
  • Anomaly alerts: Metric deviates significantly from expected range
Alert hygiene:
  • Every alert should be actionable. If you cannot do anything about it, do not alert on it.
  • Review and tune alerts regularly. Too many false positives and people ignore all alerts.
  • Define an owner for each alert. Who responds when it fires?
  • Set appropriate severity levels. Not everything is P0.
为需要立即关注的指标设置告警：
  • 阈值告警：指标低于或高于临界阈值（如错误率>1%、转化率<5%）
  • 趋势告警：指标在多日/多周内持续下降
  • 异常告警：指标显著偏离预期范围
告警规范:
  • 每个告警都应是可落地的。如果无法采取行动，不要设置告警。
  • 定期复盘并调整告警规则。过多的误报会导致用户忽略所有告警。
  • 为每个告警指定负责人。告警触发时由谁响应？
  • 设置合适的严重级别。并非所有告警都是最高优先级。