metrics-framework
Define product metrics with a North Star, input/output tree, and counter-metrics. Use when asked to define metrics, set up measurement, choose KPIs, pick a north star metric, or build a metrics framework. Prevents vanity metrics and gaming.
What this skill does
Define metrics that drive decisions, not dashboards that collect dust. Every metric must answer: "If this number changes, what will we do differently?" If nothing changes, it's a vanity metric.
## North Star Metric
One metric that captures the core value your product delivers to customers. Not revenue (that's an output). Not signups (that's vanity). The North Star reflects the moment customers get value.
Examples:
- Slack: Messages sent in channels with 3+ members
- Spotify: Time spent listening
- Airbnb: Nights booked
**Test:** If this metric goes up, does the company sustainably grow? If yes, it's your North Star.
## Input/Output Tree
Build a tree connecting your North Star to actionable inputs:
```
North Star: Weekly active teams with 3+ collaborators
|
+-- Acquisition: New signups/week
| +-- Website visitors
| +-- Signup conversion rate
|
+-- Activation: % who invite a teammate in 7 days
| +-- Onboarding completion rate
| +-- Time to first shared project
|
+-- Engagement: Documents edited per active team/week
| +-- Feature adoption (comments, mentions, sharing)
| +-- Return frequency
|
+-- Retention: % active at day 30
+-- Weekly return rate
+-- Feature breadth used
```
Each leaf is a metric a team can directly influence. The tree shows HOW inputs drive the North Star.
## Counter-Metrics
EVERY metric gets a counter-metric. This prevents gaming and ensures you're not optimizing one thing at the expense of another.
| Metric | Counter-Metric |
|--------|---------------|
| Signup conversion rate | Activation rate (don't lower the bar to get signups) |
| Time to first value | 30-day retention (don't rush users past learning) |
| Feature adoption | Task completion rate (don't push features that confuse) |
| Revenue per user | Churn rate (don't squeeze users into leaving) |
If the metric improves but the counter-metric degrades, you've optimized the wrong thing.
## Guidelines
- CRITICAL: ALWAYS pair every metric with a counter-metric. No exceptions.
- NEVER use vanity metrics: total signups, page views, total users, app downloads. These only go up and tell you nothing.
- NEVER track more than 5-7 metrics actively. If your dashboard has 20 charts, nobody looks at any of them.
- ALWAYS define metrics with exact formulas. "Activation rate" means nothing. "Percentage of new signups who invite at least one teammate within 7 days of account creation" is a metric.
- ALWAYS set a baseline before setting a target. You can't improve what you haven't measured.
- NEVER set targets without understanding the current number and why it's where it is.
- ALWAYS measure outcomes (user behavior) over outputs (features shipped).
---
*Built on Amplitude's North Star framework and the Linear Method. Skills from [productskills](https://github.com/assimovt/productskills).*
Related in Data & Analytics
clawarr-suite
IncludedComprehensive management for self-hosted media stacks (Sonarr, Radarr, Lidarr, Readarr, Prowlarr, Bazarr, Overseerr, Plex, Tautulli, SABnzbd, Recyclarr, Unpackerr, Notifiarr, Maintainerr, Kometa, FlareSolverr). Deep library exploration, analytics, dashboard generation, content management, request handling, subtitle management, indexer control, download monitoring, quality profile sync, library cleanup automation, notification routing, collection/overlay management, and media tracker integration (Trakt, Letterboxd, Simkl).
querying-soql
IncludedSOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
habit-flow
IncludedAI-powered atomic habit tracker with natural language logging, streak tracking, smart reminders, and coaching. Use for creating habits, logging completions naturally ("I meditated today"), viewing progress, and getting personalized coaching.
app-store-optimization
IncludedApp Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.
visualizing-data
IncludedBuilds dashboards, reports, and data-driven interfaces requiring charts, graphs, or visual analytics. Provides systematic framework for selecting appropriate visualizations based on data characteristics and analytical purpose. Includes 24+ visualization types organized by purpose (trends, comparisons, distributions, relationships, flows, hierarchies, geospatial), accessibility patterns (WCAG 2.1 AA compliance), colorblind-safe palettes, and performance optimization strategies. Use when creating visualizations, choosing chart types, displaying data graphically, or designing data interfaces.