Against the Dashboard

The productivity dashboard is the physical form of the argument this site makes. It deserves its own objection.

What it does well

Being fair first, because the format is not worthless. For a related reference, see this overview.

Operational monitoring. Is the system up, is the queue growing, did the batch run. Genuinely what dashboards are for.

Trend detection at aggregate level, where individual accuracy does not matter.

And a shared reference. Everybody looking at the same number is worth something even when the number is imperfect.

The four objections

One. It selects for the measurable. Whatever the instrumentation emits becomes the definition of performance, and manager quality — the largest factor — emits nothing.

Two. It updates without judgement. A number that arrives automatically feels observed rather than chosen, and the choices behind it — what counts as active, which applications are productive — are invisible defaults set by a vendor.

Three. It produces confidence rather than understanding. Precision reads as accuracy, and a screen of exact figures feels like knowing.

Four. It changes what it measures. 24% take fewer breaks to avoid appearing idle — the instrument creating the reading.

The specific failure at individual level

Aggregate dashboards are defensible. Individual ones are not.

At team level, an activity figure smooths over the cases it gets wrong.

At person level, every error lands on somebody, and the errors are systematic rather than random: thinking, conversation and paper work all score as idle.

Which means the dashboard reliably penalises a specific kind of work rather than being noisy about all of it.

What to have instead

Two or three numbers you chose, reviewed on a slow cadence, checked against whether they move with what you care about.

Plus the things that are not numbers, looked at rather than measured.

A page rather than a screen, quarterly rather than live, is the shape that fits the questions actually being asked.

The uncomfortable admission

Managers want dashboards because managing without one is harder and lonelier.

A screen full of figures answers "how are things" without anybody having to form a view. Forming a view is the job, and it is uncomfortable, and the dashboard is a way of not doing it that looks like doing it.

That is the real reason they persist, and it is not addressed by better metrics.

The short version

• Dashboards are genuinely good for operational monitoring, aggregate trends, and providing a shared reference
• Four objections: they select for the measurable, update without judgement, produce confidence rather than understanding, and change what they measure
• Aggregate views are defensible and individual ones are not, because the errors are systematic rather than random
• Thinking, conversation and paper work all score as idle, so the instrument reliably penalises one kind of work
• Have two or three numbers you chose, reviewed slowly, checked against whether they move with the outcome
• They persist because a screen of figures answers "how are things" without anybody forming a view, which is the job

For additional context on this topic, see Unsplash.