Metrics Framework: Leading vs Lagging Indicators
When to use: Setting up metrics, designing dashboards, or when you need early signal before outcomes materialize
Framework source: Aakash Gupta's "Become an A/B Testing Expert" and metrics guidance
Quick Start
- Tell me: "Help me build a metrics framework for [product/feature]"
- I will check
thoughts/shared/pm/frameworks/for your North Star andthoughts/shared/pm/metrics/for baseline data - I will ask about your North Star (lagging metric), product stage, and decision speed needs
- We build a metric hierarchy: Lagging (quarterly) -> Leading (weekly) -> Input (daily)
- For each key metric, we define alert thresholds (green/yellow/red) and a dashboard layout
- Output goes to
thoughts/shared/pm/metrics/metrics-framework-[date].md
Key principle: Leading metrics should PREDICT lagging metrics. If they do not, you are tracking the wrong thing. We always validate the correlation before committing to a leading indicator.
Context Routing Logic (Internal - for Claude)
Automatic Context Checks: When this skill is invoked, immediately check:
| Source | Files/Folders | Search Terms | What to Extract | | ---------------- | ---------------------------------------------- | ------------------------------------ | -------------------------------------- | | Strategy Context | thoughts/shared/pm/frameworks/.md | North Star, objective, business goal | Company-wide lagging metric target | | Business Model | thoughts/shared/pm/context/business-info-template.md | metrics, KPIs, growth model | Current revenue/retention/growth focus | | Metrics History | thoughts/shared/pm/metrics/.md | baseline, trends, benchmarks | Historical leading/lagging metric data | | PRDs | thoughts/shared/pm/prds/.md | success metrics, measurement | Feature-level metric definitions | | Meetings | thoughts/shared/product/meeting-notes/.md | "metrics", "dashboard", "KPI" | Stakeholder metric priorities |
Context Priority:
- Business strategy and North Star FIRST
- Current product metrics and baselines SECOND
- Historical trend data THIRD
- Feature-specific metrics FOURTH
Cross-Skill Links:
- If defining North Star → Link to
/define-north-star - If setting up feature success → Link to
/feature-metricsfor STEDII framework - If tracking product health → Link to
/retention-analysisand/activation-analysis - If analyzing test results → Link to
/feature-results
Step 0: Understanding Your Metric System
Before designing your metrics framework, let me understand what you're optimizing for...
Checking:
thoughts/shared/pm/context/business-info-template.mdfor business model and goalsthoughts/shared/pm/frameworks/*.mdfor strategic prioritiesthoughts/shared/pm/metrics/for existing metric baselinesthoughts/shared/pm/prds/for current feature success metrics
Based on what I find, I'll show you:
Your Current Metric Health
North Star / Lagging Metric:
- [Current North Star metric from strategy]
- [Baseline value: X]
- [Target: Y by when]
Existing Leading Indicators:
- [What you're already tracking]
- [Historical effectiveness: does this predict the lagging metric?]
Metric Gaps:
- [Metrics you're missing that would help you move faster]
- [Decision-making gaps: where you're flying blind]
PM-Specific Diagnosis Questions
- Decision Speed: How long do you need to make go/no-go decisions? (Days vs weeks vs months)
- Product Stage: Are you focused on growth, retention, monetization, or operational efficiency?
- Team Alignment: Do different teams use different success metrics? (Problem!)
- Data Quality: Do you have reliable tracking for the metrics you care about?
- Stakeholder Expectations: Does your executive team care about your current metrics?
Leading vs Lagging Metrics
Lagging Metrics (Outcome Indicators)
Definition: Metrics that measure final outcomes - what already happened
Characteristics:
- Slow to respond
- High certainty (accurate)
- Ultimate measure of success
- Hard to influence directly
Examples:
- Revenue
- Customer lifetime value (LTV)
- Annual retention rate
- Net Promoter Score (NPS)
- Market share
- Profit margins
When to use:
- Board reporting
- Annual/quarterly goals
- Validating long-term bets
- Measuring ultimate success
Leading Metrics (Predictive Indicators)
Definition: Metrics that predict future outcomes - early signals
Characteristics:
- Fast to respond
- Lower certainty (probabilistic)
- Actionable in real-time
- Directly influenceable
Examples:
- Day 7 activation rate (predicts retention)
- Weekly active users (predicts revenue)
- Feature adoption rate (predicts stickiness)
- Time to first value (predicts churn)
- Support ticket volume (predicts satisfaction)
When to use:
- Day-to-day decisions
- Experiment evaluation
- Early problem detection
- Sprint planning
The Connection
Leading metrics should PREDICT lagging metrics.
If they don't, you're tracking the wrong leading metrics.
Example 1: E-commerce
Lagging: Monthly revenue Leading:
- Add-to-cart rate (faster signal)
- Checkout start rate
- Payment success rate
Logic: If add-to-cart drops today, revenue drops next week.
Example 2: SaaS Product
Lagging: 90-day retention Leading:
- Day 7 activation rate
- Weekly active usage
- Feature adoption in first 14 days
Logic: Users who activate in 7 days have 10x better 90-day retention.
Example 3: Marketplace
Lagging: GMV (Gross Merchandise Value) Leading:
- Search-to-view rate
- View-to-cart rate
- Seller response time
- Inventory depth
Logic: More searches + better inventory = more transactions = higher GMV
How to Identify Your Leading Metrics
Step 1: Start with Your North Star (Lagging Metric)
What's the ultimate outcome you care about?
Examples:
- Revenue
- User retention
- Engagement
- Customer satisfaction
Step 2: Work Backwards to Find Predictors
Use this prompt pattern:
Use /metrics-framework and reference thoughts/shared/pm/context/business-info-template.md
Our North Star / main outcome metric is: [your lagging metric]
Help me identify 3-5 leading indicators that:
1. Happen BEFORE this outcome
2. Predict this outcome with data
3. Are actionable (we can influence them)
4. Give us signal within 1-2 weeks
Our product: [describe product]
User journey: [describe key actions]
Current metrics: [what you track today]Step 3: Validate the Correlation
Run analysis to prove the connection:
- Cohort analysis:
- Users with high leading metric → retention/revenue outcome
- Users with low leading metric → churn outcome
- Time-series correlation:
- Leading metric moves up Week 1
- Lagging metric moves up Week 4-6
- Correlation coefficient > 0.7
If no correlation exists, it's not a leading indicator.
Minimum Data Quality Bar
Before trusting any correlation between leading and lagging metrics:
Minimum thresholds:
- Sample size: At least 1,000 users (or 100 accounts for B2B) in each comparison group
- Time period: At least 6 weeks of data (2 full product cycles minimum)
- Event frequency: Each user should have 5+ events of the measured behavior (avoid drawing conclusions from single actions)
- Segment stability: The user segments being compared should be stable (not changing composition) during the measurement period
Data quality red flags:
- Correlation based on fewer than 500 users -- mark as "Directional only, not statistically reliable"
- Correlation from a single week of data -- mark as "Preliminar