Decision Intelligence vs Dashboards: What the Deal Shows

The acquisition is a bet on closing the gap between insight and action. Where that closed loop beats the dashboard, and where the dashboard still wins.

Pyramid was never just a chart tool, and that is the point.

We cover the practical side of this in our AI work, and how East of England Co-op adopted Pyramid looks at a closely related question.

The acquisition by ServiceNow is a bet that analytics belongs inside the work, not in a separate place you visit.

To understand why a workflow platform paid a serious sum for an analytics business, you have to look past the visuals. The interesting word in all of this is not "dashboard". It is "decision". The acquisition is a wager on a particular idea about where analytics is going, and whether you use any of the products involved, the idea is worth thinking through.

What decision intelligence was reaching for

The platform that was acquired bundled data preparation, modelling, analysis and natural-language querying into one place. The ambition behind that was never just prettier reports. It was to shorten the distance between a question and a decision: ask in plain language, get a trustworthy answer, act. That framing, analytics organised around the decision rather than the chart, is the thread that makes the deal make sense. Pyramid saw this earlier than most and built for it, which is a large part of why it was worth acquiring.

The dashboard is a destination

Think about how most reporting works today. You are doing your job in one system. A question comes up. You leave that system, open a dashboard in another, find the number, interpret it, form a view, then go back to where you were and do the thing. It works, and it has worked for thirty years. But there is a gap in the middle, the space between seeing the insight and taking the action, and that gap is filled by a human stopping, switching context and deciding what to do.

The dashboard tells you what is happening. The open question has always been what you do next, and where.

The closed loop the buyer wants

The bet is that the gap can close. Instead of a report that shows you a rising backlog, a system that surfaces the issue, opens the case, routes it, recommends the next action and lets you approve it, all in the flow of the work you were already doing. Insight that arrives as action, not as a chart you have to act on yourself. For routine, repeatable decisions, that is a real improvement, and it is clearly where the larger platforms are heading.

Where the dashboard still wins

It would be a mistake to declare the dashboard dead, and we would not. The closed loop is strong for known, repeatable decisions with a clear next step. It is weak, or simply wrong, for the work that has no predefined action: open-ended exploration, understanding why something happened, building the story behind a board number, testing a hypothesis nobody has framed yet. That work needs a place to think, and a dashboard, or a well-built report, is still the right place for it. The future is both, used for what each does well.

The catch nobody puts on the slide

There is a condition attached to all of this, and it is the same condition that runs through everything we have written lately. Acting automatically on an insight requires trust, and trust requires governance and a shared layer of meaning that both people and agents agree on. If an agent is going to open a case based on a number, that number has to be defined once, correctly, in a way everyone relies on. The closed loop is only as safe as the semantic layer underneath it. That is the unglamorous foundation the exciting demos depend on.

What this looks like in practice

Take a simple operational case: a supplier slips on delivery performance. In the destination model, a report shows the dip, an analyst spots it on their morning round, and someone emails the category manager to chase it. In the closed-loop model, the system notices the slip against an agreed threshold, opens a case, attaches the context, suggests contacting the supplier, and waits for a human to approve. Same insight, but the distance to action collapses from days to a click. Now picture the opposite: a board asking why margin fell last quarter. No threshold, no predefined step, just a question that needs a person to investigate. That one still belongs in a report. The two examples, side by side, are the whole distinction.

What we would do this week

Find one report in your business that ends with a person manually doing a task: chasing a supplier, flagging a risk, opening a ticket. That handoff, from insight to action, is exactly what this shift is aimed at. Naming a few of them tells you where decision intelligence would earn its keep in your organisation, and where a dashboard is still the right answer.

If any of this sounds familiar, talk to us about your data.

Decision intelligence versus the dashboard: what the deal is really about