They’re built like Business Intelligence tools, but used like decision-making tools.

A BI dashboard answers “what happened?” An ERP dashboard should answer “what should I do now?”

The first invites exploration. The second demands direction.

When you put twenty KPIs on a manager’s screen with no hierarchy, you’re not giving them information. You’re giving them homework.

The architectural mistake

Most enterprise systems are built by teams who deeply understand the business but rarely the psychology of decision-making under time pressure. The result is a kind of architectural inversion: the system optimises for completeness when its users need clarity.

A regional sales manager opening her dashboard at 8 am doesn’t want a database snapshot. She wants answers to three questions:

• Is anything wrong right now?
• What’s behind it?
• What should I do about it?

When a dashboard answers these — in that order, with progressive disclosure — it stops being a data viewer and becomes what I call a Decision Compass.

The three-layer fix

The fix isn’t fewer KPIs. It’s a different architecture.

Layer 1 — Information

Curated, not exhaustive. The foundation, available on demand but not foregrounded. Numbers, tables, raw data — everything that exists in the system, organised so users can drill into it without being hit by it on entry.

Layer 2 — Insight

The meaning layer. Comparisons, deviations, trends, contextual indicators. This is where information becomes interpretable. “Sales are down” becomes “Sales are down 12% versus last quarter, concentrated in the Eastern region.”

Layer 3 — Action

The decisive top. Where the system either prompts a clear next step, or surfaces a decision that needs to be made. This is the layer most ERPs never reach.

What this changes

When the architecture flips toward decision rather than completeness, three things happen:

• Time-to-decision drops, often dramatically.
• User confidence rises, because the system actively supports them rather than testing them.
• Adoption deepens, because the dashboard becomes a daily ally rather than a daily chore.

In a recent engagement, a B2B SaaS in the Gulf saw sales managers reduce their dashboard interpretation time by an estimated 60% after applying this framework. They didn’t add features. They removed cognitive friction.

A note for product teams

If you’re a product manager or a CPO reading this and recognising your own ERP in the diagnosis: the fix doesn’t require a complete rebuild.

It requires a reframe.

Most of the data is already there. Most of the metrics are already calculated. What’s missing is the architecture of attention — the deliberate design of what speaks first, second, last.

That reframe is, in my experience, the highest-leverage UX work you can do on a mature enterprise system. It costs less than a new feature. It changes more than ten of them.

The next time someone asks you to add a chart to your dashboard, ask them: which layer is this serving — Information, Insight, or Action? If the answer isn’t clear, the chart isn’t ready.