methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session60-90 minWorkshop or asyncCounter-Metric-Liste

Session: Counter Metrics

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 2-6. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Counter-Metric-Liste. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Confirm main metrics

    10 min

    For each top metric verify definition, calculation, and owner. Remove or clarify metrics without clear calculation before counter metrics are introduced. Hint: If the top metric itself is unclear, counter metrics are useless. Better stop here than build around the problem.

    FacilitatorCounter-Metric-Liste
  2. 2

    Phase 2: Collect side effects

    20 min

    Brainstorm 3-5 plausible negative side effects per top metric: what would also deteriorate if someone maximizes the top metric at any cost? Include categories such as performance, complaints, refunds, quality of engagement. Hint: Intentionally play out the worst interpretation of the top metric. If you are too polite here, the counter metric will not be effective.

    FacilitatorGuardrail-Definitionen
  3. 3

    Phase 3: Select counter metrics

    20 min

    Define 1-2 counter metrics per top metric that best proxy for the identified side effect. Define data source, calculation, and allowed variance in writing. Hint: No more than 2 counter metrics per top metric, otherwise every experiment hits some counter metric threshold and no one takes action.

    FacilitatorCounter-Metric-Liste
  4. 4

    Phase 4: Thresholds and consequences

    15 min

    Set threshold for each counter metric where the experiment is paused or investigation is triggered. Record owner and escalation path. Hint: Thresholds must be fixed before experiment start, not during review. Otherwise thresholds become retrofitted after the fact.

    FacilitatorGuardrail-Definitionen
  5. 5

    Phase 5: Wire into reporting

    10-15 min

    Add counter metrics directly in the top-metric dashboard so they appear automatically in each review. Record owner and review cadence. Hint: Counter metrics not in the same dashboard as the top metric are simply forgotten in reviews.

    OwnerCounter-Metric-Liste
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerCounter-Metric-Liste
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Counter Metrics

Goal

Artifact: Counter-Metric-Liste

Working Question

What undesirable side effect would increasing the top metric cause, and how can we detect it early?

Context

Current values and trends of top metrics (last 4 weeks); known historical side effects of past optimizations; planned experiments in the quarter; list of sensitive metrics (latency, refunds, NPS).

Setup

  • Format: Method session
  • Duration: 60-90 min
  • Mode: Workshop or async
  • Participants: One owner per top metric (PM or growth lead); one data analyst with tracking access; one engineering representative for performance counters; optional trust or support representative for complaint counters.
  • Owner: One owner per top metric (PM or growth lead)
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Counter-Metric-Liste. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Table with columns top metric, counter metric, definition, data source, threshold, owner; link to current metric documentation; list of active experiments; dashboard template.

Preparation

Share the table, pre-fill top metrics, leave data source column empty. Prepare a dashboard with top metric plus placeholder counter metrics so each agreed counter metric can be wired in immediately.

Agenda

  1. Phase 1: Confirm main metrics (10 min) Owner: Facilitator Action: For each top metric verify definition, calculation, and owner. Remove or clarify metrics without clear calculation before counter metrics are introduced. Hint: If the top metric itself is unclear, counter metrics are useless. Better stop here than build around the problem. Output: Counter-Metric-Liste

  2. Phase 2: Collect side effects (20 min) Owner: Facilitator Action: Brainstorm 3-5 plausible negative side effects per top metric: what would also deteriorate if someone maximizes the top metric at any cost? Include categories such as performance, complaints, refunds, quality of engagement. Hint: Intentionally play out the worst interpretation of the top metric. If you are too polite here, the counter metric will not be effective. Output: Guardrail-Definitionen

  3. Phase 3: Select counter metrics (20 min) Owner: Facilitator Action: Define 1-2 counter metrics per top metric that best proxy for the identified side effect. Define data source, calculation, and allowed variance in writing. Hint: No more than 2 counter metrics per top metric, otherwise every experiment hits some counter metric threshold and no one takes action. Output: Counter-Metric-Liste

  4. Phase 4: Thresholds and consequences (15 min) Owner: Facilitator Action: Set threshold for each counter metric where the experiment is paused or investigation is triggered. Record owner and escalation path. Hint: Thresholds must be fixed before experiment start, not during review. Otherwise thresholds become retrofitted after the fact. Output: Guardrail-Definitionen

  5. Phase 5: Wire into reporting (10-15 min) Owner: Owner Action: Add counter metrics directly in the top-metric dashboard so they appear automatically in each review. Record owner and review cadence. Hint: Counter metrics not in the same dashboard as the top metric are simply forgotten in reviews. Output: Counter-Metric-Liste

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Counter-Metric-Liste

Closeout

  • Update result artifact: Counter-Metric-Liste
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Counter-Metric-Liste: Counter Metrics

Working Question

What undesirable side effect would increasing the top metric cause, and how can we detect it early?

Context

Current values and trends of top metrics (last 4 weeks); known historical side effects of past optimizations; planned experiments in the quarter; list of sensitive metrics (latency, refunds, NPS).

Participants

  • Owner: One owner per top metric (PM or growth lead)
  • Participants: One owner per top metric (PM or growth lead); one data analyst with tracking access; one engineering representative for performance counters; optional trust or support representative for complaint counters.

Input

Table with columns top metric, counter metric, definition, data source, threshold, owner; link to current metric documentation; list of active experiments; dashboard template.

Template

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.

Completion Check

  • Counter-Metric-Liste is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Counter Metrics Working Template

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

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Counter-Metric-Liste.
  • Quarterly snapshot with date and responsible person. Record changes to thresholds or definitions in the edit log with rationale. Keep old thresholds, do not overwrite, so experiment evaluations stay comparable.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet