metric-definition

Define a metric system with North Star, drivers, guardrails, and counter-metrics.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill metric-definition-ssiertsema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metric-definition
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/metric-definition/skills/metric-definition
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill metric-definition-ssiertsema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a coherent, operational framework to define product or initiative metrics that are both meaningful and measurable. This Skill provides a structured approach to creating a North Star, 3–5 input drivers, associated leading and lagging indicators, guardrails, and counter-metrics, with explicit definitions and ownership.

Core Features & Use Cases

  • North Star definition: Single, user-value oriented outcome that guides strategy.
  • Driver decomposition: Break the North Star into 3–5 measurable inputs that the team can influence.
  • Operational definitions: Provide precise formulas, data sources, populations, and exclusions for each metric.
  • Leading vs lagging and timing: Identify predictive signals and their time lag to lagging metrics.
  • Guardrails and counter-metrics: Build safety nets and anti-gaming measures to maintain healthy progress.
  • Diagram support: Generate metric trees and diagrams to communicate the model.

Quick Start

Define your North Star and 3–5 drivers, then write an initial operational definition for each driver.

Frequently Asked Questions about metric-definition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define a North Star metric and input drivers for my product?

To define a North Star metric, you identify a single user-value oriented outcome and break it down into 3–5 measurable input drivers. This structured approach creates a coherent metric system with operational definitions, formulas, and clear ownership.

What is the difference between leading and lagging indicators in a metric tree?

In a metric tree, leading indicators are predictive signals with a time lag before lagging metrics reflect the change. Leading indicators must have justified predictive power or be labeled as assumed leading, ensuring you measure readiness and track leading versus lagging relationships accurately.

How do I create operational definitions for product metrics with data sources?

Creating operational definitions involves specifying precise formulas, data sources, populations, and exclusions for each metric. This process identifies instrumentation gaps for resolution and documents data sources thoroughly, ensuring your product metrics are both meaningful and measurable.

What are guardrails and counter-metrics in a metric framework?

Guardrails and counter-metrics in a metric framework act as safety nets and anti-gaming measures. Building these into your metric system maintains healthy progress by preventing teams from optimizing input drivers at the expense of overall product health.

Best way to build a coherent metric system from scratch?

The best way to build a coherent metric system is applying a structured framework from Phase 1 to Phase 12. This produces a complete metric tree with a North Star, input drivers, and operational definitions, ensuring measurement readiness and clear leading and lagging relationships.

Can I generate metric tree diagrams for my operational definitions?

Yes, you can generate metric trees and diagrams to communicate your operational model. Diagram support visually maps the North Star, input drivers, and guardrails, making the operational definitions and metric relationships clear for stakeholders.