Short answer
A decision dashboard is a role-specific view that leads with the decisions a person owns — each shown as a decision card with the signal, recommended action, evidence, confidence, financial impact and approve or override buttons — and supports it with only the KPIs and predictive signals that matter for that decision.
Anatomy of a decision card
| Element | Purpose |
|---|---|
| Signal | What changed, in one sentence |
| Recommendation | The option the models and policies prefer |
| Evidence | The facts, forecasts and documents behind it — one click deep |
| Confidence & context health | How sure, and what is missing |
| Impact | Money, time, risk and customers affected |
| Authority | Who can approve, and by when |
| Actions | Approve, modify, override with reason — written back to the system of record |
What each persona sees
| Persona | Leads with | Key KPIs |
|---|---|---|
| CXO | Top three enterprise decisions and risks | Revenue at risk, readiness, decisions waiting |
| Reliability manager | Which asset fails next and when to act | Assets at risk, MTBF, planned vs unplanned |
| Production head | What to run, hold or reschedule | Schedule adherence, downtime, OEE |
| Quality head | Holds, releases and investigations | First-pass yield, lots on hold, complaints |
| Sales head | Deals and accounts needing action | Pipeline coverage, win rate, delivery risk |
| Distributor head | Stock, credit and attention by distributor | Fill rate, stock-out risk, channel inventory |
| Fleet head | Routes, vehicles and drivers | On-time %, utilization, fuel |
| Operations | Cross-site capacity and service | OTIF, OEE, backlog |
| Care operations | Where patients will wait today | ED boarding, discharges by noon, prior-auth turnaround |
| Automation lead | Which robots act alone and which escalate | Fleet availability, missions inside envelope, escalations |
| Analyst | What changed and whether it is real | Forecast accuracy, signals triaged, data freshness |
| CIO / CTO | AI and data health | Decision latency, drift, adoption |
Design principles
- Decision firstThe first thing on screen is a decision, not a chart.
- Evidence on demandDetails are one click away, never in the way.
- Same truth, different lensEvery persona reads the same entities and forecasts.
- Act where you workCards also appear in Teams, Slack, email, mobile and inside ERP or CRM screens.
Key takeaways
- BI shows what happened; decision dashboards show what to do.
- Each persona sees only the decisions it owns.
- Approvals and overrides train the system.
Frequently asked questions
What is the difference between a BI dashboard and a decision dashboard?
A BI dashboard reports metrics. A decision dashboard leads with recommended actions, their evidence and impact, and lets the owner approve or override in place.
Can decision cards appear inside our existing tools?
Yes. Cards can be embedded in Teams, Slack, email, mobile and inside applications like SAP, Salesforce or ServiceNow.