KPI Selection Frameworks
Vanity metrics vs. actionable KPIs
A vanity metric moves in a direction that feels good but doesn't reliably connect to a business outcome you control or care about — total pageviews, social media followers, impressions. An actionable KPI is one where a specific, identifiable action would move it, and moving it has a traceable connection to a business result that matters (revenue, retention, pipeline). The practical test for any proposed KPI: if this number moved 20% in either direction tomorrow, would anyone know what specific action to take, and would that action matter to the business? If the answer is no to either half, it's a vanity metric dressed up as a KPI.
Leading vs. lagging indicators
Lagging indicators (revenue, churned customers, closed-won deals) measure outcomes after they've already happened — they're the ultimate scoreboard but arrive too late to change the thing that produced them. Leading indicators (demo requests, trial activations, email engagement rate, pipeline velocity) correlate with and precede those outcomes, giving enough lead time to intervene before the lagging number is locked in. A mature KPI framework pairs each lagging goal metric with one or two leading indicators that are known, from historical data, to reliably predict it — and tracks the leading indicators operationally day-to-day, reserving the lagging metric for retrospective accountability.
Common KPI selection frameworks
| Framework | Core idea | Best fit |
|---|---|---|
| North Star Metric | One metric that best captures the core value delivered to customers, correlating with long-term business success | Product-led growth companies with a clear usage-to-value link |
| AARRR (Pirate Metrics) | Acquisition, Activation, Retention, Referral, Revenue — a funnel-stage breakdown | Startups needing a structured view across the full customer lifecycle |
| OKRs (Objectives & Key Results) | Qualitative objective paired with 2-4 measurable key results | Teams aligning quarterly priorities across departments |
| HEART framework (Google) | Happiness, Engagement, Adoption, Retention, Task success | Product/UX-focused teams measuring experience quality, not just volume |
A metric is only a good KPI in context of a specific goal
interface KpiCandidate {
name: string;
movableByTeam: boolean; // can the team directly influence it?
tracesToBusinessOutcome: boolean; // does moving it matter to revenue/retention/etc?
leadingOrLagging: "leading" | "lagging";
hasReliableDataSource: boolean; // can it actually be measured accurately?
}
function isViableKpi(candidate: KpiCandidate): boolean {
return (
candidate.movableByTeam &&
candidate.tracesToBusinessOutcome &&
candidate.hasReliableDataSource
);
// vanity metrics typically fail movableByTeam or tracesToBusinessOutcome,
// not hasReliableDataSource — that's the trap: good data on the wrong metric
}The counter-metric discipline
Optimizing a single KPI in isolation routinely produces a damaging side effect somewhere else in the business — a sales team incentivized purely on lead volume will hit the number by lowering lead quality bar, a growth team optimizing purely for sign-ups will tolerate rising churn among low-intent users acquired to hit the target. A mature KPI framework pairs every primary metric with a counter-metric that would catch the gaming behavior — lead volume paired with lead-to-opportunity conversion rate, sign-ups paired with 30-day retention. The primary metric answers "are we growing," the counter-metric answers "are we growing in a way that's actually healthy."
Too many KPIs is the same failure mode as too few, just slower
What's Next?
Choosing the right KPIs is the measurement half of goal-setting — translating those KPIs into a structured, time-bound commitment the whole team aligns around is the organizational discipline that determines whether tracking the right number actually changes behavior.
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.