
How to Choose the Few Metrics That Actually Matter
On this page
Analytics & Data
The traffic line on the dashboard climbed for three straight quarters, a clean diagonal up and to the right, and on the same screen, one tile over, the cash in the account fell every single month of those three quarters, and nobody on the weekly call ever put those two lines next to each other and asked what the first one was actually buying. Sessions were up forty percent year over year. The owner mentioned it on every call. Meanwhile the business was quietly running down its reserve, because the traffic was arriving on pages that converted worse than the traffic it replaced, and the average order behind each sale had shrunk, and the metric everyone was proud of had no edge on the metric that decided whether payroll cleared. The number went up. The business got worse. Both things were true at once, and the dashboard was built so that you could stare at it for an hour and never notice.
A metric that matters is a number that maps directly to a decision and to money, chosen because changing it would change what the business does, in the context of a small or mid-sized business deciding which few figures to run on instead of tracking everything a tool happens to report. That definition has two clauses and both are load-bearing. A number that does not change a decision is decoration. A number that changes a decision but has no honest line to cash is a distraction with good production values. The metrics that pass both tests are few, far fewer than any tool's default dashboard, and the entire job of metric selection is finding those few and having the discipline to cut the rest.
How to choose the few metrics that matter
You do not choose metrics by picking the interesting ones out of a tool. You choose them by starting from the business and asking, for every candidate number, the same two questions, and keeping only the numbers that survive both.
Map every candidate to a decision and to money, or cut it
For each number on the table, ask first: if this moved, what would we do differently. Not "would we notice", not "would we care", but specifically, what action changes. If the honest answer is "nothing, we would just look at it", that number is not a metric worth watching closely. It might be worth knowing once. It is not worth a permanent tile and a recurring sentence on the weekly call.
Then ask the second question: where is the line from this number to money. Sometimes the line is one step. Revenue per customer maps to money in one move. Sometimes it is two or three steps, and that is fine, as long as you can actually draw the steps. Trial-to-paid conversion maps to money because more paid accounts at a stable price is more revenue, and you can say that out loud without flinching. The test is not whether the line is short. The test is whether you can draw it at all without inventing a step.
A number that passes the first test but fails the second is the most dangerous kind, because it feels operational. A team can watch "tickets resolved per day" climb and feel productive, and there is even a decision attached to it: staff up if it falls. But if resolving more tickets faster has no honest line to retention or revenue, and sometimes it does not, because the fastest way to close a ticket is to close it badly, then the number is governing a decision that does not move money. Both questions, every candidate, no exceptions. The list that survives is short on purpose.
An example: the vanity metric that climbed while the cash fell
Take an unnamed subscription tool, a small one, a few thousand paying accounts. The dashboard the founder watched led with signups. Signups had a beautiful trend. The team ran a referral push, signups jumped, the line on the screen looked like success, and the founder reported growth to anyone who asked.
Underneath, three numbers nobody had on the dashboard told the real story. Of the new signups, the share that ever reached the point in the product where it became useful had dropped, because the referral traffic was lower intent than the traffic it replaced. The accounts that did convert were converting onto the cheapest plan at a higher rate than before. And the existing accounts, the ones already paying, were canceling at a rate that had crept up for two quarters without anyone watching it, because the dashboard had no tile for it. Signups, the number everyone watched, went up. Recognized revenue, the number almost nobody watched, went sideways and then down, because more cheap accounts arriving could not outrun better accounts leaving.
The signup line was not lying. It was accurately reporting a thing that did not matter on its own. It mapped to a decision in theory, spend more on referral, and it had a line to money in theory, signups become customers become revenue. But the line had two hidden steps, conversion quality and retention, and both had quietly moved the wrong way, so the in-theory line to money was severed in practice. That is the anatomy of a vanity metric: not a fake number, a real number whose link to money has been cut somewhere the dashboard does not show.
Tracking everything is how you see nothing
The instinct, when you are not sure which numbers matter, is to track all of them and sort it out later. It feels safe. It is the opposite of safe. A dashboard that shows everything shows nothing, because the few numbers that decide the quarter are sitting in a grid of forty tiles that all look equally important, and a busy operator scanning it for ten seconds before a meeting cannot tell the load-bearing wall from the wallpaper.
The cost of a fifty-metric dashboard: the five that decide the quarter get buried
Visibility is not coverage. Putting a number on a screen does not mean anyone is acting on it; it usually means the opposite, because a number that shares a screen with forty-nine others has been demoted to ambient noise. The cost of the everything-dashboard is not the cost of collecting the data. It is the cost of attention. Every tile that does not change a decision is competing for the same ten seconds as the tiles that do, and it wins more often than it should, because it is often the prettier number. Vanity metrics trend up and to the right by their nature. The numbers that actually matter are frequently flat, or down, or noisy, and they lose the visual competition to a clean rising line that means nothing.
A grid of forty numbers. Sessions, page views, social followers, email list size, app downloads, average session duration, bounce rate, tickets opened, tickets closed, NPS, and thirty more. All present, all updating, all equally sized. The owner glances at it before the weekly call and lands on whichever number moved most, which is usually a high-volume vanity number because those swing the most. No single tile is tied to a named decision. In a year, not one of the forty has been the reason a decision was made differently. The dashboard is a feeling of being informed, not an instrument.
Five numbers. Each one has a sentence attached: if this moves past here, we do this. Net revenue retention, new revenue, gross margin, the one leading indicator that moves before revenue does for this model, and cash runway. The owner reads it in ten seconds and knows whether anything needs a decision this week. Four of the five are sometimes flat or down and that is the point: they are reporting reality, not flattering it. Every tile has changed at least one real decision in the last year, which is the only test a tile has to pass to keep its place.
The five-tile version is not a worse, simplified version of the forty-tile one. It is the better instrument, because an instrument that surfaces the signal is more useful than one that buries it under everything it can technically display. A shorter list is not a compromise forced by limited screen space. It is the entire point of selecting.
Leading versus lagging, and why owners over-weight the lagging ones
Among the numbers worth keeping, there are two kinds, and most owners systematically over-trust the wrong one. A lagging indicator confirms an outcome after it has already happened and can no longer be changed for the period it describes. Last month's revenue is a lagging indicator. It is true, it is important, and by the time you can read it, last month is over and nothing you do now will alter it. A leading indicator moves before the outcome, while there is still time to act, and is therefore the one a small team can actually steer with.
For the subscription tool, recognized revenue is lagging: it confirms what already happened. The share of new accounts that reach the activation point in their first week is leading: it moves now and tells you what next quarter's revenue is being shaped into while you can still change it. Owners over-weight the lagging number for a simple, human reason. Lagging numbers are certain and clean. Revenue is revenue. Leading numbers are noisier and require believing that a soft early signal predicts a hard later outcome, which feels like a leap. So the dashboard fills with certain, clean, lagging numbers that can no longer be acted on, and the noisy, early, actionable numbers get left off because they are uncomfortable. The discipline is to keep at least one genuine leading indicator per model and to weight it as heavily as the lagging one it predicts, precisely because it is the only one you can still do anything about.
The selection procedure
There is a repeatable way to get from a tool's default dashboard to the few numbers your business actually runs on. It is three moves: start from the model, apply the three-to-five test, and run every survivor through the kill criteria.
Start from the business model, not the tool's default dashboard
The default dashboard is wrong for you by construction. It was designed to be reasonable for the median customer of that tool, which is no one. An analytics tool ships traffic and engagement tiles because that is what it can see, not because those are what your business runs on. A help desk ships ticket-volume tiles for the same reason. Starting from the tool means letting whichever vendor you happened to buy decide what your business measures, which is roughly as sound as letting your thermometer decide what temperature the building should be.
Start instead from one question: how does this specific business make and lose money, in its own terms. Write the actual money mechanics in plain language first, with no metrics in the sentence. A subscription business makes money by acquiring an account, keeping it long enough to recover what it cost to acquire, and growing it; it loses money when accounts leave faster than that, or arrive too cheap to ever pay back. A services firm makes money by selling skilled hours and delivering the work for less than it billed; it loses money when people sit idle or when jobs cost more to deliver than they were quoted at. Only once that sentence is written do you ask which numbers track each clause of it. The metrics fall out of the money mechanics. They do not fall out of the tool.
The three-to-five test
The target is three to five metrics watched closely. Not one: a single number, however good, hides the trade you might be making to move it, the way revenue can rise while margin collapses. Not forty: past roughly five, the marginal number is no longer adding signal, it is adding load and diluting the five that matter. Three to five is not a magic constant; it is the empirical range where a human running a business while reading the dashboard can actually hold the whole picture in their head and notice when a decision is required. More than that and the dashboard goes back to being wallpaper.
The three-to-five test, in one place. Pick the smallest set of numbers such that, taken together, they tell you whether the business is healthy and whether a decision is needed this period, and removing any one of them would blind you to a way the business could be quietly going wrong. If a candidate can be dropped without creating a blind spot, drop it. If dropping it would hide a real failure mode, it stays. The right number is almost always between three and five. If your list is longer, you have not finished selecting; you have finished collecting.
Kill criteria for a vanity metric (numbered)
Every survivor of the model and the three-to-five test still gets run through a kill test. A metric fails, and comes off the dashboard, if any of the following is true.
- It only ever goes up. If, by the nature of the number, it essentially never goes down regardless of business health, it cannot signal trouble and therefore cannot drive a decision. Cumulative signups, total registered users, all-time downloads: these only climb. A number that cannot deliver bad news is not an instrument.
- No decision is attached. If you cannot state, in one sentence, what you would do differently if it crossed a threshold, it is not governing anything. "We would look into it" is not a decision. A real decision names an action.
- The line to money requires an invented step. If drawing the path from the number to revenue or cost forces you to assume a link you have not verified, the metric is mapped to money only in theory. Hold it to the standard of a line you could defend out loud, not one you hope holds.
- It moves only as a side effect of something you already track better. If a number rises and falls almost entirely because another metric you watch more directly rose and fell, it is a redundant shadow. Keep the upstream number; cut the shadow.
- It rewards an action that can be gamed against the business. If a team can move the number by doing something that helps the number and hurts the business, tickets closed fast by closing them badly, it is an actively dangerous metric, not a neutral one. These are the first to cut.
A number that survives the model, the three-to-five test, and all five kill criteria is a metric that matters. Most numbers on most dashboards do not survive. That is the expected outcome, not a sign you did it wrong.
The right set by business model
The same dashboard does not fit three different businesses, and the clearest way to show that is to build the short list for each of the three common shapes. The numbers are different because the money mechanics are different. None of these are exhaustive; each is the spine the rest hangs off.
Subscription: retention and the movement of accounts you already have
A subscription business lives on the accounts it already has, far more than on the ones it is about to get. The spine is therefore retention and the net movement of existing revenue, not gross new sales. The few numbers:
Net revenue retention is the single most important number, because it captures, in one figure, whether the revenue from accounts you already had a year ago grew or shrank after accounting for upgrades, downgrades, and cancellations. If accounts you already have are expanding faster than others are leaving, the business grows even with no new sales; if they are contracting, new sales are running up a down escalator. Logo churn, the rate at which accounts leave outright, sits next to it, because revenue retention can be propped up by a few accounts expanding while many small ones quietly leave, and you want to see both. Then a leading indicator: the share of new accounts that reach the activation point, the moment the product becomes genuinely useful, within their first week, because that share predicts which of this period's signups become next period's retained revenue while you can still influence it. New revenue is on the list, but deliberately not at the top, because for this model it is the number most likely to be flattered by a vanity push while the account base rots underneath. Signups are not on the list at all. They are the metric from the opening scene: a real number whose line to money runs through conversion quality and retention, both invisible on the signup line itself.
Project-based services: utilization and quoted-versus-actual cost to deliver
A project-based services firm sells skilled hours and makes its margin in the gap between what a job was quoted at and what it actually cost to deliver. Retention metrics built for subscription are close to meaningless here; the spine is different.
Utilization, the share of available billable hours that were actually billed, is the first number, because idle skilled capacity is the most expensive thing this business owns and the fastest way it bleeds without anyone noticing, since idle time does not generate an invoice that anyone questions. Quoted-versus-actual margin per job is the second and arguably the real one: for completed work, what was billed against what it genuinely cost to deliver including the hours that ran over the estimate. A firm can be busy, fully utilized, and unprofitable, because it is utilized on jobs it underquoted, and only this number shows that. The trap is reading utilization alone and feeling healthy while every fully-utilized job loses money on delivery. A leading indicator for this model is the trend in the estimate-to-actual gap on jobs as they progress, not just after they close, because a gap that is widening across the open jobs is next quarter's margin problem arriving early enough to reprice or rescope. Revenue is a lagging confirmation here, useful but not steerable; it tells you what the quoting and the utilization already did.
Transactional retail: margin per transaction and repeat rate
A transactional retailer makes money on the margin of each sale and on how often a buyer comes back to make another one. Volume of transactions on its own is this model's classic vanity number, because more sales at collapsing margin is the express route to being busy and broke.
Gross margin per transaction is the anchor: not revenue per sale, margin per sale, after the cost of the goods, because a discount-driven volume spike inflates revenue and transaction count while the number that pays the rent goes the other way. Repeat purchase rate, the share of buyers who come back within a sensible window for the category, is the second number, because acquiring a buyer typically costs more than the margin on their first purchase, so the model only works if a meaningful share return, and a quarter of strong first-time sales with no repeats is a quarter of buying revenue at a loss. A leading indicator is the early repeat signal: the share of recent first-time buyers who have already made a second purchase faster than the historical norm, which forecasts the cohort's eventual repeat rate while there is still time to act on it. Total transactions stays off the headline list, or sits demoted next to margin where it cannot be read alone, because read in isolation it is the number most likely to look great in exactly the quarter the business is hurting.
Metric selection versus what it gets confused with
Four pairs get conflated constantly, and conflating any of them puts the wrong number on the dashboard. Each pair is worth separating cleanly.
A metric vs a vanity metric
A metric that matters changes a decision and tracks money. A vanity metric only ever goes up and changes nothing you do. The tell is not whether the number is real, both are usually real, but whether it can deliver bad news and whether bad news on it would trigger an action. Net revenue retention can fall, and if it does you act; it is a metric. All-time signups essentially cannot fall and triggers nothing when it rises; it is vanity. Same dashboard real estate, opposite value. The fastest sort: ask the number to tell you something bad. If it structurally cannot, it is vanity.
A leading indicator vs a lagging indicator
A leading indicator moves before the outcome, while you can still act; a lagging indicator confirms the outcome after it is fixed for that period. First-week activation share is leading for the subscription model: it moves now and shapes revenue you have not booked yet. Recognized revenue is lagging: by the time you read it, the period that produced it is closed. Both belong on the list. The error is keeping only lagging numbers because they are cleaner and more certain, which leaves the dashboard accurate about a past you cannot change and silent about a future you still can.
A metric vs a KPI (a KPI is a metric with a target and an owner; hand that to guide 4)
A metric is a number you have selected because it maps to a decision and to money. A KPI is that same number after it has been given a target, a named owner, and a trigger that says what happens when it crosses the line. Selection produces the metric. It does not produce the target, the owner, or the trigger, and deliberately so: deciding the threshold and assigning who acts is a separate discipline with its own failure modes. This guide stops at the chosen number. Turning that number into something a specific person is on the hook to act on is the job of turning metrics into KPIs people actually act on, which is where selection ends and actionability begins. Choose the metric here; set its target and its owner there.
An input metric vs an outcome metric
An input metric is something you do; an outcome metric is the result it is supposed to produce. Hours spent on onboarding outreach is an input. Activation share is the outcome that outreach is meant to move. The mistake is treating an input as if it were the outcome, watching outreach hours climb and assuming activation must be improving, when the whole question is whether the input is actually producing the outcome. Keep at least one true outcome metric per model on the list. Inputs are worth tracking only as levers on an outcome you are also watching, never as a stand-in for it.
What choosing well changes
A well-chosen short list is not the end of the work; it is the input the rest of the discipline runs on. Selecting well changes three downstream things, and naming each one also names where this guide stops and another picks up.
It makes a one-page measurement plan possible
You cannot fit forty metrics on one page in a way anyone will read, and you should not try. A one-page measurement plan, the thing that says here are our numbers, here is what each is for, here is who looks and how often, is only possible because selection already cut the list to a length that fits a page and a human's attention. Selection is the precondition. The plan is the composition of the selected set into something a team runs on a cadence, and that composition is its own procedure, owned by building a one-page measurement plan. A good short list is what makes that page possible; the procedure for assembling and operating the page lives in that guide, not this one. Choose the few here; compose them into the running plan there.
A chosen metric still needs a target and an owner
A selected metric on a dashboard is necessary and not yet sufficient. Net revenue retention sitting on a screen tells you nothing about whether anyone should be alarmed today, because a number without a target is just a number, and a target without an owner is a wish. The chosen metric becomes something the business acts on only once it has a threshold that defines good and bad and a named person accountable for the response when it crosses. That step, the target and the owner and the trigger, is exactly the seam handed to turning metrics into KPIs people actually act on. Selection answers which numbers. That guide answers what good is and who acts. Do not set the target here; choose the right number to set a target on, and hand it across cleanly.
Selected metrics are worthless on a substrate nobody captured or cleaned
There is a quiet assumption under everything above: that the few numbers you selected can actually be measured truthfully. Often they cannot, because the event was never captured, or it was captured into three systems that each define it slightly differently, or the field that the metric depends on is filled in by hand and is wrong as often as it is right. A perfectly chosen metric computed from data nobody captured cleanly is a confident number that is quietly false, which is worse than no number, because a false number still drives decisions, just bad ones. The selection is only as honest as the substrate underneath it.
Getting that substrate right, the event capture, the consistent definitions across systems, the ongoing cleanup as the business changes, is not a one-time setup. It is sustained execution work, and it is precisely the work most small teams do not have anyone staffed to own, which is why the chosen numbers so often sit on a foundation that silently drifts. When that is the gap, building and maintaining a trustworthy data foundation is the data foundation work Iron Goo runs for small teams: the unglamorous, continuous job of making sure the few numbers you decided to run on are computed from data that is actually captured and actually clean. Reading those numbers without fooling yourself, once the substrate is sound, is a further discipline of its own and belongs to reading your numbers without fooling yourself. Select the few; make sure they sit on data you can trust; then read them honestly.
Where this leaves you, and the first tile to cut
Metric selection is the first move in an SMB measuring what actually moves the business instead of what a tool happened to default to, and it is the move everything else in this pillar is built on: a chosen number is what you later give a target and an owner, what you later compose into a one-page plan, and what you later learn to read without fooling yourself. Get the selection wrong and every downstream step is faithfully operating on the wrong numbers. Get it right and the rest of the discipline has something true to work with.
The action is not to build a new dashboard. It is to take your current one, find the tile your team is proudest of, and run it through the two questions and the five kill criteria honestly. If it only ever goes up, or no decision is attached to it, or its line to money needs an invented step, that is the first tile to cut, today, before you add anything. Then take the survivors to turning metrics into KPIs people actually act on and give each one a target and an owner. The shorter list is not the smaller version of the work. It is the work.


