Metrics Ownership

What problem does it solve?

This Skill addresses the problem of teams building features without a clear understanding of whether they are successful, leading to development in the dark. It emphasizes the principle that teams must define and own the metrics for their features before development begins.

Core Features & Use Cases

• Feature Success Definition: Guides teams to ask critical questions about user impact, measurement, and success criteria for each feature.
• North Star Metric Identification: Helps define a single, overarching metric that represents the true value of a product.
• Input vs. Output vs. Outcome Metrics: Differentiates between activity, output, and outcome metrics, prioritizing outcome metrics for accountability.
• Story-to-Metric Linking: Provides a template for embedding success metrics directly within each development ticket.
• Use Case: A team developing a new contract editing feature will define success by measuring completion time and error rates, aiming for under 5 minutes and less than 1% errors, respectively, before starting development.

Quick Start

Use the Metrics Ownership skill to define success metrics for a new feature.