WEBVTT

00:00:01.000 --> 00:00:03.970
This accompanies our article on dashboards.

00:00:04.280 --> 00:00:08.250
Users need to recognise what needs attention and trace the information

00:00:08.280 --> 00:00:09.690
to underlying records.

00:00:10.280 --> 00:00:13.650
A fictional team wants to distribute open requests.

00:00:13.880 --> 00:00:17.170
An overview card and separate export disagree.

00:00:17.400 --> 00:00:20.250
Which selection does each total represent?

00:00:20.520 --> 00:00:23.050
Agree which statuses mean open.

00:00:23.320 --> 00:00:26.090
Completed and withdrawn requests are excluded.

00:00:26.680 --> 00:00:30.650
Use only the agreed current source version for each request, so

00:00:30.680 --> 00:00:33.210
the same request does not appear twice.

00:00:33.480 --> 00:00:37.610
Define team, status, date field and reference time.

00:00:37.880 --> 00:00:40.770
Request age follows the agreed receipt date.

00:00:41.000 --> 00:00:44.490
A later edit must not silently make an old request look

00:00:44.520 --> 00:00:45.850
newer in the worklist.

00:00:46.440 --> 00:00:49.770
Selecting the card opens its corresponding records.

00:00:50.040 --> 00:00:52.810
An authorised user can reach the source record.

00:00:53.240 --> 00:00:55.930
That shows where work is assigned or completed.

00:00:56.520 --> 00:01:00.250
When a refresh fails, do not display a reassuring zero.

00:01:00.680 --> 00:01:04.010
Show the error and last successful processing time.

00:01:04.280 --> 00:01:09.210
Whether the earlier snapshot remains usable depends on agreed freshness requirements.

00:01:09.800 --> 00:01:13.130
Close a request in the source and check the selection after

00:01:13.160 --> 00:01:14.730
successful refresh.

00:01:15.000 --> 00:01:18.090
Test duplicate and incomplete records too.

00:01:18.360 --> 00:01:21.770
The card and detailed view must follow the same agreements.

00:01:22.360 --> 00:01:25.650
Define which roles may view details and exports.

00:01:25.880 --> 00:01:29.370
Test direct requests, not just visible controls.

00:01:29.880 --> 00:01:33.610
Assign an owner for definitions, source failures and ongoing

00:01:33.640 --> 00:01:35.050
maintenance of the dashboard.

00:01:35.560 --> 00:01:38.570
A dashboard does not automatically correct its data.

00:01:38.920 --> 00:01:41.490
It exposes meaning and limitations.

00:01:41.720 --> 00:01:46.010
Our source article explores operational questions, source records,

00:01:46.040 --> 00:01:49.370
freshness and appropriate access in more detail.