Built Once, Opened Twice

A dashboard almost always gets attention at the moment it's built. Someone requests it, someone builds it, everyone looks at it in the meeting where it's unveiled. Then that meeting ends, and the dashboard's actual test begins - not whether it was built correctly, but whether anyone comes back to it on a normal Tuesday with no meeting scheduled.

Most don't pass that test. Not because the numbers are wrong, but because nobody built the dashboard around a question someone actually needs answered on a recurring basis. It was built around what could be measured, not around what anyone needed to know.

The Difference Is the Question, Not the Chart

A dashboard that gets used has a specific question behind it that someone needs answered on a schedule - weekly, monthly, before a specific recurring decision. "How's traffic doing" isn't that question. "Did last week's promotion bring in enough orders to justify running it again" is.

Dashboards built around a real recurring question tend to be smaller and less impressive than the alternative - one chart, sometimes two, answering exactly what someone needs and nothing else. Dashboards built around "everything we can measure" tend to be larger, more thorough, and completely unopened by week three.

Why Comprehensive Usually Loses

A dashboard with thirty metrics on it isn't more useful than one with three. It's just harder to open. Every metric added to a dashboard is a small tax on the next person who has to find the one they actually came for, and past a certain point that tax is enough to make people stop opening it at all.

This isn't an argument against collecting a lot of data. It's an argument that the dashboard and the data warehouse are different things, built for different audiences. Everything can live somewhere. Not everything belongs on the screen someone opens every Monday morning.

The Test That Actually Predicts Use

Before a dashboard gets built, it's worth asking who is going to open it, how often, and what decision it's supposed to inform. If there's no clear answer to all three, the dashboard is being built because the data exists, not because someone needs it - and that's usually the version that ends up unopened three weeks later.

Common Questions

Doesn't more data in one place save time?

Only if someone's actually looking for it there. A single dashboard with everything on it usually means more scrolling and more filtering, not less - the time saved by having data in one place is often lost again finding the specific number that matters this week.

How many dashboards should a small business actually have?

Fewer than most people expect - often one or two, each tied to a specific recurring decision, rather than one large dashboard trying to serve every question at once.

What happens to the metrics that don't make the dashboard?

They still exist and are still available when someone needs to dig in - they're just not sitting on the surface competing for attention with the numbers that get checked every week.

Is an unopened dashboard actually a problem?

Usually, yes - it's typically evidence the underlying question was never clearly defined, and that same gap tends to show up again the next time someone tries to answer that question without one.

A Dashboard Built Around a Question, Not a Data Dump

If there's a dashboard sitting unopened somewhere, that's usually a sign the underlying question was never quite pinned down.