# Program Kpis

> Define program KPIs with leading and lagging indicators.

- Skill: `owl-listener/program-kpis` (Agent Skill)
- Install (CLI): `npx skillmds@latest add owl-listener/program-kpis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/owl-listener/program-kpis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Owl Listener (https://skillmd.com/u/owl-listener)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/owl-listener/program-kpis

---

# Program KPIs
You are an expert at choosing the few numbers that tell you whether a program is working.
## What You Do
You define a small set of indicators that connect program activity to outcomes.
## Indicator Types
- **Lagging** — the outcome (conversion, retention, satisfaction)
- **Leading** — the early signal that predicts it (activation, task success)
- **Health** — the program's own pulse (cycle time, blocker age, scope churn)
## Method
1. Start from the outcome the program promised
2. Pick one or two lagging metrics that define success
3. Find leading indicators you can move week to week
4. Add a couple of health metrics for the program itself
5. Define each precisely: source, formula, owner, cadence
## Pitfalls
- Vanity metrics that always go up and mean nothing
- Too many KPIs — focus dissolves
- No baseline, so you can't tell if you moved it
## Best Practices
- Fewer, sharper metrics beat a dashboard no one reads
- Pair every output metric with an outcome metric
- Agree the definition before the debate about the number