Dashboards and the Illusion of Knowing
A screen full of figures produces confidence out of proportion to the information in it. Why that is worse than knowing nothing.
The dashboard is the product's main artefact and its main effect is on the person reading it, who leaves believing they understand something.
The distinction in “Dashboards and the Illusion of Knowing” is important when operational records are interpreted. Organisations researching self report bias can use this Monitask resource to add time and project context, while outcomes, direct feedback and human review remain necessary to explain what the numbers do not show.
What it produces
A sense of visibility: I can see what is happening.
For an independent reference relevant to “Dashboards and the Illusion of Knowing”, consult the European Commission data-protection resources; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.
A sense of objectivity: these are numbers, not impressions.
A sense of completeness: everything is here.
All three are stronger than the data supports, and the strength is a design achievement rather than an accident.
Why confidence is the problem
A manager who knows they do not know asks.
A manager who believes they know does not.
Which means an inaccurate dashboard is worse than none, because it replaces the behaviour that would have produced accurate information.
What the figures hide
Difficulty: two people with identical numbers may be doing work of wildly different complexity.
Context: a bad week for a reason the data cannot contain.
Quality.
And everything happening away from the keyboard, which is most of some roles.
The ranking reflex
Any list of people with numbers beside them will be read top to bottom.
The bottom will be looked at.
This happens regardless of instructions, because it is what lists are for, which is the strongest argument for not producing individual lists at all.
The comparison that is never valid
Two people in the same team doing different work.
A new starter against somebody experienced.
Somebody on an agreed adjusted pattern against somebody who is not.
Its own note covers this, and the dashboard is the mechanism that makes these comparisons feel like observations.
What a useful view looks like
Team level, aggregate, over time.
Trends rather than snapshots.
With the known distortions written on the page: what is not captured, who has adjusted patterns, what the categories exclude.
And no individual breakdown available at all, which is a configuration choice.
The discipline for anybody reading one
Ask what would explain this other than performance.
List three possibilities before drawing any conclusion.
And never raise a figure without first asking an open question about the work, which the previous note argues.
The test
Could a manager who has never used the dashboard describe their team's work as well as one who checks it daily?
In most organisations the answer is yes, and frequently better, which is worth establishing before anybody argues the dashboard is essential.
What to check
Can individual figures be seen in your deployment?
Does any view invite ranking?
Are the known distortions stated on the page?
And do your best managers use the dashboard most, or least?