duo-metric-design
Choose, weight and defend the single number your team is graded on, so that moving it means users actually got value rather than merely spent time. Covers putting activity weights inside the formula instead of a memo, threshold-percentage goals versus aggregate totals, pairing a growth metric with a daily-readable quality proxy, refusing to score a vague goal and decomposing it instead, giving producers leading indicators while they author, per-unit quality maps, and ranking a feedback queue larger than you can read. Use when someone asks what metric a team should own, how to pick a north star, why the number went up while nothing actually improved, how to build a counter-metric next to a growth metric, how to stop metric gaming, how to keep a fast lever from beating a slow structural fix, or how to triage a feedback firehose.
- Version
- 2.0.0
- License
- MIT
Pinned to revision 78072c9528fb, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/duo-metric-design/SKILL.md
- skills/duo-metric-design/references/leading-indicators-for-the-people-doing-the-work.md
- skills/duo-metric-design/references/pair-every-growth-metric-with-a-quality-proxy.md
- skills/duo-metric-design/references/per-unit-quality-map-not-aggregate-score.md
- skills/duo-metric-design/references/put-the-weight-in-the-formula-not-the-memo.md
- skills/duo-metric-design/references/refuse-to-measure-the-vague-goal.md
- skills/duo-metric-design/references/score-the-feedback-queue-do-not-drain-it.md
- skills/duo-metric-design/references/threshold-percentage-not-aggregate-total.md
Every link opens the file at its source, pinned to the revision this page describes.