Helps clarify target group, value, goals, and priorities in concrete terms. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.
Counter Metrics
Moves target group, value, goals, and priorities toward a concrete result through "name the main metric", "collect possible unintended side effects", and "use counter metrics alongside the main metric in reviews".
What undesirable side effect would increasing the top metric cause, and how can we detect it early?
The team follows the steps "name the main metric", "collect possible unintended side effects", "select the best proxies as counter metrics", "define thresholds and ownership", and "use counter metrics alongside the main metric in reviews". Each step is made visible. At the end, a counter-metric list and guardrail definitions are available so decisions, tests, or actions can continue directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Name the main metric
- 2Collect possible unintended side effects
- 3Select the best proxies as counter metrics
- 4Define thresholds and ownership
- 5Use counter metrics alongside the main metric in reviews
The runsheet guides execution with 5 phases, timeboxes, 6 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Growth teams with experimentation
- OKR follow-up
- Platform teams
Not good for
- Very early prototypes without a data pipeline
Deep dive
Counter Metrics, also called Guardrail Metrics, add safeguards around any main metric. If engagement rises, the counter metric checks whether that comes at the cost of complaints, abandonment rates, or performance. The idea comes from experimentation platforms and is now standard in large product teams.
Agree on at least one counter metric per main metric. Fix thresholds in writing before the experiment starts.
Counter Metrics Working TemplateCompact working template for Counter Metrics with context, input, output artifacts, and next step.markdown
counter-metrics-working-template.md
Compact working template for Counter Metrics with context, input, output artifacts, and next step.
Counter Metrics Working Template
Goal
Protective metrics that surface unwanted side effects of a primary metric.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Counter-metric list:
- Guardrail definitions:
Assumptions and open questions
- ...
Decision / next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
Statt Counter Metrics, wenn du mit HEART Framework Nutzererlebnis mit Happiness, Engagement, Adoption, Retention und Task Success messen willst.
Similar methods
All methodsMoves target group, value, goals, and priorities toward a concrete result through "define the top metric", "describe the main driver of the top metric", and "set the review cadence".
Links data, insights, beliefs, and bets so strategy and product decisions become traceable and reviewable.
Turns target group, value, goals, and priorities into a tangible result by drafting a raw goal, checking specificity, and defining time relevance.
Moves technical problems, hypotheses, and next steps toward a concrete result through "formulate the goal clearly", "derive probing questions for each goal", and "set the review cadence".
Moves observations, needs, and patterns toward a concrete result through "define a goal for each HEART dimension", "identify signals for each goal", and "agree on a review cadence".
Statt Counter Metrics, wenn du mit HEART Framework Nutzererlebnis mit Happiness, Engagement, Adoption, Retention und Task Success messen willst.
Turns customer value, goals, and priorities into a tangible result through defining objectives, setting key results, and running review and adjustment.