Part of Build Product Features With PM Guidance
Product & Design Blueprint
Safety checkedDefine Success Metrics by Category
A skill that structures metrics into primary, secondary, guardrail, leading indicators, and anti-metrics with measurement methods and baselines.
What problem does this solve?
Defines complete measurement frameworks so you measure the right thing and catch regressions early. It translates vague goals into precise metrics with data sources, baselines, targets, and timeframes. It identifies anti-metrics so you catch perverse incentives before they damage your product.
How does it work?
- Say 'define metrics for [feature]' or 'what should I measure for [initiative]'. 2. Claude asks what you're trying to achieve, what you can currently measure, and your goal. 3. It structures your metrics into: primary metric (with definition, measurement method, baseline, target, timeframe), secondary metrics, guardrail metrics (what should NOT get worse), leading indicators (week-1 signals that predict long-term success), and anti-metrics (what going UP would actually be bad). Output: a metrics framework you can hand to analytics and engineering with no ambiguity about what success means.
Included Skills
No skills in this group
What's required to run this?
Triggered by 'define metrics', 'what should I measure', 'success metrics for [feature]', or 'KPIs for [initiative]'. Requires specificity in inputs. Vague goals produce vague metrics. Inherits your product context from CLAUDE.md.
Key Features
Primary Metric
Precise definition, exact measurement method, current baseline, target number, and evaluation timeframe.
Guardrail Metrics
What should NOT degrade. Includes current baseline and acceptable range. Prevents optimization in one area from breaking another.
Anti-Metrics
Metrics that going UP would be bad (e.g., high DAU plus low task completion equals user confusion). Forces thinking about perverse incentives.
Leading Indicators
Week-1 signals that predict long-term success, so you can validate earlier rather than waiting 90 days.
Instrumentation Flags
Flags metrics requiring new event tracking with [NEEDS INSTRUMENTATION] so you know what to ask engineering to build.
Tools in this Blueprint
About This Blueprint
- Industry
- Technology
More Blueprints to explore
⭐ Ask Nicely : Find your next reviewers
Pick promoters from your CRM, remove accounts with open escalations, overdue billing or a recent review, then create the G2 review campaign after you approve the list, send method and any incentive.
G2CRMSurvey or CS platform+4 moreCharlie Albuery
🤝 You Said We Did : Align your roadmap to real user feedback
Group recent G2 reviews into themes, check each theme against tickets in your work tracker, and return a ranked one-page brief that lists the themes with no ticket first.
G2Work trackerResearch repository+3 moreCharlie Albuery
👀 Wandering Eyes : Identify churn risk early
Match accounts renewing soon in your CRM to G2 buyer intent on competitors and your category, check usage, support and meetings, then rank the accounts and brief the CSM. Runs as a weekly sweep or on one named account.
G2CRMProduct usage analytics+4 moreCharlie Albuery