methodatlas
Product Strategy

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".

Core question
What undesirable side effect would increasing the top metric cause, and how can we detect it early?
LowWorkshop + async30-60 min
Purpose

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.

How it works

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.

Counter Metrics · Guardrails against Optimization DriftProtect a primary metric with counter metrics, thresholds, and stop rules so side effects become visible
Counter MetricsThe visual shows a primary metric, several counter metrics with thresholds, a stop rule, and a shared review cadence.Protect optimization with guardrail metricsCounter Metrics reveal whether a primary metric improves at the expense of quality, trust, or stability.Primary metricengagement risesGuardrail SetOptimization targetmore active usageComplaints< 2% ticketsPerformancep95 < 1.8 sDrop-off ratenot +5%Qualityerrors < 1%Stop rulestop experiment when aguardrail tipsReviewread primary and counter metricstogetherName side effects upfrontoptimize not onlythe targetfix thresholdsbefore the test

Flow

  1. 1Name the main metric
  2. 2Collect possible unintended side effects
  3. 3Select the best proxies as counter metrics
  4. 4Define thresholds and ownership
  5. 5Use counter metrics alongside the main metric in reviews

The runsheet guides execution with 5 phases, timeboxes, 6 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Growth teams with experimentation
  • OKR follow-up
  • Platform teams

Not good for

  • Very early prototypes without a data pipeline

Deep dive

In detail

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.

Facilitation

Agree on at least one counter metric per main metric. Fix thresholds in writing before the experiment starts.

Output artifacts
Counter-Metric-ListeGuardrail-Definitionen
Tags
Artifact templates
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.

HEART Framework

Statt Counter Metrics, wenn du mit HEART Framework Nutzererlebnis mit Happiness, Engagement, Adoption, Retention und Task Success messen willst.

Similar methods

All methods