AI Dashboard: Build One You Will Actually Look At
Building a dashboard used to take a week and somebody who knew what they were doing. Now you describe what you want and it appears. That sounds like unambiguous progress, and it mostly is, except for one thing: the reason most dashboards fail was never that they were hard to build. It was that they answered questions nobody was actually asking, and making them cheaper to produce does nothing about that.
Two different things called the same name
Worth separating, because they solve different problems. The first is a dashboard built with AI help: you describe what you want, it assembles the charts and the queries, and you skip the configuration work. Useful, and a straightforward time saving.
The second is more interesting. A dashboard you can interrogate, where you ask a question in ordinary words and get an answer from your own data. That removes an old limitation, which is that a dashboard could only ever answer questions somebody thought of in advance. Every real question you had beyond that meant asking someone to build a new view, which in a small business meant not asking.
Why they stop being opened
The pattern is consistent and slightly embarrassing. Someone builds a comprehensive dashboard with fifteen charts. Everyone admires it. Two weeks later nobody has looked at it, and six weeks later it is wallpaper.
The cause is not laziness. It is that none of it changes what anyone does on a Monday morning. A number you look at and then carry on exactly as before is decoration, and AI has made decoration very cheap to produce, which is why this problem is about to get considerably worse rather than better.
Work backwards from decisions
| Decision you make often | Number that informs it |
|---|---|
| Do we need another person? | Booked work in the next six weeks |
| Should we chase more leads? | Quotes out, and how many are converting |
| Is anything going wrong quietly? | Jobs open longer than they should be |
This is the whole method. Start from the decision, find the number, build that. It sounds obvious and almost nobody does it, because starting from the data you happen to have is easier and produces something that looks more impressive.
Five to seven, no more
For something checked weekly, five to seven numbers is the practical ceiling. Past that nobody scans properly, and the figure that mattered gets lost among the ones that were merely interesting.
Here is a test that sounds glib and works. Could you recite the current value of each number from memory? If not, you are not really watching it, whatever the dashboard says. Keep the deeper detail somewhere you go deliberately when investigating something specific, which is a different job from a weekly glance.
Consistent matters more than clean
Your data does not need to be pristine. It does need to be consistent for the handful of things you are measuring.
If the same customer appears three ways, or two systems disagree about what counts as a completed job, an AI-built dashboard will report a wrong number inside an attractive chart. That is worse than having no dashboard, because a confident chart gets believed in a way a messy spreadsheet never does. Fix the naming and the definitions for your five numbers rather than attempting a full cleanup, which is the version of this project that never finishes. The narrow approach in getting your data ready for AI applies directly here.
Ask it what it left out
When AI builds the view or answers a question from your data, add one prompt: what did you assume, and what is this not counting?
You will regularly find that a revenue figure quietly excludes a category, or that a completion rate counts something differently than you would. Those definitional gaps are where dashboard numbers go wrong, and they are invisible in the chart itself. It is the same habit we set out in asking AI what it is likely to get wrong, applied to numbers instead of prose, and it matters more here because a figure carries more authority than a paragraph.
Review what you actually looked at
After a month, be honest about which numbers you checked and which you scrolled past. Remove the ones you ignored, even the ones you were sure would be important when you started.
That pruning is what keeps a dashboard alive, and it is much easier now that rebuilding costs minutes rather than a week. The old economics encouraged building one comprehensive thing and living with it. The new economics allow a small, ruthless view that changes as your questions change, which is a considerably better fit for how a small business actually runs. If you want the reporting side of this rather than the watching side, AI handing you the finished report covers the other half.
Frequently Asked Questions
What is an AI dashboard?
In practice it means two different things. One is a dashboard built with AI help, where you describe what you want in plain language and it assembles the charts and queries instead of you configuring them by hand. The other is a dashboard you can interrogate, where you ask a question in ordinary words and get an answer from your own data. The second is the more interesting of the two, because it removes the limitation that a dashboard can only answer questions somebody anticipated when they built it.
Why do most dashboards stop being used?
Because they answer questions nobody is actually asking. The usual pattern is that someone builds a comprehensive view with fifteen charts, everyone admires it for a fortnight, and then it quietly stops being opened because none of it changes what anyone does on a Monday. A dashboard earns its place only if looking at it regularly leads to a different decision. If you cannot name the decision a number informs, that number is decoration, and AI has made decoration extremely cheap to produce.
How many numbers should be on it?
Fewer than you want. For most small businesses, five to seven is the honest limit for something checked weekly, because beyond that nobody scans it properly and the important figure gets lost among the ones that are merely interesting. A good test is whether you could recite the current value of each number from memory. If you cannot, you are not really watching it. Extra detail is better kept in a place you go to deliberately when investigating something.
Does the data need to be clean first?
It needs to be consistent, which is a lower bar than clean but still a real one. If the same customer appears three ways, or two systems disagree about what counts as a completed job, an AI-built dashboard will confidently report a wrong number in an attractive chart. That is worse than no dashboard, because it gets believed. Fix naming and definitions for the handful of things you plan to measure rather than attempting a full data cleanup, which is a project that tends never to finish.
What is the best way to start?
Pick the three decisions you make most often that you would like to make with better information. Work backwards from each to the one number that would inform it. Build only those. Live with it for a month, then add or remove based on what you actually looked at rather than what seemed important at the start. A dashboard built from decisions stays useful. One built from available data becomes wallpaper, usually within about six weeks.
Measure the things that change decisions
We help Canadian businesses cut reporting down to the few numbers that matter, and make sure those numbers are counting what you think they are.
Related Articles
Judge AI on What It Finds, Not How It Talks
Your Data Isn't Ready for AI (and That's the Problem)
Quality Data Is AI’s Real Bottleneck — and Your Advantage
Ajan leads the ChatGPT.ca team: 200+ custom GPT builds and automation projects for 50+ businesses across 20+ industries. Based in Markham, Ontario. PIPEDA-compliant solutions.