Product Strategy Decision method
Complements a target metric with guardrail and counter metrics so local improvement does not hide material harm.
Counter metrics state what must not degrade while the primary metric improves. They come from counter-hypotheses, system boundaries, and affected groups, and need equally clear formulas and decision thresholds.
Which material degradation could the target metric hide, and which counter metric stops or qualifies the decision?
Counter Metrics uses one primary metric with explicit counter-hypotheses, guardrails, and stop thresholds. Assessments remain justified and context-bound.
Counter-hypotheses
State plausible incentives, displacement, and affected groups for each target metric.
Counter metrics
Define a measurable counter metric with population, formula, and window for each harm hypothesis.
Set thresholds
Set baseline, stop threshold, segment rules, and decision logic before optimisation.
Review outcomes
Evaluate primary and counter metrics together and add newly discovered side effects.
Update the set after incentives fail, segments shift, or new effects emerge, retaining historical definitions.
Useful for experiments and KPI control with optimisation risks. They do not replace ethical or legal review.
counter-metric contract with traceable sources, assumptions, and domain decisions.
Owners, dates, and next review for counter-metric contract.
Fictional worked example
one primary metric with explicit counter-hypotheses, guardrails, and stop thresholds as a precise working structure with a fictional example.
| Item | Primary metric | Counter-hypothesis | Counter metric | Guardrail | Decision |
|---|---|---|---|---|---|
| counter-metric contractWorked example | Completed reviews / started reviews; target +10%. | Fast shallow completions increase. | Reviews <5 min / completed reviews per week. | Stop at +2 pp; new teams separately. | Roll out only if primary target passes without guardrail breach. |
The example demonstrates the domain logic of Counter Metrics; worksheets remain blank.
Microsoft Experimentation Platform: Overall Evaluation Criterion
Start with the core question: Which material degradation could the target metric hide, and which counter metric stops or qualifies the decision?
When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions.
It places matching counter-indicators alongside the primary metric and sets thresholds for warning signals. This keeps optimization tied back to quality, safety, or user experience where a single headline number would otherwise create the wrong incentives.
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.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Your feedback helps shape the next improvements to methodatlas.
Plan Counter Metrics around its domain steps and the concrete decision question.
To be confirmed
To be confirmed
Establish and review the practice Time: 45–60 minutes initially; review per experiment
Complete this worksheet on paper or in your own document during the work.
| Item | Goal · formula · desired change | Potential harm and causal path | Formula · population · window | Baseline · stop threshold · segment | Primary + counter · action |
|---|---|---|---|---|---|
| counter-metric contract |
Enter only real input, sources, and decisions.
Microsoft Experimentation Platform: Overall Evaluation Criterion
Expected artifact: harm hypotheses
harm hypotheses · source · uncertainty · next decision
Entry:
...
Expected artifact: metric contracts
metric contracts · source · uncertainty · next decision
Entry:
...
Expected artifact: guardrail rule
guardrail rule · source · uncertainty · next decision
Entry:
...
Expected artifact: balanced decision
balanced decision · source · uncertainty · next decision
Entry:
...
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/counter-metrics/run-sheet
Fitting alternatives with decision guidance, followed by other related methods.
Instead of Counter Metrics, choose HEART Framework when you want to measure user experience through happiness, engagement, adoption, retention, and task success.
Moves 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.
Formulates goals precisely enough that measure, relevance, and deadline together form a clear basis for steering.
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".
Translates priorities into objectives, key results, and a review cadence so progress stays measurably steerable.
