The dashboard mattered less than who owned it.
Most enterprises are rich in data and poor in decisions. Adding another dashboard rarely changes anything; agreeing which ten numbers are reviewed weekly, by whom, usually does. On one hospital engagement the change held because the metric sat with the supervisor whose team caused the defect — not with the CFO who read the report.
The second problem is timing. A report assembled by hand describes a month that has closed. Generated from source, the same number is available while the decision it should inform is still open.
Why reporting consumes so much and changes so little.
Four systems, four definitions
The same metric is computed differently in each source, so the monthly meeting argues about the number instead of the decision.
Assembled by hand
A senior person spends two days a month rebuilding the same workbook from exports.
Describes a closed period
By the time it is agreed, every decision it would have changed has already been taken.
Built for the designer
The dashboard is dense, beautiful and answers questions the executive never asked.
Alerts nobody owns
Thresholds fire into a shared inbox and everyone assumes someone else is looking.
Forecasts nobody acts on
A model predicts demand and the planning cycle is still monthly, so the prediction changes nothing.
What the engagement actually includes.
Definition workshop
Before any dashboard is built, one agreed definition per metric across the organisation — because a shared template with unshared definitions produces false consolidation.
Reports that generate themselves
Recurring reporting produced from source data on a schedule, including narrative summaries, so nobody rebuilds a workbook from exports.
Role-based views
Each role sees the metric it can act on — the supervisor, the buyer, the executive — rather than one dense dashboard designed for nobody in particular.
Anomaly detection
Exceptions raised against expected behaviour and routed to a named owner with a required action, rather than fired into a shared inbox.
Forecasting where it changes a decision
Demand, cash and capacity forecasting applied only where the planning cadence can actually respond to it.
The review cycle
A weekly cadence where the number changes something, with the owner in the room. Without the cycle, the reporting is decoration.
Definitions, then views, then the cycle.
The problem is almost never the tool — it is the definitions beneath it. These are the components we build the layer from.
Ranges observed on Al Jawad engagements. Your targets are agreed in assessment, before the work starts.
Can you just build us a dashboard?
We can, and it usually will not change anything. We run the definition workshop first — without agreed definitions a shared dashboard produces false consolidation.
How many metrics should we track?
Roughly ten reviewed weekly, each with a named owner and a defined action. More than that and the review becomes a reading exercise.
Should we automate the exception review immediately?
Usually not. We would run it manually for longer first — the manual version teaches the team what the automated version later enforces.
Do you replace our BI tool?
Rarely. The problem is almost never the tool — it is the definitions beneath it and the review cycle above it.
Start a conversation.
Choose the one that fits where you are. None of them is a sales call. Each is an advisory conversation calibrated to a specific question.