north star metrics for developer tools
Explains how to pick a north star metric for a developer tool: what makes a good one, common candidates, and the traps to avoid. Use when defining product metrics for a devtool; not for vanity reporting or for teams that already have a working metric.
TL;DR
A north star metric aligns the whole team on the one number that captures value delivered. For devtools it usually sits at the moment the tool does its job, not at signup. Applies to developer tools with real usage to measure.
The query
north star metrics for developer toolsUse this when
- You are defining product metrics for a developer tool.
- The team needs one number capturing value delivered.
- The product has real usage to measure.
Not for
- You need a full metrics dashboard (the north star is one number, not a dashboard).
- The product has no users yet (pick a leading indicator instead).
- Leadership wants the metric to always go up (a north star must be allowed to move honestly).
Steps
- List the moments users get value: the successful run, the resolved issue, the shipped artifact.
Expected output: Candidate value moments grounded in real usage.
- Pick the one moment that best predicts retention and is measurable today.
Expected output: A single metric definition with a clear counting rule.
- Check it against the traps: it should resist gaming and reflect user value, not activity.
Expected output: A metric you would defend in a hard quarter.
- Instrument it, baseline it, and review it weekly with the team.
Expected output: A living number the team actually uses to make decisions.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst__ZsRRwPEC6M7ktUd0KJSWA
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.