metrics-frameworklisted

# 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 1. Tell me: "Help me build a metrics framework for [product/feature]" 2. I will check `context-library/strategy/` for your North Star and `context-library/metrics/` for baseline data 3. I will ask about your North Star (lagging metric), product stage, and decision speed needs 4. We build a metric hierarchy: Lagging (quarterly) -> Leading (weekly) -> Input (daily) 5. For each key metric, we define alert thresholds (green/yellow/red) and a dashboard layout 6. Output goes to `outputs/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 | `context-library/strategy/*.md` | North Star, objective, business goal | Company-wide lagging metric target | | Business Model | `context-library/business-info-template.md` | metrics, KPIs, growth model | Current revenue/retention/growth focus