TL;DR: Most small teams either track nothing or track too much, and both end in the same place: not knowing what’s actually broken. Averages make this worse because they smooth over the exact problems you need to see. This post covers how to pick one metric tied to your worst friction point, why averages hide disasters, and what to do the moment that number moves.
A support team at a mid-size company once looked fine on paper. Their average ticket resolution time was reasonable. Then someone pulled the actual distribution and found that 11% of tickets, the ones taking more than a day, accounted for 89% of all customer waiting time. The average had been hiding a real problem the whole time.
That’s what happens when you track too many business metrics, or the wrong one. You end up staring at a number that says “fine” while something underneath is actively breaking. This is a common trap for small teams. You either track nothing and run on gut feel, or you build a dashboard with fifteen numbers on it and check none of them consistently. Both end the same way: you find out something was wrong only after it cost you time, money, or a client.
There’s a simpler approach. Pick one metric tied to your worst pain point. Watch it every week. Ignore the rest until that one is boring.
How Many Business Metrics Should a Small Team Actually Track?
Most small teams do best with one to four metrics, not fifteen. Xero’s guidance for small businesses puts new businesses at three to four KPIs tied to immediate priorities, expanding only as the business grows. More than that, and the numbers stop informing decisions and start just existing.
The test isn’t whether a metric is interesting. It’s whether it changes what you do. If a number moved and you wouldn’t act any differently, it’s not worth tracking. Scoop Analytics frames this well: ask what action you’d take if the metric changed. If the answer is “nothing” or “I don’t know,” stop tracking it.
This matters more for a five-person team than a five-hundred-person company. You don’t have an analyst to interpret a dashboard. You have you, checking a number between client calls. Every extra metric is time you’re not spending fixing the thing that’s actually broken.
Why Do Averages Hide the Problems You’re Trying to Find?
Averages smooth out variation, which is exactly what hides the outliers doing the damage. A number can look completely fine while a small slice of your work is quietly falling apart underneath it.
Think about that support team again. Around 70% of their tickets got resolved in under an hour. The median case took 44 minutes, which sounds healthy. But the average was 24.3 hours, more than a full working day, because a small number of severely delayed tickets dragged the mean up without moving the typical case at all. The gap between the median and the mean was the whole story, and the average alone would never have shown it.
This is the same mistake Alex made with his marketing agency. He built a dashboard tracking fifteen metrics, including average project duration. That number had only crept up slightly, from seven weeks to eight. It looked manageable. But when he pulled the actual project list, four out of his last twelve projects had taken ten to twelve weeks, more than double what he’d promised clients. The average was blending his disasters in with his normal projects and calling the result “fine.”
Averages aren’t useless. They’re a starting point. But when a distribution has a long tail, relying only on the mean can turn a real problem invisible. If one student scores 100% and nine score 0%, the average is 10%, which tells you nothing true about anyone in that class. Your business metrics can do the exact same thing.
The One Metric That Matters
There’s a concept from the startup world worth borrowing here, even if you’re not running a startup. It’s called the One Metric That Matters, or OMTM, and it comes from the book Lean Analytics by Alistair Croll and Ben Yoskovitz. The idea is simple: at any given stage, there’s one number that deserves more attention than everything else combined.
The point isn’t that other numbers don’t exist. It’s that most founders, including solo operators, get pulled in a dozen directions by a dozen numbers, and end up acting on none of them with any real focus. Picking one metric forces a decision about what actually matters right now, instead of monitoring everything and reacting to nothing.
For a small service business, this doesn’t need to be complicated. It’s not a company-wide dashboard with a growth team behind it. It’s you, deciding which single number would tell you the moment your worst problem is getting worse, and checking it on a fixed schedule.
How Do You Pick the One Number Worth Watching Every Week?
Start from the friction point that’s already costing you the most, not from a list of KPIs you found online. Ask what number would spike specifically when that problem is happening.
This only works if you’ve already identified what actually hurts. If you’re constantly rewriting the same proposal sections, your number might be “hours spent per proposal.” If projects keep running long, it’s “projects that exceed the promised timeline by more than X weeks.” If client questions keep repeating, it’s “the same question asked more than twice in a month.”
The metric needs to be countable without new software. A tally in a notebook works. A single column in a spreadsheet you already use works. If picking this metric requires building new infrastructure, you’ve picked the wrong one, or you’re avoiding the actual work of watching it.
Check it on the same day, same time, every week. When the number moves, that’s your signal. When it doesn’t, that’s confirmation whatever you changed is holding.
What Should You Actually Do When That Metric Spikes?
The instinct is to react to the number itself. Resist that. Investigate the cause first.
If your metric spikes, ask why before you act. A metric is a proxy for something underneath it, not the full truth. If “projects running long” ticks up, that could mean scope creep, a new client type you haven’t adjusted for, or a bottleneck in one specific step. Reacting to the number without knowing the cause usually means fixing the wrong thing.
This is where your metric connects to your weekly habits. If you’re already running a weekly improvement review, checking your one metric is the first five minutes of that session. If the number moved, that’s the pattern you dig into that week, not a new fire to chase separately. And if it points to something worth logging, that’s exactly what an issue log is for: capturing the specific thing that broke so you can see if it’s a one-off or a pattern.
The goal isn’t a perfect metric that never spikes. It’s a metric that tells you early enough to fix something small instead of finding out three months later that it became expensive.
Signs You’re Tracking the Wrong Thing
If checking your metric makes you feel nothing, you’re tracking the wrong thing. A useful metric should be mildly annoying to look at when it’s high. It should make you want to fix something, not just note the number and move on.
This ties back to the difference between leading and lagging indicators. A lagging indicator tells you what already happened, like last month’s revenue. A leading indicator tells you what’s happening right now, in time to still change the outcome. Both have their place, but the weekly metric you’re picking here should lean leading. You want a warning, not a postmortem.
Another sign you’ve picked wrong: the metric is really an average hiding a smaller, worse story underneath it, the same trap covered above. If you’re not sure, ask whether the number would look different if you filtered out just the worst 10% of cases. If it would, you’re probably watching the wrong version of it.
Feeling like “everything looks fine but something’s still off” is often a sign that operational debt is building somewhere your current metrics don’t reach. That’s worth investigating directly rather than adding more numbers to your dashboard.
You don’t need fifteen metrics. You need one number, tied to your actual worst problem, checked on a schedule you’ll actually keep. Everything else is noise competing for your attention.
If you’re not sure which friction point deserves that metric in the first place, that’s exactly the diagnostic work covered in The Self-Managing Business, which walks through picking your one workflow, mapping how it really breaks, and choosing the single metric that signals when it’s getting worse. And if you’d rather have someone map this out with you directly, that’s what working with TAW looks like in practice.
Frequently Asked Questions
Most small businesses do best with three to six KPIs depending on their stage, with newer businesses closer to three or four tied to immediate priorities. More than that usually means the metrics stop driving decisions and start just existing on a dashboard nobody checks.
A lagging indicator tells you what already happened, like last month’s revenue or a completed project’s final timeline. A leading indicator tells you what’s happening right now, early enough that you can still act on it. Small teams benefit most from leaning on leading indicators for their weekly check-in metric.
Averages smooth out variation, which means a small number of severe outliers can get blended in with everything else until the number looks fine. A support team can have a reasonable-looking average resolution time while a small slice of tickets quietly account for the vast majority of actual customer waiting time.
Investigate the cause before reacting to the number itself. A metric is a signal, not the full explanation. Use your weekly review to dig into what specifically changed, and log it if it looks like a repeating pattern rather than a one-off.
A notebook or a single spreadsheet column is enough. If tracking your one metric requires new software or a dashboard build, that’s usually a sign you’ve picked something too complicated. The metric should be countable in under a minute, not something that needs infrastructure to maintain.