Business intelligence answers the question you asked. That was always the flaw.

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

Business intelligence has spent thirty years getting very good at one thing: answering the question you asked.

It works. The numbers are right, they arrive faster than they used to, and the self-serve generation genuinely removed a bottleneck. I am not here to tell you BI failed. It did what it said.

The problem is what it said.

The expensive failures are never the asked questions

Think about the last thing that genuinely hurt your company. Not an outage — a business failure. A segment that quietly stopped converting. A cohort that churned for a reason nobody named for two months. A pricing assumption that stopped being true and kept being used.

Now ask whether anyone would have found it by opening a dashboard.

Almost never, and the reason is structural rather than anyone's fault. To find it on a dashboard, someone had to already suspect it, already build the view, and already be looking on the week it moved. Three conditions, all of which have to hold at once. The failures that hurt are precisely the ones where at least one of them did not.

Business intelligence optimises the answer. It has never held any responsibility for the question.

Two different layers, routinely confused

It is worth being precise about this, because the confusion is what causes companies to buy more of the first thing while believing they are buying the second.

• Reporting infrastructure — warehouses, models, dashboards, scheduled emails. Its job is that the number is correct and available. It succeeds when a person who looks can find out.
• Decision infrastructure — thresholds, owners, escalation, review. Its job is that the right person finds out without having looked, and that something happens afterwards. It succeeds when a decision was made and the outcome was checked.

Almost every company I have worked in has industrial-grade reporting infrastructure and effectively no decision infrastructure. Not weak decision infrastructure. None — no written thresholds, no owner per signal, no measurement of how long it takes to respond to anything.

And because the two are confused, the response to a decision failure is almost always to build more reporting. Somebody missed something, so we add a chart. It feels like a fix. It is the same layer, one unit larger.

Where the responsibility moves

If I had to compress the difference into one sentence: in business intelligence, the human is responsible for noticing. In decision intelligence, the system is.

That is a much bigger change than it sounds, because responsibility for noticing is the thing that quietly consumes a management team. It is not the meetings. It is the background process of holding four hundred things loosely in mind in case one of them moves, which is what a good operator is actually doing all day and why they are tired.

Moving that responsibility has consequences a reporting tool never has to deal with. The system now has to be able to say why it raised something. It has to be able to say nothing for three weeks and be trusted. It has to handle two sources disagreeing rather than showing both and letting a meeting resolve it. It has to accept that being wrong is a real event with a cost, not just an incorrect cell.

Those are accountability problems. BI never had to have them, which is exactly why it was easy to adopt and exactly why it did not change how decisions get made.

What I had backwards

For a long time I thought the gap was speed. Get the data fresher, get the pipeline to minutes instead of hours, and the organisation would respond faster.

We did that. The warehouse got current to the minute. Response time did not move at all, because the constraint was never freshness — it was that the only forum where a class of decision got made met on Fridays. A pipeline current to the second and a company that decides weekly gives you a company that decides weekly, with a very good pipeline.

I had optimised the half of the system that was already working.

BI is not dying, it is being demoted

The honest ending here is not that dashboards go away. They will not. They are good at what they do and there will always be a need to go and look at something specific.

What changes is their position. Reporting stops being the top of the stack and becomes a layer that something else reads from — the way a database stopped being the product once applications were built on it. Nobody says the database died. It just stopped being where a person went.

The layer above it is the one worth arguing about, because it is the one that has an opinion about what your week is for.

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

Read on themeetpatel.com