Lesson 6: Stop Measuring Everything. Start Measuring the Things That Actually Matters.
Think about this: your team tracks half a dozen metrics, yet no one knows if things are really getting better. The issue probably isn’t with your data. It’s what you’re choosing to care about.
Most organizations only notice things are off after they’ve built a fancy dashboard. You see conversion rates, response times, customer satisfaction scores, Net Promoter Scores, time-to-close, onboarding completion, churn – the list grows every quarter until everyone’s staring at a wall of numbers. Still, no one can answer the only question that really counts: are we actually getting better at delivering value to customers?
That’s the trap: turning everything into a metric. Honestly, it’s easy to fall into because adding a metric feels like progress. Finding something to measure, tracking it, adding discipline – all that feels responsible. But often, all you get is noise. The signal you need just gets buried.
Here’s the deal: Too Many Metrics = Confused Teams. One Signal = Real Alignment.
Measuring operations isn’t the same as understanding them. You could track twenty numbers and know next to nothing, or just pick one truly meaningful metric and actually know if you’re on the right path. Once you’ve mapped your process, diagnosed weak spots, and figured out the real failures, you need to decide what “winning” looks like – in one sentence, no theory, nothing complicated.
One signal. One shared definition. Everyone clear on what matters.
Sounds basic, but it’s harder than it looks. Teams have to agree on what’s actually important, which means agreeing that other things are less important. That’s when old assumptions and clashing priorities bubble up. That’s uncomfortable, but seriously – it’s worth it. When everyone pulls toward one clear outcome, the whole team moves faster and smarter.
A Real Story: Too Many Metrics, No Direction, One Change That Worked
Here’s what drove this home for me. A company’s onboarding flow used six metrics: completion rates, time-to-activation, support ticket volume, 30-day NPS (Net Promoter Score), feature adoption, and an overall customer health score. All valid, all useful on their own.
But I asked the team which one really told them if onboarding was working. Six different people gave six different answers. Product cared about feature adoption. Support focused on tickets. Customer success liked the health score. Leaders pointed at NPS.
Everyone worked hard, but nobody was rowing in the same direction.
We did something simple but tough: forced a single choice. After talking it out, the team agreed to focus on just one signal – time to first value. That’s the time it takes for a new customer to sign up and use the product’s main feature for the first time. We wrote it down in a sentence, put it up on the wall, and called it the North Star for 60 days.
Here’s what changed:
Decisions shifted right away. Teams started making choices to speed up that journey instead of each optimizing their own favorite stat. Handoffs between teams got tighter because everyone now shared the same goal. Documentation stayed focused on helping customers find value faster, not covering every edge case. And the metric? It steadily improved. Even better, some “secondary” stats, like support volume and NPS started moving up too, without anyone intentionally targeting them.
That’s the kicker. When you pick the right leading indicator, one that really connects to customers feeling value, the other metrics often take care of themselves.
How to Pick Your Signal (The Practical Version)
This step takes real thought. Picking the wrong signal leads teams off course, and it sometimes takes weeks before anyone notices.
Start by asking: when do customers first feel the value you promised?
That moment is almost always where your North Star metric lives. Some examples:
- Time to first value: How long from signup to actual meaningful use?
- % first-contact resolution: How often does support fix things right away, without any follow-ups?
- Onboarding in 3 days: Did customers hit success within a tight time window?
Once you have your signal:
- Write a one-sentence definition, clear enough that anyone measuring would get the same result.
- Get real agreement from every team. Not just “okay, whatever” – actual buy-in that this is the number everyone cares about for now.
- Post it somewhere visible – make it a part of daily life, not a forgotten document in the drive.
And check in after a set time. If things are tracking in the right direction but customers still aren’t happy, or if the signal stays flat while you know something’s breaking, swap it out. Don’t get attached to a bad metric. The point isn’t to be right about the metric; it’s to be honest about how you’re doing.
The Real Lesson
Picking the wrong metric will cost you. Maybe not fatally, but it does burn your team’s energy on things customers don’t really care about.
The easy mistake? Picking a stat that’s super easy to measure, but not all that meaningful. Emails sent, tickets closed, calls made – those are simple to collect, but they don’t tell you much about whether the customer’s experience is really getting better.
If your one signal doesn’t budge when your customer experience improves, it’s time for a new signal. Change it fast, no shame. You’re not trying to “win” at the original pick; you’re trying to get to the truth.
One clear signal. Simple definition. True alignment. That’s where progress starts.
So look at your dashboard right now. If you had to delete every stat but one – the only number that tells you, honestly, if you’re delivering customer value – which one would stick around? If you can’t answer right away, that’s where your work starts.
In my next post I will be discussing why your improvement initiatives keep failing and how to fix them, see you then.