Intraday Management: Dashboards
Objective. Read the IDM dashboards as a summarised at-a-glance view for a leader or review, and understand that the headline tiles compress detail that must be opened before any conclusion.
Dashboards present the day and recent period as summarised tiles and charts for someone who is not driving the floor minute to minute - a senior leader, or a review conversation - rolling up what the detail screens hold.
See it in the demo
What this screen answers
'Give me the state of play without making me drive every screen.' Dashboards serve the leader or reviewer who needs the shape of the day or the period at a glance - overall position, notable gaps, key trends - as the entry point from which they can drill into the detail screens when a tile looks off.
The task
Scope to the operation and period, scan the headline tiles for anything off-trend or service-critical, and use the dashboard as a navigation surface - each concerning tile is a prompt to open the underlying screen (forecast vs actual, staffing, backlog, analytics) where the real detail lives. For a CSM, the task is often to curate which tiles tell the customer's honest story for a review.
How to read it
A dashboard tile is a compression of many intervals, skills and days into one number or shape. The classic misread is concluding from the tile alone - a green summary can hide a bad interval, and a single red tile can be a recovered blip. Always open the detail before acting or reporting. And as everywhere in IDM, any tile built on simulated or projected figures is decision support, not a delivered result - do not present a rolled-up projection as an outcome.
Honest limits
Dashboards summarise; they do not add information beyond their source screens, and they inherit every limit of those feeds. Which tiles exist, how they are defined and whether they are configurable is production-dependent - confirm with product. Exact tile definitions, layout and the demo figures are SME-validation-pending.
Interpretation check
A dashboard tile compresses many intervals, skills and days into one signal - a green roll-up can hide a bad interval and a red tile can be a recovered blip. Always open the detail before concluding or reporting.
In the field
KnackGlobal (RCM): a leader scanning a green intraday dashboard still needs the claim-queue interval detail opened before telling stakeholders deadlines are safe - the tile compresses exactly the interval that could be short.
Practical task
On the demo, pick one dashboard tile that looks reassuring, open the underlying detail screen, and write a one-line note on whether the detail confirms or complicates the headline.
Self-check
The dashboard shows the day broadly green. Is it safe to report the day went well?
No. A roll-up tile can hide a bad interval or skill. Open the detail screens to confirm before reporting - the tile is an entry point, not a conclusion.
What is the dashboard's real job in the workflow?
To give a leader or reviewer the shape of the day or period at a glance and act as a navigation surface - each off-trend tile is a prompt to drill into the underlying detail screen.
A tile rolls up what-if projections. How should it be presented to a customer?
As decision support labelled as projection, never as a delivered outcome. Rolling projections into a tidy tile does not turn them into achieved results.
Does a dashboard tell you anything the detail screens do not?
No - it summarises them and inherits their limits, including feed freshness. Its value is speed of orientation, not new information.
Verified vs demo. Screen is live in the demo at /#/dashboards; exact tile definitions, layout, configurability and figures are SME-validation-pending.