← ClaudeAtlas

kpi-outcome-measurementlisted

Design or review outcome measurement with precise definitions, units, populations, baselines, targets, data authority, and decision use. Use when a program or product needs measures that distinguish activity, output, outcome, and impact.
JovaniPink/skills · ★ 0 · AI & Automation · score 71
Install: claude install-skill JovaniPink/skills
# KPI and Outcome Measurement Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim. ## Workflow 1. Define the decision the measurement must inform and the outcome it represents. 2. Specify population, unit, numerator, denominator, exclusions, aggregation, time window, and segmentation. 3. Identify source systems, authoritative fields, transformations, latency, missingness, and ownership. 4. Record baseline, target, threshold, confidence, seasonality, and comparison method. 5. Distinguish leading indicators, lagging outcomes, guardrails, quality measures, and operational health. 6. Test incentives, gaming risk, survivorship, selection, attribution, privacy, and subgroup harm. 7. Define review cadence, decision rules, and conditions for retiring or revising the metric. ## Boundaries - Do not call activity or output an outcome without an explicit causal model. - Do not invent baselines, targets, or data quality. - Do not expose personal or sensitive data merely to increase measurement detail. ## Output Return Decision use, Metric dictionary, Data lineage, Baseline and target, Guardrails, Bias and gaming risks, and Review cadence.