Decision intelligence is not analytics with a better name

By Meet Patel · 2026-09-06 · updated 2026-09-19

I sat through a demo last year for a product that called itself decision intelligence.

It was a dashboard. A good one — fast, well built, connected to more sources than most. At the end I asked what happened if nobody opened it. The answer was that it emailed you a summary on Mondays.

That is not decision intelligence. That is reporting with a delivery mechanism.

The category has a naming problem and it is doing real damage, because companies are buying the label and receiving the thing they already had.

The word everyone skips is "decision"

A decision has properties that a chart does not.

It has an owner — a named person who is accountable for making it. It has a moment where it is either made or deferred, and deferring is itself a choice with a cost. It has an asymmetry, because being wrong in one direction usually costs more than the other. And it has an afterwards: something either changed or it did not, and someone can check.

Analytics has none of that. Analytics has a query and a result. The result is correct or it is not, and that is the entire extent of its responsibility.

Which is why so much of what is sold as decision intelligence is analytics wearing the word. The product improves the quality of the answer and leaves every property of the decision untouched.

Four things that have to exist

If I am being strict about the category — and I think someone should be, before it dissolves into a marketing adjective — four properties have to be present. Not one. All four, because each of them fails on its own.

• Noticing. Something in the system is responsible for looking, without being asked. If every investigation begins with a human typing a question, the system holds no opinion about what matters, and the quality of your operations is capped by whoever happened to be curious that week.
• Reconciliation. When two sources disagree, something resolves the disagreement before it reaches a person. Most companies have three systems that will each answer the same question differently, all of them correct, and the reconciliation happens in a meeting by argument.
• Evidence. Every claim arrives with its source, when that source was read, how confident the system is, and what would change the answer. Without this you have a confident sentence, which is not the same thing as an answer.
• Disposition. It reaches a named person as a decision with a deadline, and the system knows afterwards whether the decision was made. A recommendation nobody acted on is indistinguishable from no recommendation, and should be counted as one.

Drop noticing and you have a very good search box. Drop reconciliation and you have a confident system that is wrong in ways nobody can trace. Drop evidence and you have an oracle. Drop disposition and you have a beautifully instrumented company that still decides things on Friday.

One question separates them

When someone shows me a product in this category, I ask a single thing.

What did this system decide not to tell me?

A reporting tool has no answer. It cannot have one, because it never selected anything — it displayed everything it had and handed the selection problem back to you. That is not a criticism of dashboards. Displaying everything is what they were built for and they do it well.

But a decision system has to have an answer, because selection is the whole job. It looked at four hundred things, judged that three hundred and ninety-six of them did not warrant your week, and it should be able to say which ones and on what basis. If nobody can tell you what got filtered out, nothing was filtered — you are simply looking at a subset chosen by an algorithm nobody has audited.

The second question, once they answer the first, is what happens when it is wrong about that. It will be. The interesting products have a story about it.

This is a management problem wearing a technology costume

Here is the part I did not expect.

Building the thing that notices is mostly tractable. Deciding what should count as worth a person's attention is not a technical question at all. It is a threshold, and a threshold is a management judgment: how much revenue movement is worth interrupting a founder for, how long a metric can drift before someone is accountable, which customer going quiet matters and which is normal for that segment.

Nobody in the company has usually written those down. They live in the head of whoever has been there longest, and they are inconsistent, and they change when that person is tired.

I assumed the hard part of this category was the model. I was wrong, and not narrowly. The hard part is that most companies have never made their attention thresholds explicit, so there is nothing for a system to implement. You end up writing down the company's judgment as a precondition to automating it, and that exercise is uncomfortable enough that a lot of teams stop there.

Which, honestly, is still worth doing. A company that has written down what deserves its attention is better run than one that has not, whether or not it ever buys software.

Where the line actually sits

Dashboards are reporting infrastructure. They answer a question that someone once cared enough about to build a chart for.

Decision intelligence is the layer above: responsible for which question matters this week, whether the numbers underneath it agree, what the evidence supports, and who now has to do something. It is a smaller and more accountable claim than the marketing around it suggests, and it is worth defending, because a category that means everything ends up sold by everyone and bought with no expectations at all.

If you take one test from this: ask what the system chose not to say. Then ask how it decides that. If the second answer is a threshold somebody in your company owns, you are looking at decision infrastructure. If it is a model, you are looking at a guess with good manners.

Written by Meet Patel — founder of Company 8, building Dan (usedan.com). Dubai, UAE.

Read on themeetpatel.com