4 ms·
For the example of the call centre a graph would still be better than a gauge. Because if the graph of people in the queue is going up you may want to get more
by EdSchouten 2y ago
For the example of the call centre a graph would still be better than a gauge. Because if the graph of people in the queue is going up you may want to get more staff.
- viraptor 2y agoYes / no... For continuous action you'd want something more clever for that, like an indicator of wait over capacity, taking standard load during that time + prediction into account. You want an indicator not history to interpret. On the other hand, for planning / long term analysis, you probably want something like daily heatmap, or similar. I'm not sure where a plain graph of very recent history would be useful in practice in that scenario. Again, the main thing I'm trying to say is: who looks at the dashboard, why, from what distance, etc. all impact on what elements you want to use. None of them is bad/good in general. (Apart from 3d pie)