The Score Isn’t the Intelligence
A score is only useful if it reflects the specific decision someone is trying to make. The number helps you sort a pile. The reasoning behind it is the intelligence — and when the explanation disappears, a judgment starts passing for the truth.
I almost made something worse this week by trying to make it smarter.
That happens more than I'd like to admit.
I was looking at how companies prioritize things. Customers. Accounts. Markets. Projects. Risks. Whatever the pile happens to be. And the obvious idea showed up right on schedule: wouldn't it be easier if everything just had a score?
A nice clean number. 87. 88. 89. High priority, medium priority, low priority. Simple. Looks great in a dashboard. Feels objective.
An 87 for what?
There was only one problem. An 87 for what?
That's the part I think we skip too often. A company can look incredibly attractive to one business and completely irrelevant to another. Same company. Same facts. Different answer.
A 200-person manufacturer might be a great target for one seller and a terrible one for another. A new location might be a huge deal to one company and barely register with the next. A recent leadership change might matter a great deal. Or it might mean absolutely nothing.
The information didn't change. The decision did.
Every score hides an assumption
We have become very comfortable scoring things. Lead scores. Risk scores. Intent scores. Fit scores. Health scores. Priority scores. The software world loves a score, and humans do too. Numbers feel clean. Numbers feel scientific. Numbers make messy things feel settled.
But every score hides an assumption, and the assumption sounds something like this: “According to what we currently believe matters…” That sentence is doing a lot of work.
I'm not anti-score. Scores are useful. They help sort a pile. They help focus attention. They help compare things quickly. But the score itself is not the intelligence. The intelligence is the reasoning behind it.
Why is this account more interesting than that one? What changed? What matters now? What makes this opportunity stronger? What would make us stop caring? What does the business actually value? Those questions matter more than the number at the end.
When the explanation disappears
This is one of those ideas that sounds obvious until you watch people use software. A number appears. It's green. It's near the top. Done. Nobody asks why.
That's dangerous, because once the explanation disappears, the score starts looking like truth. And it isn't. It's a judgment. A compressed one. Hopefully a good one. But still a judgment.
I think this is where a lot of “smart” systems quietly become dumb. They act as if the same definition of “good” applies everywhere. It doesn't. A good opportunity for a bank is not the same as a good opportunity for a field salesperson. A good customer for one business may be a terrible customer for another. A useful signal in one market might be noise in the next.
Context changes the meaning. That's true in business, and honestly, it's true in life too.
Scoring is closer to policy than math
That's why I've started thinking about scoring less like mathematics and more like policy. Not “this is objectively a 92,” but “given what we care about right now, this deserves more attention than the alternatives.”
That's a much healthier way to treat it, because priorities change. Markets change. Customers change. Products change. What mattered last year may not matter now, and a system should be able to reflect that.
Never trust a naked score
There's one rule I really like: never trust a naked score.
If something is important, I want to know why. If something moved up, I want to know what changed. If the evidence is weak, say it's weak. If the situation is unclear, say that too. The number can help me sort. It should never replace the explanation.
This matters more now because we're putting scores on everything. Customers. Leads. Employees. Vendors. Opportunities. Markets. Risk. Performance. We keep compressing complicated situations into numbers because numbers are easier to process. That's useful. But compression always loses something, and if we forget that, we start confusing convenience with truth.
Four questions for any score
So now when I see a score, I want to ask four questions:
For what decision? → Based on what priorities? → Using what evidence? → What would make it change?
If those questions don't have good answers, the score probably isn't intelligence. It's decoration.
Deciding what matters here
That may be the thing I keep coming back to lately. The hard part isn't always getting more information. I wrote about that when you can drown in information. It isn't even always analyzing it. The hard part is deciding what matters. For this company. For this decision. At this moment.
That answer is rarely universal, which is exactly why the score isn't the intelligence. The reasoning behind it is.
This is the thinking behind our growth and sales intelligence work: a number should always arrive with its reasoning. New to the series? Start with What Is an Intelligence Estate.