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
L1 Metrics (Health Indicators)
The 5-7 metrics that together paint a complete picture of product health:
- Acquisition: New signups, signup conversion rate, channel mix, cost per acquisition
- Activation: Activation rate, time to activate, setup completion rate
- Engagement: DAU/WAU/MAU, DAU/MAU ratio (stickiness), core action frequency, feature adoption
- Retention: D1/D7/D30 retention, cohort retention curves, churn rate, resurrection rate
- Monetization: Free-to-paid conversion, MRR/ARR, ARPU/ARPA, expansion revenue, net revenue retention
- Satisfaction: NPS, CSAT, support ticket volume, app store ratings
L2 Metrics (Diagnostic)
Detailed metrics used to investigate changes in L1 metrics:
- Funnel conversion at each step
- Feature-level usage and adoption
- Segment-specific breakdowns
- Performance metrics (page load time, error rate, API latency)
Common Product Metrics
DAU / WAU / MAU
- DAU/MAU ratio (stickiness): values above 0.5 indicate a daily habit. Below 0.2 suggests infrequent usage.
- Trend matters more than absolute number.
- Segment by user type. Power users and casual users behave very differently.
Retention
- Plot retention curves by cohort
- Compare cohorts over time -- are newer cohorts retaining better?
- Segment retention by activation behavior
Conversion
- Map the full funnel and measure conversion at each step
- Identify the biggest drop-off points
- Segment conversion by source, plan, user type
Activation
- Look at retained users vs churned users -- what actions did retained users take?
- The activation event should be strongly predictive of long-term retention
- Track activation rate for every signup cohort
Goal Setting Frameworks
OKRs (Objectives and Key Results)
Objectives: Qualitative, aspirational goals that describe what you want to achieve.
Key Results: Quantitative measures that tell you if you achieved the objective.
- 2-4 Key Results per Objective
- Outcome-based, not output-based
- 70% completion is the target for stretch OKRs
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
Setting Metric Targets
- Baseline: What is the current value?
- Benchmark: What do comparable products achieve?
- Trajectory: What is the current trend?
- Effort: How much investment are you putting behind this?
- Confidence: Set a "commit" (high confidence) and a "stretch" (ambitious)
Metric Review Cadences
Weekly Metrics Check (15-30 minutes)
- 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
Monthly Metrics Review (30-60 minutes)
- 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?
Quarterly Business Review (60-90 minutes)
- OKR scoring for the quarter
- Trend analysis for all L1 metrics over the quarter
- Year-over-year comparisons
- What worked and what did not
Dashboard Design Principles
Effective Product Dashboards
- Start with the question, not the data. What decisions does this dashboard support?
- Hierarchy of information. North Star at the top, L1 next, L2 on drill-down.
- Context over numbers. Always show: current value, comparison, trend direction.
- Fewer metrics, more insight. Focus on 5-10 that matter.
- Consistent time periods. Use the same time period for all metrics.
- Visual status indicators. Green (on track), Yellow (needs attention), Red (off track).
- Actionability. Every metric on the dashboard should be something the team can influence.
Dashboard Anti-Patterns
- Vanity metrics: Metrics that always go up but do not indicate health
- Too many metrics: Dashboards that require scrolling
- No comparison: Raw numbers without context
- Stale dashboards: Metrics that have not been reviewed in months
- Output dashboards: Measuring team activity instead of user and business outcomes
1---2name: metrics-tracking3description: Define, track, and analyze product metrics with frameworks for goal setting and dashboard design4---5
6# Metrics Tracking Skill
7
8You 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.
9
10## Product Metrics Hierarchy
11
12### North Star Metric
13The single metric that best captures the core value your product delivers to users. It should be:
14
15- **Value-aligned**: Moves when users get more value from the product
16- **Leading**: Predicts long-term business success (revenue, retention)
17- **Actionable**: The product team can influence it through their work
18- **Understandable**: Everyone in the company can understand what it means
19
20### L1 Metrics (Health Indicators)
21The 5-7 metrics that together paint a complete picture of product health:
22
23- **Acquisition**: New signups, signup conversion rate, channel mix, cost per acquisition
24- **Activation**: Activation rate, time to activate, setup completion rate
25- **Engagement**: DAU/WAU/MAU, DAU/MAU ratio (stickiness), core action frequency, feature adoption
26- **Retention**: D1/D7/D30 retention, cohort retention curves, churn rate, resurrection rate
27- **Monetization**: Free-to-paid conversion, MRR/ARR, ARPU/ARPA, expansion revenue, net revenue retention
28- **Satisfaction**: NPS, CSAT, support ticket volume, app store ratings
29
30### L2 Metrics (Diagnostic)
31Detailed metrics used to investigate changes in L1 metrics:
32- Funnel conversion at each step
33- Feature-level usage and adoption
34- Segment-specific breakdowns
35- Performance metrics (page load time, error rate, API latency)
36
37## Common Product Metrics
38
39### DAU / WAU / MAU
40- DAU/MAU ratio (stickiness): values above 0.5 indicate a daily habit. Below 0.2 suggests infrequent usage.
41- Trend matters more than absolute number.
42- Segment by user type. Power users and casual users behave very differently.
43
44### Retention
45- Plot retention curves by cohort
46- Compare cohorts over time -- are newer cohorts retaining better?
47- Segment retention by activation behavior
48
49### Conversion
50- Map the full funnel and measure conversion at each step
51- Identify the biggest drop-off points
52- Segment conversion by source, plan, user type
53
54### Activation
55- Look at retained users vs churned users -- what actions did retained users take?
56- The activation event should be strongly predictive of long-term retention
57- Track activation rate for every signup cohort
58
59## Goal Setting Frameworks
60
61### OKRs (Objectives and Key Results)
62
63**Objectives**: Qualitative, aspirational goals that describe what you want to achieve.
64
65**Key Results**: Quantitative measures that tell you if you achieved the objective.
66- 2-4 Key Results per Objective
67- Outcome-based, not output-based
68- 70% completion is the target for stretch OKRs
69
70**Example**:
71```
72Objective: Make our product indispensable for daily workflows
73
74Key Results:
75- Increase DAU/MAU ratio from 0.35 to 0.50
76- Increase D30 retention for new users from 40% to 55%
77- 3 core workflows with >80% task completion rate
78```
79
80### Setting Metric Targets
81- **Baseline**: What is the current value?
82- **Benchmark**: What do comparable products achieve?
83- **Trajectory**: What is the current trend?
84- **Effort**: How much investment are you putting behind this?
85- **Confidence**: Set a "commit" (high confidence) and a "stretch" (ambitious)
86
87## Metric Review Cadences
88
89### Weekly Metrics Check (15-30 minutes)
90- North Star metric: current value, week-over-week change
91- Key L1 metrics: any notable movements
92- Active experiments: results and statistical significance
93- Anomalies: any unexpected spikes or drops
94
95### Monthly Metrics Review (30-60 minutes)
96- Full L1 metric scorecard with month-over-month trends
97- Progress against quarterly OKR targets
98- Cohort analysis: are newer cohorts performing better?
99- Feature adoption: how are recent launches performing?
100
101### Quarterly Business Review (60-90 minutes)
102- OKR scoring for the quarter
103- Trend analysis for all L1 metrics over the quarter
104- Year-over-year comparisons
105- What worked and what did not
106
107## Dashboard Design Principles
108
109### Effective Product Dashboards
110
1111. **Start with the question, not the data**. What decisions does this dashboard support?
1122. **Hierarchy of information**. North Star at the top, L1 next, L2 on drill-down.
1133. **Context over numbers**. Always show: current value, comparison, trend direction.
1144. **Fewer metrics, more insight**. Focus on 5-10 that matter.
1155. **Consistent time periods**. Use the same time period for all metrics.
1166. **Visual status indicators**. Green (on track), Yellow (needs attention), Red (off track).
1177. **Actionability**. Every metric on the dashboard should be something the team can influence.
118
119### Dashboard Anti-Patterns
120- **Vanity metrics**: Metrics that always go up but do not indicate health
121- **Too many metrics**: Dashboards that require scrolling
122- **No comparison**: Raw numbers without context
123- **Stale dashboards**: Metrics that have not been reviewed in months
124- **Output dashboards**: Measuring team activity instead of user and business outcomes